The command reads its input and splits the arguments at spaces or newlines. It's legal (though pretty unusual) for UNIX filenames to have spaces or newline characters in them. Those filenames can cause xargs trouble.
For example, I have a directory full of copies ofarticles. The filenames are the same as the subjects of the articles:
lsA use for the "yes" command Beware UNIX Security Holes Causes of 'test' errors ...
The problem comes when I run a command like this:
find . -type f -mtime +7 -print | xargs rm
If find outputs the pathname ./Beware UNIX Security Holes, the xargs command would most likely tell rm to remove four filenames: ./Beware, UNIX, Security, and Holes. I'd probably get four error messages from rm because no files with those names exist. If they did exist, though, they'd be removed when they shouldn't! Newlines in filenames can cause the same problems.
Some versions of xargs (see below) are better at handling this problem. Here's a simple test to see how well your system's version works.
Make an empty directory, a filename with spaces, and a filename with a newline. Try to remove the file:
That xargs broke the filenames at the space and newline. If it hadn't broken the filenames, the files would have been removed.
The GNU xargs (on the CD-ROM) has a -0 (zero) option; this means the pathnames it reads are separated by NUL characters instead of whitespace. GNU's find (also on this disc) has a -print0 operator that puts a NUL between pathnames instead of a newline. Use them together like this:
find . -type f -mtime +7 -print0 | xargs -0 rm