X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: Date: Tue, 11 Dec 2007 20:00:45 +0000 From: "Richard Copley" To: cygwin@cygwin.com Subject: Re: question with xargs and jar- seems to drop files. In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <042c01c836a1$e6c0d1d0$2e08a8c0@CAM.ARTIMI.COM> <20071205123104.GH26345@calimero.vinschen.de> <04a001c8374f$a58b1a00$2e08a8c0@CAM.ARTIMI.COM> <20071205153214.GI26345@calimero.vinschen.de> <04a801c83756$90a8b5f0$2e08a8c0@CAM.ARTIMI.COM> <20071205172520.GB3147@ednor.casa.cgf.cx> <04b901c83767$91e6f290$2e08a8c0@CAM.ARTIMI.COM> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On 05/12/2007, Mike Marchywka wrote: > I seem to have an odd problem with xargs and jar. I'm not sure if I can isolate a simple test > case but essentially it only seems to be taking some of the input files. > > This seems to work suggesting the file list is acceptable to jar: > > $ more latest65day | jar -@cvf wtf2.zip>jarlog2.txt > > this, however, only includes a some files, apparently lopping off certain directories: > > $ more latest65day | xargs jar -cvf wtf2.zip>jarlog.txt > > > $ xargs --version > GNU xargs version 4.3.8 > Built using GNU gnulib version 2007-05-26 > > Administrator@TESTBED01 /cygdrive/e/new/temp > $ jar -V > jar (fastjar) 0.92-gcc > > Copyright 1999, 2000, 2001 Bryan Burns > Copyright 2002 Free Software Foundation > > Thoughts on diagnostic process of known problems? At first, I thought it had to do with > errors encountered during the jarring but I think I've eliminated all of those ( missing files > mostly). Also, as I indicated before, my configuration is suspect but I wouldn't expect it > to cause problems like this. I expect you've got this covered, but last week when I had a similar problem with xargs and tar, it turned out that my problem was that I hadn't read the xargs manpage (not recently anyway). Its second sentence is "xargs ... executes the command ... one or more times ...". The solution was to use tar's --files-from option. For jar: -@, see above (except that you should redirect jar's standard input to your file-of-files with "