[Buildroot] log storage strategy

[Buildroot] log storage strategy

[Sylvain LG]

Hello,

many services like to write log files.

I suppose that it could be a problem on an embedded device, since space is
limited and NAND has write limitation in time.

What is the correct strategy to deal with log?

Thank you,

Sylvain
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20150305/08cf7255/attachment.html>

[Buildroot] log storage strategy

[Arnout Vandecappelle]

On 05/03/15 10:30, Sylvain LG wrote:
> Hello,
> 
> many services like to write log files.
> 
> I suppose that it could be a problem on an embedded device, since space is
> limited and NAND has write limitation in time.
> 
> What is the correct strategy to deal with log?

 There is no single strategy that will work for everybody.

 Often the logs are put in a tmpfs so they are never committed to NAND. But then
of course you loose them when the system reboots.

 If you do write to flash, with a decent wear-levelling filesystem the write
limit is not necessarily a problem, especially if you enable some write
buffering (which defaults to 5-30 secs anyway, cfr. sysctl
vm.dirty_writeback_centisecs and vm.dirty_expire_centisecs) and rate limiting
(rsyslogd and journald have controls for that).

 And finally, you'll have to clean up old logs. You can use logrotate, or the
built-in rotation in rsyslogd and journald.


 Regards,
 Arnout
-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F