headers
Hubert Feyrer | 1 Oct 2005 01:13
Picon
Favicon

Re: w with 24h format

On Fri, 30 Sep 2005, Rui Paulo wrote:
> | I'd prefer to see the Login time 10:22PM as 22:22.
> Maybe this could be done locale-specific ?

Seconded.

> I agree with the idea of sending a PR.

Including patch. :)

  - Hubert
Permalink | Reply | 0 comments |
headers
Steven M. Bellovin | 1 Oct 2005 02:23

Re: w with 24h format

In message <Pine.LNX.4.61.0510010112290.24261 <at> m24s24.vlinux.de>, Hubert Feyrer 
writes:
>On Fri, 30 Sep 2005, Rui Paulo wrote:
>> | I'd prefer to see the Login time 10:22PM as 22:22.
>> Maybe this could be done locale-specific ?
>
>Seconded.
>
>
>> I agree with the idea of sending a PR.
>
>Including patch. :)
>

It looked to be a very simple change; the time-printing is isolated to 
a separate file pr_time.c.  My original thought was an enviornment
variable W_TIMEFORMAT that would hold a strftime string, but in fact 
there are three separate cases in the code.

		--Steven M. Bellovin, http://www.cs.columbia.edu/~smb
Permalink | Reply | 0 comments |
headers
Christos Zoulas | 1 Oct 2005 03:17

Re: w with 24h format

In article <9982.1128112790 <at> www72.gmx.net>,
Zafer Aydogan <zafer <at> gmx.org> wrote:
>This is a feature request:
>
>I'd like to have the possibility to see the time in 24h Format, when using
>the command "w". I'm living in a country where AM and PM is not used.
>It would be great to have an Option to set these.
>
>$ w
>10:36PM  up 181 days, 10:54, 1 user, load averages: 0.07, 0.10, 0.08
>USER    TTY FROM                           LOGIN <at>   IDLE WHAT
>zafer    p0 wh30221.techfak.uni-kiel.de 10:22PM     0 w
>zafer <at> mia:~ $
>
>I'd prefer to see the Login time 10:22PM as 22:22.

The real fix is to add localization code to it.

christos
Permalink | Reply | 0 comments |
headers
Kent Peacock | 1 Oct 2005 03:37
Picon

Re: w with 24h format

> The real fix is to add localization code to it.

Yep. Solaris has this already...

Kent
Permalink | Reply | 0 comments |
headers
Hubert Feyrer | 1 Oct 2005 03:45
Picon
Favicon

Re: w with 24h format

On Fri, 30 Sep 2005, Kent Peacock wrote:
>> The real fix is to add localization code to it.
> Yep. Solaris has this already...

In what version?

tabaluga% w
   3:44am  in Betrieb 16:38,  1 Benutzer,  Durchschnittslast: 0,03, 0,00, 
0,00
User     tty           login <at>   idle   JCPU   PCPU  what
feyrer   pts/1         3:44am                      w
tabaluga% uname -a
SunOS tabaluga 5.10 Generic i86pc i386 i86pc

  - Hubert
Permalink | Reply | 0 comments |
headers
Kent Peacock | 1 Oct 2005 05:08
Picon

Re: w with 24h format

> In what version?

Solaris 8+ has support for locales. See man strftime(3C). However, it does
appear that the "w" command is not localized. Sorry about that:

kent <at> nomad-70:69> setenv LC_TIME fr
kent <at> nomad-70:70> date
vendredi, 30 septembre 2005, 20:07:46 PDT
kent <at> nomad-70:71> w |head -10
  8:07pm  up 24 day(s),  8:20,  4 users,  load average: 0.56, 0.38, 0.33
User     tty           login <at>   idle   JCPU   PCPU  what
kent     dtlocal      17Sep05    21   1:12     11  olwmslave
kent     pts/4        17Sep05 2days      6         /bin/csh
kent     pts/5        17Sep05    10      1      1  /bin/csh
kent     pts/6        17Sep05 2days                /bin/csh
kent     pts/7        17Sep0513days                /bin/csh
kent     pts/8        17Sep0511days                /bin/csh
kent     pts/9        17Sep05 8days                /bin/csh
kent     pts/10       17Sep05 4days                /bin/csh
kent <at> nomad-70:72> ...

Kent
Permalink | Reply | 0 comments |
headers
Arto Huusko | 1 Oct 2005 09:50
Picon
Picon

Re: w with 24h format

Christos Zoulas wrote:
> In article <9982.1128112790 <at> www72.gmx.net>,
> Zafer Aydogan <zafer <at> gmx.org> wrote:
> 
>>This is a feature request:
>>
>>I'd like to have the possibility to see the time in 24h Format, when using
>>the command "w". I'm living in a country where AM and PM is not used.
>>It would be great to have an Option to set these.
>>
>>$ w
>>10:36PM  up 181 days, 10:54, 1 user, load averages: 0.07, 0.10, 0.08
>>USER    TTY FROM                           LOGIN <at>   IDLE WHAT
>>zafer    p0 wh30221.techfak.uni-kiel.de 10:22PM     0 w
>>zafer <at> mia:~ $
>>
>>I'd prefer to see the Login time 10:22PM as 22:22.
> 
> The real fix is to add localization code to it.

Which would require NetBSD to actually support LC_TIME, and I would
really love to see that one.
Permalink | Reply | 0 comments |
headers
David Laight | 1 Oct 2005 11:32
Picon

Re: w with 24h format

On Sat, Oct 01, 2005 at 10:50:56AM +0300, Arto Huusko wrote:
> 
> Which would require NetBSD to actually support LC_TIME, and I would
> really love to see that one.

Looking forward to fixing all the scripts that parse the output of ls(1).

	David

--

-- 
David Laight: david <at> l8s.co.uk
Permalink | Reply | 0 comments |
headers
Ignatios Souvatzis | 1 Oct 2005 20:35
Picon

Re: w with 24h format

On Sat, Oct 01, 2005 at 10:32:56AM +0100, David Laight wrote:
> On Sat, Oct 01, 2005 at 10:50:56AM +0300, Arto Huusko wrote:
> > 
> > Which would require NetBSD to actually support LC_TIME, and I would
> > really love to see that one.
> 
> Looking forward to fixing all the scripts that parse the output of ls(1).

They should set LC_TIME etc. to C.

	-is
Permalink | Reply | 0 comments |
headers
Igor Sobrado | 2 Oct 2005 20:51
Picon

iop(4) reference to I2O...

Hello!

Don't know if it is the right mailing list (netbsd-docs <at>  seems related
to external documentation, but I have an impressive ability to chose the
wrong lists to post messages).  I will post here instead... hope it is
the right mailing list.  ;-)

I found what I think it is a problem in iop(4).  One of the references
in the "See Also" section seems wrong to me:

  http://www.intelligent-io.com/ is not related with I2O at all, though.

I suggest removing this reference.  Should I open a PR on this issue?

Can I suggest minimizing the number of references to URLs too?  Most
URLs are short lived (at least when compared to operating systems
documentation).  I believe that references to other manual pages,
RFCs, and published articles and standards are more adequate.

Cheers,
Igor.
Permalink | Reply | 0 comments |

Gmane