11 Oct
2011
11 Oct
'11
12:47 a.m.
After upgrading stunnel to 4.44, the bug has gone. So forget about this.
On Tue, Oct 11, 2011 at 12:48 AM, crocket crockabiscuit@gmail.com wrote:
If I rotate stunnel logs with logrotate and have logrotate send SIGUSR1 signal to stunnel, stunnel doesn't close and reopen a new log and hangs.
If I rotate stunnel logs and have logrotate send SIGHUP to stunnel, stunnel writes two lines to a new log but hangs after then.
It could be a CPU problem because my D525 ATOM CPU had a problematic history with other programs. But I'm not sure of this.
Can anybody else reproduce the problem?