RE: [cobalt-users] Mem Leak???

["Travis M. Best" <sysadmin@xxxxxxxxxxxx>]

So this is normal
Before Cron Job @ 1:30pm

[root /etc]# free
             total       used       free     shared    buffers
cached
Mem:        517112     214076     303036     123380      38388
85976
-/+ buffers/cache:      89712     427400
Swap:       131448          0     131448

[root /etc]# date
Tue Jan 14 13:29:02 EST 2003


After Cron Job @ 1:30pm

[root /etc]# date
Tue Jan 14 13:32:06 EST 2003

[root /etc]# free
             total       used       free     shared    buffers
cached
Mem:        517112     362188     154924     124400      85524
174908
-/+ buffers/cache:     101756     415356
Swap:       131448          0     131448



-----Original Message-----
From: cobalt-users-admin@xxxxxxxxxxxxxxx
[mailto:cobalt-users-admin@xxxxxxxxxxxxxxx] On Behalf Of Bruce
Timberlake
Sent: Tuesday, January 14, 2003 1:04 PM
To: cobalt-users@xxxxxxxxxxxxxxx
Subject: Re: [cobalt-users] Mem Leak???

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> The reason I started to research in to this is because the sever
> started sending me e-mails with out of memory error

Cron will start _all_ jobs scheduled for a certain time slot at the 
same time.  If you _are_ running your job at the same time cron is 
trying to fire off something huge like split_logs, you will have 
memory problems, especially if your logfiles are very large.  Try 
staggering your job to before or substantially after the 'main' cron 
jobs for the system run.

- -- 
Bruce Timberlake

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+JFD0vLA2hUZ9kgwRAqxwAJwIvEt5Z4puff4ppKXWZ+az6B3/ZwCePZJF
EK7r7qjOf+BFHqmyoqbNtss=
=Olgn
-----END PGP SIGNATURE-----

_____________________________________
cobalt-users mailing list
cobalt-users@xxxxxxxxxxxxxxx
To subscribe/unsubscribe, or to SEARCH THE ARCHIVES, go to:
http://list.cobalt.com/mailman/listinfo/cobalt-users