Date: Sun, 24 Nov 1996 23:15:07 -0700 (MST) From: Marc Slemko <marcs@znep.com> To: Warner Losh <imp@village.org> Cc: current@FreeBSD.org Subject: Re: find and xargs in /etc/security Message-ID: <Pine.BSF.3.95.961124230736.12070O-100000@alive.ampr.ab.ca> In-Reply-To: <E0vRs6h-0005mq-00@rover.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Yuck. There is the little matter of sort which messes things up. There are ways around it by adding another command to the pipe, but that starts to get ugly. Hmm. Unless we just do a find -ls, but that means we don't get the full timestamps. There is more wrong with /etc/security than that, so perhaps it is worth looking at it a bit more deeply. OpenBSD and NetBSD have a far more comprehensive /etc/security. On Sun, 24 Nov 1996, Warner Losh wrote: > In message <Pine.BSF.3.95.961124193116.12070J-100000@alive.ampr.ab.ca> Marc Slemko writes: > : Now that xargs has a -0 option to allow it to use the output from find > : -print0, perhaps /etc/security should be updated to use these options so > : we get rid of the garbage output caused by things such as files with > : spaces in their name? > > What an excellent idea? Wanna implement this on your system, and send > the patches to a committer? I'll be happy to commit this change so > long as others don't object and the patches are good! > > Warner >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.961124230736.12070O-100000>