sonriks
asked on
HPUX / reboot and crontab
Hi folks,
The past two times I've had to reboot a particular HPUX server, one of the user's crontab file in /var/spool/cron/crontabs .... (only one particular user) gets zero'ed out. All the other files in the dir remain intact. Any ideas on where to start looking for the cause?
Thanks
The past two times I've had to reboot a particular HPUX server, one of the user's crontab file in /var/spool/cron/crontabs .... (only one particular user) gets zero'ed out. All the other files in the dir remain intact. Any ideas on where to start looking for the cause?
Thanks
Maybe the user is listed in /var/adm/cron/cron.deny or not listed in /var/adm/cron/cron.allow.
ASKER
the login is listed in the /var/adm/cron/cron.allow file
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
there are no references in init.d dir to the username whose crontab file is being reinitialized.
Do you have support with hp? You might want to contact them on this one.
how much data is on this machine? Can you afford to run that find/grep from '/'?
Can you reboot again?
Thinking maybe set the permissions to read only and change the owner to root. reboot and see if anything shows up in the rc log about trying to reset/remove/touch that file.
how much data is on this machine? Can you afford to run that find/grep from '/'?
Can you reboot again?
Thinking maybe set the permissions to read only and change the owner to root. reboot and see if anything shows up in the rc log about trying to reset/remove/touch that file.
check all possible hardware logs.
I suspect a filesystem structure error for that particular file, probably borne from disk wear and following read error.
this usually happens to mail spool directories in 5 years...
I suspect a filesystem structure error for that particular file, probably borne from disk wear and following read error.
this usually happens to mail spool directories in 5 years...
ASKER
Investigation showed that there was a startup script whichpurged this particular user's crontab file.
thanks!
thanks!