Unsupported Windows command line options - #620
Conversation
|
We used to have something similar already, but it was removed by afa978f. That commit message said "Unsupported system calls will error appropriately.". Does that not work sufficiently? |
|
No. See the current behavior. Option -R provides a FATAL message but the routine is not correct. Option -u provides a FATAL message but the OS user exists so the message is not correct too. Option -d doesn't even provide a FATAL message and terminates without a suitable message. |
This is from
Okay, this could be improved.
This is weird. I would expect that it would fail at the |
|
I'm back to this issue.
Lines 965 to 978 in cffa192
Ooops. I didn't provide the whole log. (Those messages were from the terminal.) Log contains When I replace Do you agree applying these error messages for usability purposes? |
For |
Option --user is not supported on Windows. Despite of having a FATAL message, it is not accurate. Let's provide the real cause of why the service did not start.
Option --daemon is not supported on Windows. Despite of having a FATAL message, it is not accurate. Let's provide the real cause of why the service did not start.
7f89309 to
4bc1ffe
Compare
Provide suitable FATAL messages for unsupported options on Windows.