Date: Thu, 31 Oct 1996 08:10:02 -0800 (PST) From: Nathan Lawson <nlawson@kdat.csc.calpoly.edu> To: wollman@lcs.mit.edu (Garrett Wollman) Cc: freebsd-security@freebsd.org Subject: Re: /etc/security Message-ID: <199610311610.IAA20880@kdat.calpoly.edu> In-Reply-To: <9610311505.AA19105@halloran-eldar.lcs.mit.edu> from "Garrett Wollman" at Oct 31, 96 10:05:55 am
next in thread | previous in thread | raw e-mail | index | archive | help
> <<On Thu, 31 Oct 1996 08:18:58 +0100, sthaug@nethelp.no said:
>
> >> checking setuid files and devices:
> >> find: /doscopy/sb16/pro_org/i'vebeen.org: illegal path
> >> find: /doscopy/sb16/pro_org/she'llbe.org: illegal path
>
> The best way to deal with this is probably using the `-print0' primary
> to `find' and using a `perl -n0' script to process the results, like:
>
> find ..... -print0 | perl -n0e 'exec "/bin/ls", "-lFgod", <>;'
Yes, the -print0 option is useful, but to avoid executing another interpreter
just for the task of filtering out the NULLs, I prefer to use xargs -0
>From the man page:
-0 Changes xargs to expect NUL (``\0'') characters as seperators,
instead of spaces and newlines. This is expected to be used in
concert with the -print0 function in find.
This avoids execing a costly interpreter and keeps the scripts using xargs,
which is useful with very long path lists.
--
Nate Lawson "There are a thousand hacking at the branches of
CPE Senior evil to one who is striking at the root."
CSL Admin -- Henry David Thoreau, 'Walden', 1854
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610311610.IAA20880>