[ic] expireall and server --start fail to run in crontab (was: Where is checkstat.sh?)
Wed, 28 Mar 2001 14:48:08 -0600
Quoting Jason Kohles email@example.com
>Expireall expects the config file to be in the directory where you run it,
>which could arguably considered a bug, however...
> 1,11,21,31,41,51 * * * *
>The easy fix is to change your crontab entry to:
>1,11,21,31,41,51 * * * * (cd /home/htdocs/my_space/interchange;
And it works! Thank you very much, Jason, and everyone that offered
assistance! I don't know why 'bin/expireall -r' didn't work, while
'bin/interchange' would run from cron. Now if I could only get rid of that
pesky server mail which is piling up every time cron runs 'bin/interchange'.
The -q switch at least suppresses catalog reconfig messages, but do they
need to be re-configured so often? I mean, what if someone had 20 cats
online and running bin/interchange from cron every 10 minutes (like myself)?
Of course, I want to know when the server went down and how often, but no
need to know that it is running. Perhaps there is yet a better way (or some
kind of /switch) to accomplish this in Interchange without filling the
I'll post to the 'wish list' if I don't hear from anybody.