: We're starting to get strange things happening with some long-standing cron
: scripts - it looks like cron is starting up the jobs (which all run from
: shell scripts) twice at virtually the same time.
Oh yes. My guess is that someone edited the scripts located
in the /usr/spool/cron/crontabs directory and left the backups
in there. When cron comes along looking for work, it executes
both the edited and the backup version.
It is also possible to have more than one copy of cron running.
However, you really have to work to do that and I assume that
you rebooted to clear any such atroscities. If rebooting still
starts two copies, then look in /etc/rc2.d/ directory and see
if there aren't two copies of S75cron. Leaving editor backups
in this directory will also cause things to be run twice.
Incidentally, the politically correct way to modify cron scripts are to:
login: root # It's nice to be root.
crontab -l -u uucp > cron.uucp # Save current crontab for uucp.
cp cron.uucp cron.uucp.old # Backups are nice.
vi cron.uucp # Make your changes.
crontab -u uucp cron.uucp # Reload the modified script.
# It will complain if errors are found.
The last crontab command copies the modified script into the
/usr/spool/cron/crontabs directory and informs cron that things
# Jeff Liebermann Liebermann Design 150 Felker St #D Santa Cruz CA 95060
# 408.699.0483 digital_pager 73557,2074 cis [don't]