|
|
|
|||||||
| Home | Forums | Register | Rules & FAQ | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| HP-UX HP-UX (Hewlett Packard UniX) is Hewlett-Packard's proprietary implementation of the Unix operating system, based on System V. |
Other UNIX.COM Threads You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Weird Awk issue | Khoomfire | UNIX for Advanced & Expert Users | 17 | 04-14-2008 04:13 AM |
| Weird crontab problem | RobSand | SUN Solaris | 8 | 10-09-2007 02:12 PM |
| weird domain issue. | thirddegreekris | UNIX for Advanced & Expert Users | 2 | 05-03-2007 09:42 PM |
| Crontab Issue | rickyt00 | UNIX for Dummies Questions & Answers | 2 | 08-06-2005 06:31 AM |
| Weird SSH issue | AKM | UNIX for Advanced & Expert Users | 6 | 11-08-2004 10:13 AM |
 |
|
|
Submit Tools | LinkBack | Thread Tools | Search this Thread | Display Modes |
04-07-2008
|
||||
|
||||
Weird Issue with crontab.
Hello all,
Normally I'm pretty comfortable with crontab, changing and updating (done it many-a-time). But in the last two days I've been pulling my hair out over the following... Details of OS: HP-UX mdirect B.11.23 U ia64 2587410573 unlimited-user license Issue: Execute a script (very similar to two pre-existing scripts - which are working) from root's crontab ... 05 16 * * * * nice ksh -c /usr/local/bin/space_chk_3 >> /usr1/log/root/cronlog/space_chk_3.log 2>&1 However it is returning the following... "sh: KEY.txt: Execute permission denied." to the cronlog file output. KEY.txt happens to be the first normal file in the root (/) directory. In the /var/adm/cron/log file I see the following with previous run attempts I did earlier today ... < root 27991 c Tue Apr 8 12:05:00 EST 2008 rc=126 < root 28748 c Tue Apr 8 12:10:00 EST 2008 rc=126 < root 29501 c Tue Apr 8 12:18:00 EST 2008 rc=126 I'm nuttered to understand why crontab for the root user is doing this. Any suggestions/assistance apreciated. I'm a little concerned that the answer is sitting right in front of me and I'm at present too blind to see the cause. Last edited by Cameron : 04-21-2008 at 08:35 PM. Reason: Removal of script - not required or part of the solution. 
|
| Forum Sponsor | ||
|
|
|
04-21-2008
|
||||
|
||||
|
I use this header at the top of the crontab file to help avoid such errors and make it easier to read
Code:
#Minute (0-59), #| Hour (0-23), #| | Day of the month (1-31), #| | | Month of the year (1-12), #| | | | Day of the week (0-6 with 0=Sunday). #| | | | | Commands #| | | | | | #------------------------------------------------------------------------------------------------------- Code:
# sudo crontab -l #ident "@(#)root 1.21 04/03/23 SMI" # # The root crontab should be used to perform accounting data collection. # # #Minute (0-59), #| Hour (0-23), #| | Day of the month (1-31), #| | | Month of the year (1-12), #| | | | Day of the week (0-6 with 0=Sunday). #| | | | | Commands #| | | | | | #------------------------------------------------------------------------------------------------------- 10 3 * * * /usr/sbin/logadm 15 3 * * 0 /usr/lib/fs/nfs/nfsfind 30 3 * * * [ -x /usr/lib/gss/gsscred_clean ] && /usr/lib/gss/gsscred_clean
|
Linear Mode
