- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - HP-UX
- >
- System Administration
- >
- Re: crontab behaviour
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
10-06-2009 06:51 PM
10-06-2009 06:51 PM
Re: crontab behaviour
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-06-2009 06:59 PM
10-06-2009 06:59 PM
Re: crontab behaviour
Did you do as Hasan suggested, use "crontab -e" and make a minor change?
I suppose this would only matter if you ever had your crontab entry executing for every day.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-06-2009 09:13 PM
10-06-2009 09:13 PM
Re: crontab behaviour
I would suggest that you verify your cronlog to determine the first time the job was executed. Other jobs entries that might be running before and that might have been accidentally been modified.
In the meanwhile you may wish to remove this entry or comment it as:
#0 18 * * 6 sh
hope this helps!
kind regards
yogeeraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-07-2009 01:53 AM
10-07-2009 01:53 AM
Re: crontab behaviour
I did two things yesterday.
1. Typed the same entry again and commented old one, suspecting any blank or spl char issue
2. Restarted cron daemon as it seemed user had done some changes few days ago.
Yesterday it didnt run, as required. Still monitoring it for few days.
Thank you all for you suggestions..
I would update after observing it more...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-07-2009 02:11 AM
10-07-2009 02:11 AM
Re: crontab behaviour
The "crontab -e" uses the editor defined in the EDITOR environment variable, or vi if nothing is defined. After the crontab file has been edited, the "crontab" command signals the cron daemon to make it re-read the crontab file. If someone edits the /var/spool/cron/crontabs/
MK
- « Previous
-
- 1
- 2
- Next »
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP