Xref: utzoo comp.unix.shell:526 alt.sources.d:950
Path: utzoo!utgpu!cs.utexas.edu!usc!apple!motcsd!mcdcup!mcdchg!att!cbnews!lvc
From: lvc@cbnews.att.com (Lawrence V. Cipriani)
Newsgroups: comp.unix.shell,alt.sources.d
Subject: Re: Beware xargs security holes
Summary: see -i option to xargs
Message-ID: <1990Oct9.204247.22082@cbnews.att.com>
Date: 9 Oct 90 20:42:47 GMT
References: <28790001@col.hp.com> <28790002@col.hp.com> <9365:Oct910:43:4590@kramden.acf.nyu.edu>
Followup-To: comp.unix.shell
Organization: Ideology Busters Inc.
Lines: 13

In article <9365:Oct910:43:4590@kramden.acf.nyu.edu>, brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
> Yeah. xargs should have a -0 option for taking null-separated filenames
> for its input. find should have a -print0 option for producing similar
> output.

It does, sort of:

	find . -print | xargs -i your_command '{}'

but, since the -i option executes your_command once per file it will be
very slow.
-- 
Larry Cipriani, att!cbvox!lvc or lvc@cbvox.att.com