Gerald Waugh wrote: > Are, you sure it is the GLIBC patch?
I'm not _sure_, but others believe so; that's what the concensus was when the patch was issued, and that's what Michael still thinks. > I have RaQ3s and RaQ4s running with no issues. As did we, until we started running the "subscribe me" program to send a lot of opt-in emails. We know that "subscribe me" taxes the system. But it's been finished for days now and we're still seeing extremely low memory. I thought I'd have to reboot this morning, but I didn't; the RaQ3 survived. Let's see how it does all day today and tomorrow morning when cron.daily starts; I've written a small cron.hourly job to send me the output of /proc/meminfo. > How do you know its not one of the cron jobs? Well it probably is something in one of the cron jobs, but as Michael says, it didn't happen until after the glibc update. > What are you running in cron daily, that might cause the problem? logrotate, makewhatis.cron, ntpdate.auto, slocate.cron, tmpwatch, vacuumdb, webalizer.pl Or in other words, all the standard stuff plus webalizer.pl. Jeff -- Jeff Lasman <[EMAIL PROTECTED]> Linux and Cobalt/Sun/RaQ Consulting nobaloney.net, P. O. Box 52672, Riverside, CA 92517 voice: +1 909 778-9980 * fax: +1 909 548-9484 _______________________________________________ cobalt-developers mailing list [EMAIL PROTECTED] http://list.cobalt.com/mailman/listinfo/cobalt-developers
