cron goes mad?

[Mark Neidorff]

On Tue, 13 Jan 2004, Stephen Walton wrote:

> Has anyone else seen output from 'ps -faxwl' like this:
> 
> 1     0  6366     1  16   0  2236  536 schedu S    ?          0:00 crond
> 1     0 16115  6366  16   0  5456 1256 do_for D    ?          0:00  \_ CROND
> 5     0 16116 16115  16   0  5456 1256 coredu D    ?          0:00  |   \_ CROND
> 1     0 16119  6366  17   0  5456 1256 do_for D    ?          0:00  \_ CROND
> 5     0 16120 16119  17   0  5456 1256 coredu D    ?          0:00  |   \_ CROND
> 1     0 16123  6366  17   0  5456 1256 do_for D    ?          0:00  \_ CROND
> 5     0 16124 16123  17   0  5456 1256 coredu D    ?          0:00  |   \_ CROND
> 
> 
> I've deleted several additional lines.  The load average on this system 
> is 30 as I write this.  Notice that the second of each pair of jobs 
> seems to be in the process of doing a core dump, which is why they are 
> unkillable.
> 
Is there sufficient disk space for the core dumps to complete?  That could 
be part of the problem.

Mark

-- 
Those who get too big for their britches will be exposed in the end.