- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- cron hunt - round 3
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2002 06:08 AM
01-24-2002 06:08 AM
find . -name 'cron' and picked through the results.
Comments would be appreciated.
Regards,
Bill
D. Allen nailed round 2. There was a cron script that referenced a directory that had been removed. There were chmod commands in there that whacked other directories. Thanks to all who responded.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2002 06:11 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2002 06:13 AM
01-24-2002 06:13 AM
Re: cron hunt - round 3
Have you looked in /var/spool/cron/crontabs - file name is same as the user you are logged in as.
Hilary
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2002 06:17 AM
01-24-2002 06:17 AM
Re: cron hunt - round 3
Crontabs are stored in /var/spool/cron/crontabs. You should not edit these files directly.
You have 2 options. "crontab -e" makes a temp copy of your crontab, puts you into edit mode on the temp copy (generally with vi), then replaces the original in /var/spool/cron/crontabs.
The preferred method of editing a crontab is to use "crontab -l >crontab.cpy" to make a copy of the crontab. Edit that file then use "crontab crontab.cpy" to make it active.
man crontab for more info.
Before doing any edits on your crontab I'd suggest you back it up. For root, a number of people do:
cd /var/spool/cron
cp -p crontabs/root root.crontab
Personally, as the admin of the box, I like to backup all the crontabs:
cd /var/spool/cron
mkdir crontabs.bak
cp -p crontabs/* crontabs.bak
Darrell
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-24-2002 06:46 AM
01-24-2002 06:46 AM
Re: cron hunt - round 3
One other suggestion is to use cron to back itself up:
0 0 * * * crontab -l > /usr/local/etc/crontab
then you haven't got to worry about it.
Rgds, Robin.