Thanks for this.
Is there any way to get a dump of historical memory usage so I can try to see what is causing the high memory drain, and what processes were running at the time?
Thanks
John
On Thursday, Jan 30, 2003, at 15:49 Europe/Dublin, Bruce Timberlake wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1I am receiving a low memory error each morning at 4:15am. The box is a Cobalt RaQ4r with 512MB RAM.Most likely it is logrotate/split_logs that is causing the problem. If you only get the one message, and not continual all day, I wouldn't worry about it. The log splitter is a notorious hog, and if it's running for more than 15 minutes (enough that Active Monitor 'catches' it), you must have some fairly large log files.running top does not give any pointers as to what is causing the low memory error?By the time you're checking it, the high memory use is over... if you were logged in at 4am and running 'top' you'd see it all happening. - -- Bruce Timberlake http://www.brtnet.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+OUl7vLA2hUZ9kgwRAppwAJ9wrvj1fG4rxJoGuj/EbG2GhAzSlgCbBCZC 9z5q2r8L7qhFTvz0TskMHV0= =vNWx -----END PGP SIGNATURE----- _______________________________________________ cobalt-developers mailing list [EMAIL PROTECTED] http://list.cobalt.com/mailman/listinfo/cobalt-developers
_______________________________________________ cobalt-developers mailing list [EMAIL PROTECTED] http://list.cobalt.com/mailman/listinfo/cobalt-developers
