I think logrotate is spawned from cron; if so it should re-read the config
when it runs next.
Check your crontab --in general, if you edit a conf for a service that is in
/etc/init.d/... then
you need to restart that service.
ben
On 1/31/07, Matthew Jarvis <[EMAIL PROTECTED]> wrote:
Thanks Mark...
I made some changes to see what compress will do for me, plus trimmed
down the # of logs from 4 to 2 - I'll see what happens...
Do I have to do anything else to tell it to use this updated conf file,
or will it see the changes already?
Thanks again...
Matthew S. Jarvis
IT Manager
Bike Friday - "Performance that Packs."
www.bikefriday.com
541/687-0487 x140
[EMAIL PROTECTED]
Mark Turner wrote:
> Its fairly easy to limit log file size if you use logrotate. In the
> configuration specification for each log you can give it a size
> parameter, which will rotate the log when it hits that size.
>
> Example:
> # sample logrotate configuration file
>
> /var/log/messages {
> rotate 5
> weekly
> size=100k
> postrotate
> /sbin/killall -HUP syslogd
> endscript
> }
>
>
> On 1/31/07, Matthew Jarvis <[EMAIL PROTECTED]> wrote:
>
>> Is there a way to globally set how big log files can get?
>>
>> i.e. maillog, maillog.1, maillog.2
>>
>> I was hoping that this global setting would also control apache,
>> postgres etc but that's prolly asking too much...
>>
>>
>> --
>> Matthew S. Jarvis
>> IT Manager
>> Bike Friday - "Performance that Packs."
>> www.bikefriday.com
>> 541/687-0487 x140
>> [EMAIL PROTECTED]
>> _______________________________________________
>> EUGLUG mailing list
>> [email protected]
>> http://www.euglug.org/mailman/listinfo/euglug
>>
_______________________________________________
EUGLUG mailing list
[email protected]
http://www.euglug.org/mailman/listinfo/euglug
_______________________________________________
EUGLUG mailing list
[email protected]
http://www.euglug.org/mailman/listinfo/euglug
