When run, as root,
# crontab -e <user>
crontab sends
caroot[many nulls]<user>[a few more nulls]
to
/var/adm/cron/FIFO
This will not trigger cron to reread the file. cron must either be
restarted (SIGHUP has no effect) or you must su to the user and do
"crontab -e" from there to get the updated cron file to be
acknowledged. SunOS 5.X's crontab command sends, when run as root,
ca<user>[many nulls]<user>[a few more nulls]
to
/etc/cron.d/FIFO
and HP-UX 10.0 does the same. The fact that the <user> in question
appears twice seems to make the difference.
Is this a bug in DU 4.0B (w/ patch rev 4)? If so, does anyone
know when it will be fixed? If not, why is crontab -e <user> supported
if it isn't supposed to work?
____________________________________________________________________
/ Brian C. Hill bchill_at_ucdavis.edu (530) 753-0358 \
| Systems Programmer University of California, Davis |
| Graduate School of Management & GIS Research Lab |
Received on Sun Sep 14 1997 - 02:33:52 NZST