Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cwjcc!gatech!hubcap!ncrcae!ncrlnk!cipc1!news
From: news@cipc1.Dayton.NCR.COM (News Administrator)
Newsgroups: news.software.b
Subject: Re: News 2.11.17 breaks "batch"
Message-ID: <778@cipc1.Dayton.NCR.COM>
Date: 31 Jan 89 14:14:17 GMT
References: <1424@vsi1.COM>
Reply-To: news@cipc1Dayton.NCR.COM (News Administrator)
Organization: NCR World Telecomputing Center - Dayton, OH
Lines: 16

In article <1424@vsi1.COM> lmb@vicom.COM (Larry Blair) writes:
>There is a major bug introduced by the 2.11.17 patches to batch.c.  The
>"optimization" added to prevent having to do a full path lookup for each
>file by doing a chdir(SPOOLDIR) can cause the site.work file not to be
>properly updated when the batch exceeds the maximum size (because you
>are not the correct directory).

Yes, I was just bitten by the same "feature".  The solution is to ensure the
first argument to batch is a full pathname ($LIBDIR/batch `pwd`/filename).



-- 
Tom Bertelson				"What's so funny 'bout
Tom.Bertelson@cipc1.Dayton.NCR.COM	 peace, love and understanding?"
...!uunet!ncrlnk!cipc1!tbertels			-- Elvis Costello