On Mon, Mar 12, 2001 at 01:52:00AM -0800, Sean Coyle wrote:
> Also,
>
> Another good thing to note:
>
> I was having a serious problem with qMail delivering mail to end users,
> however, mail was being stored in the queue (this was quite some time ago
> now). I had made a few changes to a crontab entry the day earlier, however;
> everything was seemingly running normally with qMail.
>
> Anyway, it turns out that I was running an INTENCE CRON job every single
> second,
Are you sure about that? All the crons I've seen only let you run a
job at most, once per minute. How did you get cron to run something
once per second?
If the job runs at most once per minute, it's hard to imagine how it
would consume all available resources such that qmail stopped
delivering.
(Of course it's not impossible, but just unlikely: a job that runs for
an hour that is started once per minute may well have a serious
resource impact).
> Just an example of how a completely unrelated system event can alter the
> performance of other items... (hrrmmm chaos mathematics anyone?)
Most likely the problem is much simpler and more directly related. As
the earlier poster suggested a systematic process of elimination is
the best approach.
Regards.
