Control: tags -1 moreinfo
Hi,
are you able to reproduce this issue with version 3.14.0-2 or newer
and a recent squid version?
logrotate should nowadays report more detailed if a postrotate script fails.
Best regards
Christian Göttsche
Paul,
I checked on the server today and the logs hadn't rotated :-( . The server was
still
writing to /var/log/squid3/access.log.1 . I ran squid3 -k rotate and everything
rotated
like it should have. The contents of the /etc/logrotate.d/squid3 is now:
#
# Logrotate fragment for squid3.
I've modifying the line a bit and running it from bash. Running ' test ! -e
/var/run/squid3.pid || echo File Exists ' prints File Exists. Unless
logrotate is using a different shell, it should work. This file is also exactly
the same as another Squid server I had running that was using Debian
On Fri, Jul 30, 2010 at 11:10:35AM -0500, jblack-b...@morrislaing.com wrote:
I've never filed a bug report
before this. Is this something I should notify the maintainer for
Squid3 about?
I can change this bug into being one against the squid3 package if you
like. If they eventually find that
Package: logrotate
Version: 3.7.1-5
Severity: normal
This system is running under VMware Server.
The problem occured after we upgraded squid to the lenny-backports version
(3.1.3-2). Log files currently rotate, but it appears that squid3 -k rotate
is never run. I check on the server about 8 AM
On Thu, Jul 29, 2010 at 09:05:30AM -0500, Jonathan Black wrote:
postrotate
test ! -e /var/run/squid3.pid || /usr/sbin/squid3 -k rotate
endscript
The problem is probably that exclamation mark. If your /bin/sh is bash
it probably will not like it, as it's also
6 matches
Mail list logo
