Re: [PLUG] Error when clamscan runs as cron job

[Rich Kulawiec <rsk@gsp.org>]

I find myself wondering if the reason clamscan can't create the temporary
directory is because it already exists -- that is, because it was created
shortly earlier by the same process or by a fork of it.  If that's correct,
then that would explain why clamscan complains about it, but then proceeds
to run anyway.  This may be related to your observations about memory
exhaustion and multiple processes: I wonder if something is going awry
when the job is launched via cron and that the form that takes involves
either extra invocations or gratuitous forking.

Of course this is just speculation and may be wildly wrong.  But it might
be possible to rule this line of reasoning out by (a) manually launching the
scan from cpanel and simultaneously using ps (or top) to watch the
process list and (b) automatically launching the scan from cron and
also simultaneously using ps (or top) to watch the process list.  In theory,
these two sets of observations should be quite similar, in which case
my speculation is probably wrong.  But if they're different, then maybe
this suggests a direction for further investigation.

---rsk

___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug