Date: Mon, 20 Sep 1999 18:33:47 -0400 From: Christopher Michaels <ChrisMic@clientlogic.com> To: 'Langa Kentane' <evablunted@earthling.net>, FreeBSD <Freebsd-questions@freebsd.org> Subject: RE: Squid startup problems Message-ID: <6C37EE640B78D2118D2F00A0C90FCB4401105C7C@site2s1>
next in thread | raw e-mail | index | archive | help
Yes, you may need to create the log file. But you may want to check 2 thing. 1. Who owns /usr/local/squid/logs? 2. Who owns /usr/local/squid/logs/access.log (if it exists)? Once you've checked these, see if squid is changing it's effective user id to something other than root. Usually it changes to nobody/nogroup If it is you'll need to chown the dir and file(s) so that squid can access them. -Chris > -----Original Message----- > From: Langa Kentane [SMTP:evablunted@earthling.net] > Sent: Tuesday, September 14, 1999 6:16 PM > To: FreeBSD > Subject: Squid startup problems > > Whenever my server starts up I get this message from squid: > "cannot open /usr/local/squid/logs/access.log" > > How do I sort this out... do I just create the empty file access.log? > > Thanks in advance > > Langa Kentane > Manager: Network Operations > Sunshine Networks > Tel +27 82 928 1952 > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6C37EE640B78D2118D2F00A0C90FCB4401105C7C>