within the periphery of growing it, is that at some stage the question whether a central logging of various hard / software layers would not be beneficial. that argument is supported by the fact that my nslu2-operated devices to participate only through a memory stick will result in an excessive logging to local io wait states would. attached to one of these devices to a USB hard drive is nothing wrong events, logging messages and protocols in this unit using UDP transfer.
implementation can be found as a free [open source] a syslog server syslog-ng under linux . the installation is under slugos / be native than under the Optware package feed given, and the implementation of which runs unspectacular.
# ipkg install syslog-ng
# / etc / init.d / syslog stop
# ln-s / opt / etc / init.d / opt_syslog / etc/rc3.d / S02syslog
the syslog-ng server listens on port 514 now [default syslog udp port] events to syslog-ng clients. it is recommended that certain adjustments should be logged in / opt / etc / syslog-ng / syslog-ng.conf as to what to make. On the client side is / etc / syslog.conf file by only following extended messages.
DESTINATION = "remote"
REMOTE = nwal002: 514
in connection with syslog-ng recommends the use of logrotate, which is also by default in the Optware feed offered as a package. / Opt / etc / logrotate.conf is configured in my case. [Rotate messages older than 5 days]
nocompress
/ opt / var / log / * {5
rotate size 100k
/ opt / etc / init.d / stop opt_syslog
/ opt / etc / init postrotate. d / opt_syslog start
}
include / opt / etc / logrotate.d
endscript and rotate the running as a cronjob
15 0 * * * / opt / sbin / logrotate / opt / etc / logrotate.conf> & / dev / null
login from now on my nslu2-devices and my d-link router everything centrally.
0 comments:
Post a Comment