Charles Bailey wrote:
> > I always run my perl builds in batch so I can easily trap any errors that
> > occur with the text, etc., etc., and I never ran into those "Warning: Executing
> > in batch mode... " messages before. I think they are bogus, as there has never
> > been a file locking problem before, or is this the joy of 5.6sm?
>
> Prior to this patch, Configure.Com would fail (either die or get the wrong
> answer in some tests) because of SYS$OUTPUT redirection in batch mode and
> the default to verification on. The warnings are just a hint that the
> output which would have been lost is now directed to a new version of the
> log file, since the job controller has an exclusive lock on the current
> version. (This is all usually specific to batch mode; in interactive mode
> we just assign another channel to SYS$OUTPUT, in the blithe assumption that
> someone hasn't @Configure/Out=config.log
>
> Regards,
> Charles Bailey [EMAIL PROTECTED]
Which patch?
Peter Prymmer
