Hello. I am sorry, this is a double post: i first used the Github repo discussion tab but realized the actual discussion is happening here :)
Here is my question :
I am currently using version 2.10.3.
I notice that service start and stop work fine : my executable, that takes quite a long time to stop (I added Sleep() calls to debug its termination and it takes more than 10 sec), goes to the end of the stopping sequence with no issues.
However, when Windows is asked to shut down (Windows 10 1909), it seems the child processes are killed before their closing sequence is completely performed.
I have read on this : https://www.howtogeek.com/282062/control-how-long-windows-waits-before-killing-apps-at-shutdown/
that Windows enforces a hard limit on executable shutdown time that can only be set through registry but it is a bit unclear to me. I also read about the pre-shutdown even but am not sure whether WinSW deals with it (the source code, at least in the 2.x branch, does not seem to use it)
Can you please shed some light on what I must do, both in my code/config and perhaps in Windows registry, to make sure my child processes are not forcefully terminated upon normal system shutdown ?
Thank you very much (and sorry for my non native English :) )
Hello, I am using WinSW 2.11.0 and configured to have a log mode of “roll-by-size-time”. Every time our log rolls over, we are encountering an exception - The process was terminated due to an unhandled exception. Exception Info: System.ObjectDisposedException: Cannot access a closed file.
I am assuming the closed file it refers to is the log file. The thing is, the service is running fine, thinking that it exits and tries to start a new one. Just wondering if this is a known issue and if there is a possible resolution to it? Thanks!
The ourmonitoring service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.
Hi Team, Good afternoon, I am trying to use the WINSW 2.11.0 and conducted vulnerability check against the WINSW2.11.0 so found out a vulnerability and please find the below URL of the Vulnerability.
Is there any possibilities to fix it in next release ?