Hi,
To break the vacation.pl loop there is a script: break-smrsh-loop.pl
that monitor ("run in cron or crontab") user quota and break the .db -> Null return issue.
Therefore effectively break the mail loop.
>>>>>>>>>>>>>>>>>>>
Brian have included
break-smrsh-loop.pl
in SVN
But older BQ built might not have this script running.
Cheers
patrick
On Thu, 10 Jan 2008 17:42:42 +0100
Michael Stauber <bq (at mark) solarspeed.net> wrote:
> Hi Gerald,
>
> > We have a server which keeps spawning vacation.pl
> > The app takes 100% of CPU cycles.
> > It spawns many instances, for the same users.
> >
> > Currently using a cron.quarter-hourly job to kill instances of
> > vacation.pl
> >
> > #!/bin/bash
> > # fix to kill vacation.pl
> > kill `pidof -x vacation.pl`
> > exit 0
> >
> > This keeps the server running, but not a good idea!
>
> I've seen that before - once. Check with "ps auxwf" and see which user owns
> the vacation.pl processes.
>
> Next check if the user or the site he belongs to is over quota.
>
> Additionally: Check the .forward file in that user's home directory. I've once
> seen a box where a user had both autoresponder and vacation message turned
> on, plus it was configured to email a copy to himself. That create a pretty
> nasty loop, although there are provisions built in to prevent that. Somehow
> they failed in that particular case.
>
> --
> With best regards,
>
> Michael Stauber
>
>