Dear fellow Bering-users,
I had my Bering system up and running for close to
three days on arow without my supervision, and with no
access from any local network during that time, but
the Bering-linux was constantly stressed by regular
respawning due to a removed graphics card (cf. the
thread on "inflating wtmp".) Essentially, the
only change from the ready made floppy image, was that
I arranged for log rotation at 06:42 and 16:42 each
day.
When etablishing contact today, I observed every
active
logfile to be time stamped 06:42 or with 14:25, the
time I resumed contact with Bering. However, every
other rotated logfile -- be it compressed or not --
had a time stamp 07:45 and size zero. This alarms me
slightly more than slightly (sic!). Is this phenomenon
one of those infamous features we have to live with,
or did I happen to activate some unforeseen case of
daemon interaction, of which I had not heard of
beforehand?
Best regards
Mats E Andersson
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/
