From:
[email protected]
This is a multi-part MIME message sent by reportbug.
Package: stunnel4
Version: 2:4.050-1
Severity: grave
Tags: patch
if stunnel just works the way it likes to, it's logfile reaches
enourmous dimensions, and after reaching 2G it just fails with no
reason.
The sample config should refer a logfile in /var/log/stunnel or so...
Allso i've noticed blockers happening after stunnel being up for a week
or two. (seems as if it isn't able to open fd's anymore or so)
This allso is resolved by a logrotate job, which restarts stunnel.
i'll append a sample file.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.20
Locale: LANG=C, LC_CTYPE=C
Versions of packages stunnel4 depends on:
ii libc6 2.3.2.ds1-13 GNU C Library: Shared libraries an ii libssl0.9.7 0.9.7d-3 SSL shared libraries
ii libwrap0 7.6.dbs-4 Wietse Venema's TCP wrappers libra ii netbase 4.17 Basic TCP/IP networking system
ii openssl 0.9.7d-3 Secure Socket Layer (SSL) binary a
-- no debconf information
/var/log/stunnel/*.log {
daily
missingok
rotate 356
compress
delaycompress
notifempty
create 640 root adm
sharedscripts
postrotate
/etc/init.d/stunnel4 restart > /dev/null
endscript
}
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)