who(1) exit status

2008-06-23 Thread Shal-Linux-Ind
Hi, who(1) exit status is always 0. $ who --v who (coreutils) 5.2.1 ... ... $ who $echo $? 0 I think all commands should fail with exit status 1, which is usefull in processing with other commands. Thanks Shal ___ Bug-coreutils mailing list Bug-co

Re: who(1) exit status

2008-06-23 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Shal-Linux-Ind on 6/23/2008 4:05 AM: | Hi, | | who(1) exit status is always 0. | | $ who --v | who (coreutils) 5.2.1 Thanks for the report. Consider upgrading - that is several years old, and the latest stable version is 6.12. But I ha

Re: who(1) exit status

2008-06-23 Thread Andreas Schwab
Eric Blake <[EMAIL PROTECTED]> writes: > According to Shal-Linux-Ind on 6/23/2008 4:05 AM: > | Hi, > | > | who(1) exit status is always 0. > | > | $ who --v > | who (coreutils) 5.2.1 > > Thanks for the report. Consider upgrading - that is several years old, > and the latest stable version is 6.12

[PATCH]: Replace echo AUTHORS FIXME unknown by bash builtin echo authors

2008-06-23 Thread Ondřej Vašík
Hello, according to bash sources(AUTHORS file), authors of bash built-in echo are Brian Fox, Chet Ramey. As coreutils echo is derived from bash builtin echo, I guess those authors should be used instead of FIXME unknown. Patch fixing echo authors is attached. This problem has been reported at http

Re: [PATCH]: Replace echo AUTHORS FIXME unknown by bash builtin echo authors

2008-06-23 Thread Jim Meyering
Ondřej Vašík <[EMAIL PROTECTED]> wrote: > according to bash sources(AUTHORS file), authors of bash built-in echo > are Brian Fox, Chet Ramey. As coreutils echo is derived from bash > builtin echo, I guess those authors should be used instead of FIXME > unknown. Patch fixing echo authors is attached

Re: who(1) exit status

2008-06-23 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Bo Borgerson on 6/23/2008 6:59 AM: | So it sounds like there's no portable way to distinguish between: | | 1. an error trying to look up information | 2. no information to be found | | Would it make sense, though, to return a nonzero exit

Re: who(1) exit status

2008-06-23 Thread Andreas Schwab
Eric Blake <[EMAIL PROTECTED]> writes: > POSIX requires an error message to stderr explaining the non-zero status. > ~ What would we report? On the other hand, it seems like we should always > expect at least the current user to be logged in (otherwise, how is who > being invoked?), so the idea o

Re: who(1) exit status

2008-06-23 Thread Bo Borgerson
Andreas Schwab wrote: > Eric Blake <[EMAIL PROTECTED]> writes: > >> According to Shal-Linux-Ind on 6/23/2008 4:05 AM: >> | Hi, >> | >> | who(1) exit status is always 0. >> | >> | $ who --v >> | who (coreutils) 5.2.1 >> >> Thanks for the report. Consider upgrading - that is several years old, >> a

Re: check-AUTHORS fails because of non ansi characters

2008-06-23 Thread Michael Geng
On Sat, Jun 21, 2008 at 06:10:28PM +0200, Bruno Haible wrote: > Michael must be using a locale in ASCII encoding; if it were a Latin1 > encoding, > the output would have contained a cedilla, not a question mark. I did not have the en_US.UTF8 locale installed. After installing it the problem disa

Translation failure

2008-06-23 Thread JackDesBwa
Hello, I think there is a failure in the french translation of "rmdir". This morning I tried to remove a non empty directory and rmdir said it can't delete because the file exists. Probably it wanted to say that there were files in this directory. The exact message was : "rmdir: échec de suppres

Re: Translation failure

2008-06-23 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to JackDesBwa on 6/23/2008 12:50 PM: | Hello, | | I think there is a failure in the french translation of "rmdir". | | This morning I tried to remove a non empty directory and rmdir said it can't | delete because the file exists. Can you re

Re: cp -up forever

2008-06-23 Thread jidanni
Fellas, in http://bugs.debian.org/276500 m> There is a new syscall in 2.6.22, utimensat. It gets a "struct timespec" m> which allows nanosecond resolution. That means you can now fix the difference in $ touch m; touch -r m n; stat -c %y m n 2008-06-24 06:13:24.106160298 +0800 2008-06-24 06:13:24.10

Re: cp -up forever

2008-06-23 Thread Eric Blake
jidanni.org> writes: > > Fellas, in http://bugs.debian.org/276500 > m> There is a new syscall in 2.6.22, utimensat. It gets a "struct timespec" > m> which allows nanosecond resolution. > That means you can now fix the difference in > $ touch m; touch -r m n; stat -c %y m n > 2008-06-24 06:13:24

Re: who(1) exit status

2008-06-23 Thread Shal-Linux-Ind
On 6/23/08, Andreas Schwab <[EMAIL PROTECTED]> wrote: > > Eric Blake <[EMAIL PROTECTED]> writes: > > > According to Shal-Linux-Ind on 6/23/2008 4:05 AM: > > | Hi, > > | > > | who(1) exit status is always 0. > > | > > | $ who --v > > | who (coreutils) 5.2.1 > > > > Thanks for the report. Consider u