05-14-2012
Quote:
Originally Posted by
methyl
First cron: Hourly except at 20:00 . What did you intend? I'm assuming that this certain editions of Linux because the syntax is invalid in unix.
Second cron: every 20 mins (On the hour; twenty minutes past the hour; and forty minutes past the hour).
Third cron: At 20 minutes past every hour.
I'm just learning syntax differences. Thank you for your reply I appreciate it!
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
shouldn't they give the same output?
echo `echo \`date\``
is the same as the command date
echo `echo date`
prints the word date
thanks! (3 Replies)
Discussion started by: kfad
3 Replies
2. Solaris
Hi,
I would like to know what is the difference between executing the mount command in the following ways...
eg:
/usr/sbin/mount -F <something>
AND
mount -F <something>
I mean , just executing the mount command as opposed to specifying the path and then executing it?
... (3 Replies)
Discussion started by: wrapster
3 Replies
3. UNIX for Dummies Questions & Answers
Hello All, I have a question about the difference between two commands. I am using Korn and was told by the Unix admin that 'nohup <command> &'
equals 'nohup ./<command> &. That there is no difference betwewen the two. Is this true? Also, does the command './<command> &' provide a disconnect... (4 Replies)
Discussion started by: grin1dan
4 Replies
4. Shell Programming and Scripting
Hi,
I have to setup a process which will run every 30 minutes and perform a task. I have been looking into and considered to put a cron job in place which will automatically execute the process.
But lately I have found that Maestro job is also a process which will allow me to do the... (3 Replies)
Discussion started by: shanth_chandra
3 Replies
5. Shell Programming and Scripting
HI all,
Please clarify the difference between the following
pm2srv:/var/opt/temip/vf/scripts/saiki#awk '{RS = ":"} ; {print $0}' testf2
hey:wasup:howru:
Yes
I
am
fine
pm2srv:/var/opt/temip/vf/scripts/saiki#awk 'BEGIN { RS = ":" } ; { print $0 }' testf2
hey
wasup
howru
Yes
I... (0 Replies)
Discussion started by: saiki
0 Replies
6. UNIX for Dummies Questions & Answers
Hello! I'm just learning the shell, and I would really like to know how to do this:
Given these 2 commands:
ls -l
ls -le
How can I, with a one-liner, ask the shell to show me visually in the shell, what the difference is between the output of the two commands? They look the same to me... (6 Replies)
Discussion started by: turbofayce
6 Replies
7. Shell Programming and Scripting
Hi,
I need to know the difference between this commands:
grep * *search*
grep "*" *search*
As far as i know does the 2nd command search for files which have a name with *search* and greps then all which have chars from a-z in the file content.
But was does the first command??
Best... (1 Reply)
Discussion started by: xus
1 Replies
8. Solaris
Looking at the performance hit on my server, does it matter wich command I run?
client # rsh server tar –cf - . | tar –cv –f –
or
server # tar –cf – . | rsh client ‘cd target && tar –xv -f –‘
I think it doesn't really matter because both command strings involve a tar being run on... (4 Replies)
Discussion started by: petervg
4 Replies
9. AIX
Hi all,
I'm new in this forum.
I'm looking for the difference between the HACMP commands with the prefix "cl" and "cli".
The first type are under /usr/es/sbin/cluster/sbin directory and the second are under /usr/es/sbin/cluster/cspoc directory.
I know that the first are called HACMP for AIX... (0 Replies)
Discussion started by: peppix
0 Replies
10. Solaris
i need to know the difference between two commands
ps -ef|grep oracle
ps -ef|grep -v grep |grep oracle (1 Reply)
Discussion started by: smazshah
1 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)