On 20/02/2012 17:52, alexus wrote:
> what else I can do then?
Wait until tomorrow and see what happens.
> i don't need syslogd..
>
> this is vm, it runs nothing but squid, squid generates its own
> logging, so no reason to run syslogd
Well, it's up to you, but syslogd logs a lot more than the o
what else I can do then?
i don't need syslogd..
this is vm, it runs nothing but squid, squid generates its own
logging, so no reason to run syslogd
On Mon, Feb 20, 2012 at 12:47 PM, Matthew Seaman
wrote:
> On 20/02/2012 17:29, alexus wrote:
>> /var/log/squid/access.log <7J>: --> will trim at
On 20/02/2012 17:29, alexus wrote:
> /var/log/squid/access.log <7J>: --> will trim at Tue Feb 21 00:00:00 2012
> /var/log/squid/cache.log <7J>: --> will trim at Tue Feb 21 00:00:00 2012
OK -- this looks fine. It should cycle the log files overnight.
Presumably you first setup the cycling of the
s# newsyslog -n -v
Processing /etc/newsyslog.conf
Found: /etc/newsyslog-local.conf
Processing /etc/newsyslog-local.conf
/var/log/all.log <7J>: does not exist, skipped.
/var/log/amd.log <7J>: does not exist, skipped.
/var/log/auth.log <7J>: size (Kb): 4 [100] --> skipping
/va
On 20/02/2012 17:04, alexus wrote:
> s# tail -1 /etc/newsyslog.conf
> /etc/newsyslog-local.conf
> s# cat /etc/newsyslog-local.conf
> /var/log/squid/access.log squid:squid 640 7 *@T00 J
> /var/run/squid/squid.pid
> /var/log/squid/cache.log squi
s# tail -1 /etc/newsyslog.conf
/etc/newsyslog-local.conf
s# cat /etc/newsyslog-local.conf
/var/log/squid/access.log squid:squid 640 7 *@T00 J
/var/run/squid/squid.pid
/var/log/squid/cache.logsquid:squid 640 7 *@T00 J
s# ls -la /var/log/squid/
total 95672
