When Calibre fails from a command line, it doesn't complain or set the RC

[JWGreenley]

When Calibre is started or stopped from the command line, if it has an error,, it just doesn't complain or set an error / return code. In the example below, I'm using a known issue stemming from Windows 10's security "enhancements" where the calibre --s command doesn't work from a users command window, IF Calibre was started via the Task Scheduler.

C:\WINDOWS\system32>"D:\Program Files\Util\pslist64.exe" calibre -nobanner
Process information for HP-PRIME:

Name Pid Pri Thd Hnd Priv CPU Time Elapsed Time
calibre 17768 6 21 712 254852 0:00:35.515 8:20:31.698
calibre-parallel 29200 8 1 163 10084 0:00:00.140 8:17:01.612

C:\WINDOWS\system32>calibre --s

C:\WINDOWS\system32>echo %errorlevel%
0

C:\WINDOWS\system32>"D:\Program Files\Util\pslist64.exe" calibre -nobanner
Process information for HP-PRIME:

Name Pid Pri Thd Hnd Priv CPU Time Elapsed Time
calibre 17768 6 21 712 254852 0:00:35.578 8:21:10.877
calibre-parallel 29200 8 1 163 10084 0:00:00.140 8:17:40.791

No complaint, and the return code is set to zero.
I've noticed similar behavior if I start Calibre and it encounters an error. Again, it just dies without a whimper.

My concern is not the failure. I just used it as an example. I just would like some way to verify that the command was properly executed or encountered an error.

Thanks!

[davidfor]

Is the calibre that is run from the Task Scheduler running under the same user?

When I use "calibre-debug -s", and no calibre is running, I get:

C:\Users\davidfor>calibre-debug -s
Failed to contact running instance of calibre
Failed to connect to Listener at: \\.\pipe\CalibreGUI-davidforx with error: QLocalSocket::connectToServer: Invalid name

That has my username as part of the listener name. If the running calibre instance is in a different user, then the listener will be different and this won't find it.

And I don't consider the above to be an error. The message could be cleaner, but, that is a valid result when there is nothing to shutdown. If the listener was found and the shutdown didn't happen, that would be a different matter.

[DNSB]

One question is why the OP is using --s when the documentation shows a single dash for the one character commands? I.e, -s or --shutdown-running-calibre work to kill Calibre on my system but --s does nothing.

On another hand, quite a few of the command line options do not seem to do anything on a Windows system (i.e. -h or --help, --version) unless I use calibre-debug instead of calibre.

[JWGreenley]

I guess my concern is that when Calibre commands fail, it doesn't seem to set the %errorlevel% so there's nothing to test.

Meanwhile, I'll see if Calibre-debug or the single hyphens fix the immediate issue.

THANKS!