Web lists-archives.com

Re: Unattended upgrade does not report errors via the exit code

On 7/4/2018 6:25 PM, David Stacey wrote:
On 04/07/18 19:59, Ken Brown wrote:
On 7/3/2018 1:55 PM, R. Diez via cygwin wrote:
I tried printing $? from a Cygwin shell afterwards, and %ERRORLEVEL% in a Windows console, and it always showed an exit status of 0.

setup is a Windows program, not a Cygwin application, so I don't think you can expect $? to contain its exit status.  I don't know enough about Windows programming to know what would have to be changed in the setup sources to support %ERRORLEVEL%.

%ERRORLEVEL% is the return code from the last programme or script to execute. Provided that setup exits with zero on success and non-zero on an error condition, there's nothing extra to be done.

According to https://stackoverflow.com/questions/334879/how-do-i-get-the-application-exit-code-from-a-windows-command-line/11476681#11476681, that's not true for windowed applications, but it is true if the application is started via 'start /wait'. I haven't tested this.


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