"Michael D. Schleif" <[EMAIL PROTECTED]> writes: > Vic Berdin wrote: > > > > I need to manage /var/log/wtmp data log on a regular basis (preferably > > using a cron triggered binary/script). > > As other mail archive trails suggests, A C program that will truncate it > > must be created. It can be done but, > > what do you guys have to say about it? How do LEAF users manage > > /var/log/wtmp? > > What is your real problem? > > Generally, on a LEAF firewall, if wtmp grows by mB per day, then you > have a problem; and, the real problem is not wtmp.
BTW, note that on Bering 1.0-rc3 /var/log/wtmp doesn't exist at bootup, and unlike /var/log files under the control of syslog, wtmp won't be written to unless it exists. Thus 'last' will just error if you run it. The solution is to put 'touch /var/log/wtmp' in one of the startup scripts. On my systems I put that in the 'start' section of /etc/init.d/sysklogd, since that's the point at which the other /var/log files get created. In his response to my bug report, Jacques stated that in the next version of Bering, /etc/init.d/rcS will contain the command somewhere. -- Dan Harkless [EMAIL PROTECTED] http://harkless.org/dan/ ------------------------------------------------------- This sf.net email is sponsored by: Jabber - The world's fastest growing real-time communications platform! Don't just IM. Build it in! http://www.jabber.com/osdn/xim ------------------------------------------------------------------------ leaf-user mailing list: [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
