[15:38:19]$ touch -d '20041001 18:00' test
[15:39:05]$ ls -al test
-rw--- 1 user users 0 2004-10-01 18:00:00 test
[15:39:08]$ touch -d '20041001 18:00 +0400' test
[15:39:21]$ ls -al test
-rw--- 1 user users 0 2004-10-01 14:00:21 test
The second form sets the seconds field of the file
to
i have noticed there is no -option character for
"ignore-fail-on-non-empty",
Because of the simple reason that there is no such short option for
--ignore-fail-on-non-empty.
___
Bug-coreutils mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mai
On Mon, 18 Oct 2004, Alex Powell wrote:
>i have noticed there is no -option character for
>"ignore-fail-on-non-empty",
Not all long options have corresponding short options; typically I see
this when an option is a GNU-extension, and would not be found in other
version of the utility.
Cheers,
P
i have noticed there is no -option character for "ignore-fail-on-non-empty",
i still have no idea what it is :). i dont know if it's a problem with the
university installs of linux or not. hope this is informative enough!
--pasted from console--
On Mon, Oct 18, 2004 at 05:19:38PM +0200, Alfred M. Szmidt wrote:
>The fold_text() function doesn't ever return anything and its
>return code is never checked.
>
> There is no fold_text() function in coreutils 5.2.1.
>
> [EMAIL PROTECTED]:~/coreutils-5.2.1$ grep -r fold_text *
> [EMAIL
The fold_text() function doesn't ever return anything and its
return code is never checked.
There is no fold_text() function in coreutils 5.2.1.
[EMAIL PROTECTED]:~/coreutils-5.2.1$ grep -r fold_text *
[EMAIL PROTECTED]:~/coreutils-5.2.1$
___
The fold_text() function doesn't ever return anything and its return
code is never checked.
Original bug report:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136090
--- coreutils-5.2.1/src/fold.c.void 2004-10-18 13:42:18.119712001 +0100
+++ coreutils-5.2.1/src/fold.c 2004-10-18 13:
Cyril Bouthors <[EMAIL PROTECTED]> wrote:
...
> Please also note that mv does not fail when "too many open files"
> messages occur, it just keep on warning for each file (~9000 warnings
> in the initial example) and does not move anything.
True. Neither mv nor rm exit immediately when they encoun
On 18 Oct 2004, [EMAIL PROTECTED] wrote:
> Thanks a lot for that report.
You are welcome.
> It is indeed a bug.
Thanks for the fix.
Please also note that mv does not fail when "too many open files"
messages occur, it just keep on warning for each file (~9000 warnings
in the initial example) an
Paul Eggert <[EMAIL PROTECTED]> wrote:
> Here's how I reproduced it, both with coreutils 5.2.1 and with CVS
> coreutils. On my host, /tmp and /home are different file systems;
> this is a crucial part of the bug.
>
>ulimit -n 1024
>cd /home/eggert/junk
>mkdir foo /tmp/foo
>cd foo
>
Cyril Bouthors <[EMAIL PROTECTED]> wrote:
> I'm having problems when moving everything from a directory that
> contains 10852 top level directories and a total of ~30+ files and
> subdirectories with this command:
Thanks a lot for that report.
It is indeed a bug.
Here's the fix:
Plug
11 matches
Mail list logo