Date: Fri, 27 Feb 2004 07:39:54 +0100 From: Thomas-Martin Seck <tmseck@netcologne.de> To: Wladimir Mutel <mwg@isd.dp.ua> Subject: Re: FreeBSD Port: squid-2.5.4_10 Message-ID: <20040227063954.GA1042@laurel.tmseck.homedns.org> Resent-Message-ID: <20040227131639.707.qmail@laurel.tmseck.homedns.org> In-Reply-To: <403DD9B6.7050505@isd.dp.ua> References: <403DD9B6.7050505@isd.dp.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
* Wladimir Mutel (mwg@isd.dp.ua): > Having upgraded our squid by portupgrade to 2.5.4_10 (obtained by cvsup), > we noticed the following behaviour (in cache.log) : > > 2004/02/24 15:35:20| /var/run/squid.pid: (13) Permission denied > 2004/02/24 15:35:20| WARNING: Could not write pid file > > May be this is due to introduction of 'squid' user that is set by 'su' > before starting squid itself. Yes, this is the cause of your problem. > How should we resolve this problem ? Should we change the location of pid > file, or should we go other way ? The default location of the pid file is $PREFIX/local/squid/logs/squid.pid. You can use that or any other directory that is writable by the squid user and supply it in squid.conf as pid_filename. Of course you can always replace the supplied squid.sh with your own script where you start squid as root and let it drop privileges itself, then you should be able to continue using /var/run to store the pid file. Best regards, -- Thomas-Martin Seck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040227063954.GA1042>