- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- crontab problem
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
Discussions
Discussions
Forums
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
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
тАО09-25-2006 06:42 AM
тАО09-25-2006 06:42 AM
ignores crontab "hour" value. The story is that we modified crontab (crontab -e) hour
field to be 1-22 but cron continues to execute the job on 24 hour cycle. I wonder if
restarting cron daemon will fix this problem? Any side affects to restart cron as this is our primary production system?
By the way, HP has a new cron patch but I can't install it to the production server now.
Thanks in advance,
Lynn
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2006 06:47 AM
тАО09-25-2006 06:47 AM
Re: crontab problem
After you modified the crontab file, did you run crontab
This forces a re-read of the new crontab file
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2006 06:48 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2006 06:53 AM
тАО09-25-2006 06:53 AM
Re: crontab problem
Restart cron by:
# /sbin/init.d/cron stop
# /sbin/init.d/cron start
Nothing should be affected.
PCS
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2006 06:55 AM
тАО09-25-2006 06:55 AM
Re: crontab problem
For what it's worth, the patch, PHCO_35331, does not require a reboot to install. You can see this in the patch notes, or simply by the designation "PHCO". "PHCO" are command patches and generally do not require a reboot.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2006 07:04 AM
тАО09-25-2006 07:04 AM
Re: crontab problem
shows the crrect entry there. I can not install the patch because the server's environment is freezed for the production.
I'll restart the cron daemon to see ...
Thanks!
Lynn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-25-2006 07:08 AM
тАО09-25-2006 07:08 AM