David L. Anselmi wrote:
> Hi,
>
> I notice this behavior in openvpn 2.0.6, except that it is what gets
> logged after running:
>
> /etc/init.d/openvpn stop
>
> Could it be that your bug reports normal behavior when openvpn
> receives a TERM signal?
No. The problem happened when no one was doing anything at all with the
daemon. It is possible that the TERM signal also triggers the same
behaviour.
> In that case could you close the bug?
That is not the case. Then again, I didn't get this problem lately.
Maybe it was solved by upstream?
Checking again, sending SIGSTOP to the process, followed by SIGCONT, I
get "Interrupted system call", but openvpn does not terminate. I think
we can say that this bug is resolved, probably by upstream.
Shachar
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
