Using a null byte as the only argument separator
to xargs just doesn't work:
C:\Temp>ls -lb t
total 0
-rw-rw-rw- 1 user group 0 Sep 19 22:01 a\ b
-rw-rw-rw- 1 user group 0 Sep 19 22:01 c\ d
-rw-rw-rw- 1 user group 0 Sep 19 22:01 e\ f
# (i.e., there are three files whose names contain
# whitespace in the directory "t")
C:\Temp>find t -type f -print0 | xargs -0 ls
ls: t\a: No such file or directory
ls: b: No such file or directory
ls: t\c: No such file or directory
ls: d: No such file or directory
ls: t\e: No such file or directory
ls: f: No such file or directory
# xargs still splits its input at whitespace
# disregarding the -0 option
The output from "find ... -print0" proves to be correct.
It seems to be a xargs problem.
Logged In: YES
user_id=518245
Hi Additionally, I have this problem. I dont know if it
could be because of the white spaces in one of the file
names.
DEMUC16731=C:/bea/weblogic81/config/cscdomain> find . -type
f -print | xargs
C:\rkumar\utils\unix_env\usr\local\wbin\xargs.EXE: cannot
fork