Date: Tue, 22 Mar 2005 10:44:58 GMT From: Jim Hatfield <jim.hatfield@insignia.com> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/79120: stunnel tries to create pid file in non-existent directory Message-ID: <200503221044.j2MAiwUb036619@www.freebsd.org> Resent-Message-ID: <200503221050.j2MAo1UK001114@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 79120 >Category: misc >Synopsis: stunnel tries to create pid file in non-existent directory >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Mar 22 10:50:01 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Jim Hatfield >Release: 4.10 >Organization: Insignia Solutions >Environment: FreeBSD viper.isinc.insignia.com 4.10-RELEASE-p2 FreeBSD 4.10-RELEASE-p2 #1 u Jul 29 04:17:28 PDT 2004 root@viper.isinc.insignia.com:/usr/obj/usr/s s/VIPER i386 >Description: portupgraded from stunnel 4.05 to 4.07. Saw the warning about rc_subr and added the stunnel_enable="YES" to /etc/rc.conf. Spotted that it wanted to put its pid file in /usr/local/var/stunnel rather than /var/run as before. However this directory does not exist - wasn't created by the installation. >How-To-Repeat: portupgrade from stunnel 4.05 to 4.07 and check to see if /usr/local/var/stunnel has been created. Start and stop stunnel and see the pidfile warning. >Fix: Added 'stunnel_pidfile="/var/run/stunnel.pid"' to /etc/rc.conf and 'pid = /var/run/stunnel.pid' to /usr/local/etc/stunnel/stunnel.conf. Now works as before. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200503221044.j2MAiwUb036619>