- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - HP-UX
- >
- System Administration
- >
- crontab behaviour
-
-
Categories
- Topics
- Hybrid IT with Cloud
- Mobile & IoT
- IT for Data & Analytics
- Transformation
- Strategy and Technology
- Products
- Cloud
- Integrated Systems
- Networking
- Servers and Operating Systems
- Services
- Storage
- Company
- Events
- Partner Solutions and Certifications
- Welcome
- Welcome
- Announcements
- Tips and Tricks
- Feedback
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- Converged Data Center Infrastructure
- Digital Transformation
- Grounded in the Cloud
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- Networking
- OEM Solutions
- Servers: The Right Compute
- Telecom IQ
- Transforming IT
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Categories
-
Forums
-
Blogs
-
InformationEnglish
crontab behaviour
- 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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-06-2009 02:29 AM
10-06-2009 02:29 AM
crontab behaviour
crontab behaviour
cron with entry:
0 18 * * 6 sh
is being executed daily...what could be the reason please
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-06-2009 02:58 AM
10-06-2009 02:58 AM
Re: crontab behaviour
Re: crontab behaviour
try stop and start cron deamon.
Hasan
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-06-2009 03:00 AM
10-06-2009 03:00 AM
Re: crontab behaviour
Re: crontab behaviour
>>what could be the reason
You are wrong your cron entry will not run daily as per your entry it will run
0 min 18 hr. but every 6 day of week.
In crontab file there are five fields
field allowed values
----- --------------
minute 0-59
hour 0-23
day of month 1-31
month 1-12 (or names, see below)
day of week 0-7 (0 or 7 is Sun, or use names)
For more information see the below link
http://unixhelp.ed.ac.uk/CGI/man-cgi?crontab+5
Suraj
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-06-2009 03:13 AM
10-06-2009 03:13 AM
Re: crontab behaviour
Re: crontab behaviour
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-06-2009 06:23 AM
10-06-2009 06:23 AM
Re: crontab behaviour
Re: crontab behaviour
I assume you have something other than just "sh" as the command?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-06-2009 07:10 AM
10-06-2009 07:10 AM
Re: crontab behaviour
Re: crontab behaviour
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-06-2009 07:19 AM
10-06-2009 07:19 AM
Re: crontab behaviour
Re: crontab behaviour
Pete
Pete
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-06-2009 07:26 AM
10-06-2009 07:26 AM
Re: crontab behaviour
Re: crontab behaviour
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-06-2009 07:39 AM
10-06-2009 07:39 AM
Re: crontab behaviour
Re: crontab behaviour
Where did you get this? Did you type "crontab -l"?
Run crontab -l and check if there is another cron entry for the same "sh" script.
Check what the sh script does when it runs. It could be scheduling itself to run again in 24 hours.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
10-06-2009 07:40 AM
10-06-2009 07:40 AM
Re: crontab behaviour
Re: crontab behaviour
- Mark as New
- Bookmark
- Subscribe
- 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
Re: crontab behaviour
- Mark as New
- Bookmark
- Subscribe
- 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
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
- 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
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
- 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
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
- 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
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
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2018 Hewlett Packard Enterprise Development LP