Re: Cron <root@proxy05> /usr/local/bin/lock-wrapper fasClient "/bin/sleep $(($RANDOM % 100)); /usr/bin/fasClient -i | /usr/local/bin/nag-once fassync 1d 2>&1"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



In the past I've used copy & truncate log rotate feature.
Kinda racy though... some log bits might get lost between the copy &
truncate parts.
(on extremely loaded httpd systems)

The perk is the inode number stays the same.
So there is even less reason to HUP Apache.

-Jon Disnard

On Sat, Nov 2, 2013 at 9:46 PM, Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> wrote:
> On Sat, Nov 02, 2013 at 05:48:37PM -0600, Kevin Fenzi wrote:
>> running children writing to the logs after it. So, you can't move the
>> log as it still might have processes writing to it, so they do a
>> HUP/restart to make sure logs are not being used before rotate.
>>
>> I guess we could try switching it and see if we see any issues... if we
>> compress logs they could get corrupted, but if we don't they might be
>> ok.
>
> The workaround here is to use `delaycompress` in logrotate.
>
>
>
> --
> Matthew Miller  ☁☁☁  Fedora Cloud Architect  ☁☁☁  <mattdm@xxxxxxxxxxxxxxxxx>
> _______________________________________________
> infrastructure mailing list
> infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
> https://admin.fedoraproject.org/mailman/listinfo/infrastructure



-- 

-Jon
_______________________________________________
infrastructure mailing list
infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/infrastructure





[Index of Archives]     [Fedora Development]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux