[ Scott D. Gregory writes: ]
>
> > From: Dave Wolfe <dwolfe@risc.sps.mot.com>
>
> > [ Jerry Peek writes: ]
> > >
> > > On 3 February, "Scott D. Gregory" <Scott.D.Gregory@afpubs.hq.af.mil> wrote:
> > > > Can I run bounce-remind from majordomo's crontab?
> > >
> > > Sure. Here are the lines from my "majordom" user's crontab. I also
> > > run "bounce -expire" once a week to nuke old entries:
> > >
> > > 13 2 * * * MAJORDOMO_CF=/usr/local/majordomo/majordomo.cf /usr/local/majordomo/bounce-remind
> > > 44 4 * * 0 /usr/local/majordomo/bin/bounce -expire /usr/local/majordomo/lists/bounces
> > >
> > > Notice that I'm setting the MAJORDOMO_CF environment variable. If I
> > > didn't do that, the script wouldn't be able to find the configuration file
> > > (because most environment variables aren't propagated into cron jobs).
> >
> > I thought that's why (well, at least partly why) all the Mj stuff was
> > run via wrapper: consistent environment.
> >
>
> What would you suggest??
Make sure bounce-remind and bounce are in the same directory with
wrapper and use:
13 2 * * * /usr/local/majordomo/wrapper bounce-remind
44 4 * * 0 /usr/local/majordomo/wrapper bounce -expire /usr/local/majordomo/lists/bounces
This also means that these need not be in the "majordom" user's crontab.
Caveat: I don't use bounce and it's kin, so this is all theory and not
experience.
--
Dave Wolfe
References:
|
|
