08-06-2010
crontab question
I have a user (xxx) who is allowed to run cron jobs when a job is
launched from cron is the .profile sourced in? I am not sure it is so I setup a cron job as this user to do the following:
35 15 * * 0-5 su - xxx -c "ksh ls -lt /tmp" > /tmp.out
and I am seeing the following error (see below). Does anybody know how to fix this?
3004-501 Cannot su to "xxx" : Authentication is denied.
[compat]: 3004-300 You entered an invalid login name or password.
Thanks in advance to all who answer this post.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Why does this cron entry do nothing? It works interactively.
58 23 * * * mydate=`date '+%Y%m%d'`;mv /opt/home/user/file /opt/home/user/file_$mydate (5 Replies)
Discussion started by: steelrose
5 Replies
2. Solaris
HI all,
I would want to schedule a job to run every 2 weeks. In the mean time, i'm only able to schedule on every week. Is it possible to schedule 2 weeks on crontab?
Thank you. (3 Replies)
Discussion started by: *Jess*
3 Replies
3. UNIX for Dummies Questions & Answers
I set up a job to run a script in a certain directory to remove certain files. The script seems to run as my logs indicate but nothing happens. If I run the script manually then it removes the correct files. I'm now wondering if crontab doesnt have access to remove files from the directory I'm... (9 Replies)
Discussion started by: NycUnxer
9 Replies
4. AIX
My question is how to specify the one-time execution of a shell script in crontab?
For example: If I wanted to schedule shell "Test.sh" for one-time execution on December 13 at 8:00AM would it be as follows?
00 08 13 12 6 /usr/datatools/dtbackups/Test.sh > /usr/u/sybase_12.5/logs/Test.log &... (3 Replies)
Discussion started by: Alan.AIX
3 Replies
5. UNIX for Dummies Questions & Answers
Hello guys,
I have a server with Red Hat Enterprise Linux AS release 4 (Nahant Update 5), there i have a lot of users, im the root. I need to lock the use of crontab to the users, i mean, i dont want to give to the users the option to creat any crontab line, how can i do that?
I tried to... (4 Replies)
Discussion started by: lestat_ecuador
4 Replies
6. HP-UX
Please cna you tell me if the following command entered in error would affect the crontab file
crontab -e | more
Thanks :) (12 Replies)
Discussion started by: blondie2407
12 Replies
7. Solaris
I want to run a script on (say) the 4th friday every month. But if I include this line in the crontab :
45 9 22-28 * 5 echo '4th Friday'|mailx -s "Fri week 4" mike
it sends me mail if the date is 22-28, OR the day is friday. So I get mail every day for a week , and also every friday.
I... (2 Replies)
Discussion started by: mikejordan
2 Replies
8. UNIX for Dummies Questions & Answers
Hey out there
This is all I have in my crontab file. I know the crontab works because it was already out there and working. I simply replaced the existing with my line of code below to see if it worked. I uploaded 6 month old pdf files in this directory, stopped/started all the scripts that... (3 Replies)
Discussion started by: vsekvsek
3 Replies
9. Shell Programming and Scripting
I need to run an script every 10th and 25th day in every month at 11pm.
the script name is /home/ss/automated.sh
I tried to execute the script every day and everytime with the below syntax. its not executing it from crontab.
* * * * * /home/ss/automated.sh
Any idea why it not... (6 Replies)
Discussion started by: ramkumar15
6 Replies
10. Shell Programming and Scripting
Hello,
I have scheduled the execution of a file (delete_oldv02) every hour with crontab and it works perfectly. See below the instruction written.
0 */1 * * * /home/delete_oldv02 >>/home/delete_oldv02.log
My first question is if I can add one more line to crontab.
I also would like to... (5 Replies)
Discussion started by: dcaccount
5 Replies
LEARN ABOUT OSF1
queuedefs
queuedefs(4) Kernel Interfaces Manual queuedefs(4)
NAME
queuedefs - Queue description file for at, batch, and cron commands
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron or specifies other characteristics for cron. Each noncom-
ment line in this file describes either one queue or a cron characteristic. Each uncommented line should be in one of the following for-
mats.
q.[njobj][nicen][nwaitw] max_jobs=mjobs log=lcode
The fields in these lines are as follows: The name of the queue. Defined queues are as follows: The default queue for jobs started by at
The default queue for jobs started by batch The default queue for jobs run from a crontab file
Queues d to z are also available for local use. The maximum number of jobs that can be run simultaneously in the queue; if more
than njob jobs are ready to run, only the first njob jobs will be run. The others will be initiated as currently running jobs ter-
minate. The nice(1) value to give to all jobs in the queue that are not run with a user ID of superuser. The number of seconds to
wait before rescheduling a job that was deferred because more than njob jobs were running in that queue, or because the system-wide
limit of jobs executing (max_jobs) has been reached. The maximum number of active jobs from all queues that may run at any one
time. The default is 25 jobs. Logging level of messages sent to a log file. The default is 4. Defined levels are as follows:
level-code level
0 None
1 Low
2 Medium
3 High
4 Full
Lines beginning with # are comments, and are ignored.
EXAMPLES
The following file specifies that the b queue, for batch jobs, can have up to 50 jobs running simultaneously; that those jobs will be run
with a nice value of 20. If a job cannot be run because too many other jobs are running, cron will wait 60 seconds before trying again to
run it. All other queues can have up to 100 jobs running simultaneously; they will be run with a nice value of 2. If a job cannot be run
because too many other jobs are running cron will wait 60 seconds before trying again to run it. b.50j20n60w
The following file specifies that a total of 25 active jobs will be allowed by cron over all the queues at any one time, and cron will log
all messages to the log file. The last two lines are comments that are ignored. max_jobs=25 log=4 # This is a comment # And so is this
FILES
Main cron directory The default location for the queue description file.
RELATED INFORMATION
Commands: at(1), cron(8), crontab(1), nice(1)
delim off
queuedefs(4)