Hello,
I have noticed that by sending -HUP signal to stunnel causes daemon to exit. The problem is when stunnel is logging to a file and the file was recreated (i.e. by logrotate). I have blindly configured logrotate to send -HUP to the stunnel after the logs are rotated and awaited 'common-habbit' functionality: re-read configuration and refresh file handles. But I was supprised:
xxxx@yyyyy:/var/log# more stunnel.log.1 2005.09.27 14:07:51 LOG5[23244:3084273344]: stunnel 4.07 on xxxxxxxxxxxxxxx 2005.09.27 14:07:51 LOG5[23244:3084273344]: 500 clients allowed 2005.10.02 04:40:03 LOG3[23245:3084273344]: Received signal 1; terminating
Apparently messages are going to the 'old' filehandle and stunnel exits. Is there any workaround to this except: 1) hard restarting stunnel 2) putting stunnel in inetd
Thank you, Bohdan
On Thursday 06 of October 2005 16:59, Bohdan Linda wrote:
Apparently messages are going to the 'old' filehandle and stunnel exits. Is there any workaround to this except:
- hard restarting stunnel
- putting stunnel in inetd
3) Use syslog (the most common one). 4) Sponsor logfile rotation and/or configuration reloading on a signal. 8-) 5) Wait until I have some spare time to implement it. 6) Fork a new GPL project based on stunnel and implement it yourself.
Best regards, Mike