Xen
2017-05-20 14:20:13 UTC
Hi,
I have an older Synology installation of openvpn (server). There is some
shell script starting openvpn. I am using a client connect script in the
config. Sometimes I find that the server won't restart when I tell it to
(it first sends regular kill messages then if that does not work I send
kill -9), and then I find that the client connect script has actually
been hanging.
That is very weird because it only tries to send an email message using
some PHP script. Of course that could stall.
The status code for the process was "S" which means interruptable sleep.
I was just wondering if anyone ever "battled" with something like this
and what a good solution would be.
I can:
- kill any client scripts in my restart script
- always run the PHP email script in some background process to ensure
it doesn't hang the main process.
I just want to not have to look at these problem cases anymore lol.
I guess I should just background the thing?
Regards.
I have an older Synology installation of openvpn (server). There is some
shell script starting openvpn. I am using a client connect script in the
config. Sometimes I find that the server won't restart when I tell it to
(it first sends regular kill messages then if that does not work I send
kill -9), and then I find that the client connect script has actually
been hanging.
That is very weird because it only tries to send an email message using
some PHP script. Of course that could stall.
The status code for the process was "S" which means interruptable sleep.
I was just wondering if anyone ever "battled" with something like this
and what a good solution would be.
I can:
- kill any client scripts in my restart script
- always run the PHP email script in some background process to ensure
it doesn't hang the main process.
I just want to not have to look at these problem cases anymore lol.
I guess I should just background the thing?
Regards.