On Sun, Jan 30, 2005 at 03:06:03PM -0500, Brian Bruns wrote: >Up until Cygwin 1.5.12, the return code from stuff like clamscan was >being passed back to Windows, so programs outside of Cygwin could call >the binary and tell weather or not the program found a virus in the >file it scanned. > >Now, in the latest snapshots, that is no longer the case. See example >below using freshclam, but also applies to the other apps:
The odd error return was unintentional but there will be a change in cygwin 1.5.13 -- the error return will match what you'd expect for a unix program. So, this is what you should expect: c:\>sh -c 'exit 1' c:\>echo %errorlevel% 256 This will be the behavior of the next snapshot. cgf -- 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/
