stunnel 4.14 released
The ChangeLog entry for stunnel 4.14: Version 4.14, 2005.11.02, urgency: HIGH: * Bugfixes - transfer() fixed to avoid random stalls introduced in version 4.12. - poll() error handing bug fixed. - Checking for dynamic loader libraries added again. - Default pidfile changed from $localstatedir/run/stunnel.pid to $localstatedir/stunnel/stunnel.pid. - Basic SSL library initalization moved to the beginning of execution. * Release notes - This is an important bugfix release. Upgrade is recommended. sha1sum for stunnel-4.14.tar.gz: b2edb3a2473367f2a9f04a877adcb332483a5267 Home page and download: http://stunnel.mirt.net/ Best regards, Mike
Hello, Michal Trojnara wrote:
- Default pidfile changed from $localstatedir/run/stunnel.pid to $localstatedir/stunnel/stunnel.pid. For a system-wide installation this conflicts with the Linux FHS, which specifies "Applications must generally not add directories to the top level of /var".
At minimum the path should be reasonably easily configurable, which is what the attached patch does: it allows ./configure CPPFLAGS=-DPIDFILE='\"/my/desired/path\"' Currently it is necessary to use make CPPFLAGS=-DLIBDIR=...\ -DCONFDIR=...\ -DPIDFILE=... always specyfing all three variables. See also (info '(automake)Flag Variables Ordering'). Thanks, Mirek
"Miloslav Trmac" <mitr@redhat.com> wrote:
- Default pidfile changed from $localstatedir/run/stunnel.pid to $localstatedir/stunnel/stunnel.pid. For a system-wide installation this conflicts with the Linux FHS, which specifies "Applications must generally not add directories to the top level of /var".
You're right.
At minimum the path should be reasonably easily configurable
./configure --localstatedir=/var/run Is it reasonable? BTW: According to some standards /var/run can be cleaned at system startup. What is the best directory for stunnel chrooted environment? Best regards, Mike
participants (2)
-
Michal Trojnara -
Miloslav Trmac