11-19-2007
Quote:
Originally Posted by
moe2266
I already have that but it doesn't work.
that's what i have:
0 22 1-7 * 6
And I already mentioned that this is discussed in the FAQ.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I can see where the nohup command can come in very handy. My question is, do you have to do something like this (nohup) in order to run certain cron jobs? On the windows side, I have a couple of scripts that basically run continuously, so all I have to do is ctrl-alt-del to lock my workstation,... (2 Replies)
Discussion started by: wmosley2
2 Replies
2. Shell Programming and Scripting
A co-worker is having trouble w/ a job scheduled from cron and I got involved. Unfortunately I couldn't seem to find the answer and need some help. First off, I'm pretty sure he's using redhat linux. Anyway, I want to schedule a cronjob to run a java class. Let's say that, logged in as root, I... (3 Replies)
Discussion started by: doublek321
3 Replies
3. Shell Programming and Scripting
I'm new to cron, What does this syntax mean?
0 5 * * 1-5 /u08/0ra33/run_arch.sh
thanks (2 Replies)
Discussion started by: ted
2 Replies
4. AIX
Could someone please tell me how I might specify in cron that I want a job to run only on the "last saturday" of the month?
Thanks. (2 Replies)
Discussion started by: DenD
2 Replies
5. UNIX for Dummies Questions & Answers
I have a script which goes out and installs a package on a box remotely and im trying to get it to add a cron job too..but im having a few problems, whilst it does add the entry it wont run unless I connect to the machine , crontab -e, then :wq. This re-reads the configuration file and it will now... (1 Reply)
Discussion started by: hcclnoodles
1 Replies
6. Solaris
I have a script that needs to install a script the runs just before cron starts. Currently (for 9 and older), it simply finds the name of the cron script in /etc/rc?.d, decrements the number and creates a link.
For example, if cron starts with /etc/rc2.d/S75cron, the install script extracts the... (3 Replies)
Discussion started by: BOFH
3 Replies
7. Shell Programming and Scripting
Folks;
I have this script in SUN which if i run it using command line, it works fine, but when i run it using cron, it work but it misses one thing. here's the details
#!/bin/bash
cd /opt/new_script
for i in ./report*Groups.sh; do $i $1; done
This script above when runs through cron, it... (4 Replies)
Discussion started by: moe2266
4 Replies
8. Linux
with the cron format
* * * * *
| | | | | |
| | | | |
| | | | +---- Day of the Week (range: 1-7, 1 standing for Monday)
| | | +------ Month of the Year (range: 1-12)
| | +-------- Day of the Month (range: 1-31)
| +---------- Hour (range: 0-23)
+------------ Minute ... (1 Reply)
Discussion started by: buyog
1 Replies
9. Shell Programming and Scripting
Hi,
We have developed the script which will send an (html)attachment in through mail. The stand alone script is working fine ,but when we schedule it cron the "nail" command is not working that is we are not receving any mail.
Following is the command which we used to send the mail. :confused:... (4 Replies)
Discussion started by: Amey Joshi
4 Replies
10. UNIX for Dummies Questions & Answers
Hi,
I have a cron job that I want to run twice a week, on Tues/Thurs, and I want it to run three times - specifically at 10pm, 11:10pm, and 12:20am respectively.
I "think" the way to do this is to run the following:
00,10,20 22,23,00 * * 2,4 MYCOMMAND
Just wanted to verify this... (4 Replies)
Discussion started by: xdawg
4 Replies
AT(1) General Commands Manual AT(1)
NAME
at - execute commands at a later time
SYNOPSIS
at [ -c ] [ -s ] [ -m ] time [ day ] [ file ]
DESCRIPTION
At spools away a copy of the named file to be used as input to sh(1) or csh(1). If the -c flag (for (csh(1))) or the -s flag (for (sh(1)))
is specified, then that shell will be used to execute the job; if no shell is specified, the current environment shell is used. If no file
name is specified, at prompts for commands from standard input until a ^D is typed.
If the -m flag is specified, mail will be sent to the user after the job has been run. If errors occur during execution of the job, then a
copy of the error diagnostics will be sent to the user. If no errors occur, then a short message is sent informing the user that no errors
occurred.
The format of the spool file is as follows: A four line header that includes the owner of the job, the name of the job, the shell used to
run the job, and whether mail will be set after the job is executed. The header is followed by a cd command to the current directory and a
umask command to set the modes on any files created by the job. Then at copies all relevant environment variables to the spool file. When
the script is run, it uses the user and group ID of the creator of the spool file.
The time is 1 to 4 digits, with an optional following `A', `P', `N' or `M' for AM, PM, noon or midnight. One and two digit numbers are
taken to be hours, three and four digits to be hours and minutes. If no letters follow the digits, a 24 hour clock time is understood.
The optional day is either (1) a month name followed by a day number, or (2) a day of the week; if the word `week' follows, invocation is
moved seven days further off. Names of months and days may be recognizably truncated. Examples of legitimate commands are
at 8am jan 24
at -c -m 1530 fr week
at -s -m 1200n week
At programs are executed by periodic execution of the command /usr/libexec/atrun from cron(8). The granularity of at depends upon the how
often atrun is executed.
Error output is lost unless redirected or the -m flag is requested, in which case a copy of the errors is sent to the user via mail(1).
FILES
/usr/spool/at spooling area
/usr/spool/at/yy.ddd.hhhh.* job file
/usr/spool/at/past directory where jobs are executed from
/usr/spool/at/lasttimedone last time atrun was run
/usr/libexec/atrun executor (run by cron(8))
SEE ALSO
atq(1), atrm(1), calendar(1), sleep(1), cron(8)
DIAGNOSTICS
Complains about various syntax errors and times out of range.
BUGS
Due to the granularity of the execution of /usr/libexec/atrun, there may be bugs in scheduling things almost exactly 24 hours into the
future.
If the system crashes, mail is not sent to the user informing them that the job was not completed.
Sometimes old spool files are not removed from the directory /usr/spool/at/past. This is usually due to a system crash, and requires that
they be removed by hand.
4th Berkeley Distribution October 21, 1996 AT(1)