Maybe the server was down when the cron job was supposed to run?
I would just say > /dev/null but it doesn't matter.
/var/log/syslog or similar logfile maybe with different name on different system should record what happens every time a cron job runs. Browse or grep that file.
You can crontab -e to make the job run sometime when you are around and you can monitor what happens.
You might as well direct the output to some log files so you'll never be in the dark:
I'm trying to locate all files that do not contain the string /usr but do contain the string csh within the file called /etc/passwd. Then I would like to direct this output to a file called pout.
Does anyone one have suggestions on this one?
Thanks (2 Replies)
How do I direct the output of an at command
at now < backupprogram
so that I see something happening. It says the job has been executed but I am not getting the tar file that my backup program on the computer anywhere at all
Please help me - I really am a struggling begginer. (1 Reply)
Hi,
I'm running a program by executing the following command...
convert NA 2> compiler.err
Here is the command for debugging this process in IBM debugger...
idebug convert NA 2> compiler.err
On executing the above command the error output from idebug process is
redirected to compiler.err,... (3 Replies)
Hi,
I just wrote a program in C to split a comma seperated string in to group of strings using strtok() function. The code is:
int main()
{
char *temp;//not used here but basically we extract one string after another using strtok() and assign to a string pointer defined like this.
... (3 Replies)
When I do
time tar cvf /dev/st0 /mnt/junk >> /root/benchlog, I want it to put the output of the time command into the benchlog file, but it put /mnt/junk. How do I get it to put the output of the tar command? (1 Reply)
I have a script in which some outputs are directed to one file
echo "Load Started" >>${LOGFILE1}
If I have another file LOGFILE2 and i want to redirect the output of the above echo command to LOGFILE2 as well with the same command line... how can i do that?
Thanks (2 Replies)
Dear All
I have a simple bash script that creates a folder ( I called it TEMP) in the current directory.
The question is: how do I direct the output of my awk script into folder TEMP?
Below is my attempt:
#!/bin/bash
mkdir TEMP
echo Enter input file:
read infile
awk... (4 Replies)
Is there a way to keep the output of a script displayed on the terminal when it's run by itself, but suspend part of that output and only have a specific part delivered when it's piped to another script or program? I'm thinking something like the following pseudocode:
#!/bin/bash
... (1 Reply)
Hi,
I still have the problem with directing information from cat or grep to a variable.
For instance:
XMSG "$(date +%Y_%m_%d)_error_report.txt" "$(cat "$(date +%Y_%m_%d)_error_report.txt")" &Works! The text received by cat is directed to my function.
If it is written like this, my... (2 Replies)
Discussion started by: haukee
2 Replies
LEARN ABOUT OPENDARWIN
cron
cron(1M) System Administration Commands cron(1M)NAME
cron - clock daemon
SYNOPSIS
/usr/sbin/cron
DESCRIPTION
cron starts a process that executes commands at specified dates and times.
You can specify regularly scheduled commands to cron according to instructions found in crontab files in the directory
/var/spool/cron/crontabs. Users can submit their own crontab file using the crontab(1) command. Commands which are to be executed only once
can be submitted using the at(1) command.
cron only examines crontab or at command files during its own process initialization phase and when the crontab or at command is run. This
reduces the overhead of checking for new or changed files at regularly scheduled intervals.
As cron never exits, it should be executed only once. This is done routinely by way of the svc:/system/cron:default service. The file
/etc/cron.d/FIFO file is used as a lock file to prevent the execution of more than one instance of cron.
cron captures the output of the job's stdout and stderr streams, and, if it is not empty, mails the output to the user. If the job does not
produce output, no mail is sent to the user. An exception is if the job is an at(1) job and the -m option was specified when the job was
submitted.
cron and at jobs are not executed if your account is locked. Jobs and processses execute. The shadow(4) file defines which accounts are not
locked and will have their jobs and processes executed.
Setting cron Jobs Across Timezones
The timezone of the cron daemon sets the system-wide timezone for cron entries. This, in turn, is by set by default system-wide using
/etc/default/init.
If some form of daylight savings or summer/winter time is in effect, then jobs scheduled during the switchover period could be executed
once, twice, or not at all.
Setting cron Defaults
To keep a log of all actions taken by cron, you must specify CRONLOG=YES in the /etc/default/cron file. If you specify CRONLOG=NO, no log-
ging is done. Keeping the log is a user configurable option since cron usually creates huge log files.
You can specify the PATH for user cron jobs by using PATH= in /etc/default/cron. You can set the PATH for root cron jobs using SUPATH= in
/etc/default/cron. Carefully consider the security implications of setting PATH and SUPATH.
Example /etc/default/cron file:
CRONLOG=YES
PATH=/usr/bin:/usr/ucb:
This example enables logging and sets the default PATH used by non-root jobs to /usr/bin:/usr/ucb:. Root jobs continue to use
/usr/sbin:/usr/bin.
The cron log file is periodically rotated by logadm(1M).
FILES
/etc/cron.d Main cron directory
/etc/cron.d/FIFO Lock file
/etc/default/cron cron default settings file
/var/cron/log cron history information
/var/spool/cron Spool area
/etc/cron.d/queuedefs Queue description file for at, batch, and cron
/etc/logadm.conf Configuration file for logadm
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO svcs(1), at(1), crontab(1), sh(1), logadm(1M), svcadm(1M), queuedefs(4), shadow(4), attributes(5), smf(5)NOTES
The cron service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/cron:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
DIAGNOSTICS
A history of all actions taken by cron is stored in /var/cron/log and possibly in /var/cron/olog.
SunOS 5.10 5 Aug 2004 cron(1M)