X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
From:	"Dave Korn" <dave DOT korn AT artimi DOT com>
To:	<cygwin AT cygwin DOT com>
References:	<042c01c836a1$e6c0d1d0$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <20071205123104 DOT GH26345 AT calimero DOT vinschen DOT de> <04a001c8374f$a58b1a00$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <20071205153214 DOT GI26345 AT calimero DOT vinschen DOT de> <04a801c83756$90a8b5f0$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <20071205172520 DOT GB3147 AT ednor DOT casa DOT cgf DOT cx> <04b901c83767$91e6f290$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <BAY108-W200973B554B568C4991162BE6E0 AT phx DOT gbl>
Subject:	RE: question with xargs and jar- seems to drop files.
Date:	Wed, 5 Dec 2007 18:17:15 -0000
Message-ID:	<04bd01c8376b$10881040$2e08a8c0@CAM.ARTIMI.COM>
MIME-Version:	1.0
X-Mailer:	Microsoft Office Outlook 11
In-Reply-To:	<BAY108-W200973B554B568C4991162BE6E0@phx.gbl>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On 05 December 2007 18:04, Mike Marchywka wrote:

> 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

> 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've had problems before with xargs, where it ends up generating a
command-line that is too long to spawn!

  There must be some weakness in the way xargs calculates the amount of space
available for a commandline under cygwin; I found that an effective workaround
was to give xargs the --max-chars flag with a size of around 16000 to 18000,
but depending on the size of your environment variables.

  Your mileage *will* vary, so you might need to experiment a bit.

    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -