07-22-2006
Well....
if that is the case then you can look into the directory --
/var/log and you will find files by the name cron, cron.1, cron.2.....etc.
There's a size specified for the file and if it grows larger than the specified file size, then it is named as cron.<a no.> and a new file for new logs is created by the name "cron ".
Although if you want to specify a different location for the cron log files, then edit the file /etc/syslog.conf and look for the entry given for cron and edit it and specify the new location.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all, my problen is I designed a crontab with specific parameters & was running till yesterday.
Suddenly it stoped working, I have a confusion that what should be the crontab file location in our file directory...or it doesn't matter that where ever this file is stored.
What should I do now?
... (3 Replies)
Discussion started by: Vips
3 Replies
2. Shell Programming and Scripting
Hi,
I scheduled one script through crontab command and seems like it is hanging. I come to know this through the command 'ps -ef' whcih is showing me the program running, but no chances of it to take more than 2hrs to comlpete.
I want to kill that process. I tried to kill it using the... (6 Replies)
Discussion started by: DILEEP410
6 Replies
3. UNIX for Dummies Questions & Answers
I am looking for a way to kill 2 processes from a user through some kind of script.
Using an oracle script, I get two process ids that need to be killed.
SQL> select ssn.process as client_process_id, pcs.spid as oracle_process_id, ssn.sid, ssn.serial#
2 from v$session ssn inner join... (5 Replies)
Discussion started by: Meert
5 Replies
4. UNIX for Advanced & Expert Users
This below one find the table name in the log.I want location of log file.Please any help
> find / -type f -name "*.log" -exec grep -i 'sct' {} 2>/dev/null \;
. . importing table "sct"
. . exporting table sct
. . importing table "sct"
. . exporting table sct
... (1 Reply)
Discussion started by: mohan705
1 Replies
5. AIX
What is the location of smit.log (3 Replies)
Discussion started by: AIXlearner
3 Replies
6. Shell Programming and Scripting
Hello,
I have a process a.out that runs from /a and /b
How can I get the pid of the one running from /a
ps -C /a/a.out
does not work
Thanks! (4 Replies)
Discussion started by: JCR
4 Replies
7. AIX
Hi,
I would like to find out where the system will display the server was shutdown due to power fluctuation.
I have check the command errpt and alog -o -t boot |more but not getting the requred information.
alog -o -t boot command is not showing the time
Time: 9 LEDS: 0x538
invoking... (4 Replies)
Discussion started by: manoj.solaris
4 Replies
8. Shell Programming and Scripting
Hi,
I am logging to a linux server through a user "user1" in /home directory.
There is a script in a directory in 'root' for which all permissions are available including the directory. This script when executed creates a file in the directory.
When the script is added to crontab, on... (1 Reply)
Discussion started by: archana.n
1 Replies
9. UNIX for Dummies Questions & Answers
Hi!
I need your help, please.
I'm in AIX node and sometimes listener process from an oracle instance gets duplicated, i mean that it get spawned a second listener process. As we can't apply changes to the databases on this months, i want to build a shell that can identify the second... (6 Replies)
Discussion started by: Pactows
6 Replies
10. Solaris
Hi
I've found this crontab entry to run sa1 on sunOs box but I don't know where the result of this command is being stored. Is there a standard location for this? I assume the command is supposed to be storing the details somewhere..
Thanks (2 Replies)
Discussion started by: Grueben
2 Replies
CRON(8) BSD System Manager's Manual CRON(8)
NAME
cron -- daemon to execute scheduled commands (ISC Cron V4.1)
SYNOPSIS
cron [-n] [-x debugflags]
DESCRIPTION
cron is normally started during system boot by rc.d(8) framework, if cron is switched on in rc.conf(5).
It will return immediately so you don't have to start it with '&'.
cron searches /var/cron/tabs for crontab files which are named after accounts in /etc/passwd. Crontabs found are loaded into memory. cron
also searches for /etc/crontab which is in a different format (see crontab(5)). Finally cron looks for crontabs in /etc/cron.d if it exists,
and executes each file as a crontab.
When cron looks in a directory for crontabs (either in /var/cron/tabs or /etc/cron.d) it will not process files that:
- Start with a '.' or a '#'.
- End with a '~' or with ``.rpmsave'', ``.rpmorig'', or ``.rpmnew''.
- Are of zero length.
- Their length is greater than MAXNAMLEN.
cron then wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute. When
executing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab,
if such exists).
Events such as START and FINISH are recorded in the /var/log/cron log file with date and time details. This information is useful for a num-
ber of reasons, such as determining the amount of time required to run a particular job. By default, root has an hourly job that rotates
these log files with compression to preserve disk space.
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab or /etc/cron.d) has changed,
and if it has, cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted when-
ever a crontab file is modified. Note that the crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
The following options are available:
-x This flag turns on some debugging flags. debugflags is comma-separated list of debugging flags to turn on. If a flag is turned on,
cron writes some additional debugging information to system log during its work. Available debugging flags are:
sch scheduling
proc process control
pars parsing
load database loading
misc miscellaneous
test test mode - do not actually execute any commands
bit show how various bits are set (long)
ext print extended debugging information
-n Stay in the foreground and don't daemonize cron.
Daylight Saving Time and other time changes
Local time changes of less than three hours, such as those caused by the start or end of Daylight Saving Time, are handled specially. This
only applies to jobs that run at a specific time and jobs that are run with a granularity greater than one hour. Jobs that run more fre-
quently are scheduled normally.
If time has moved forward, those jobs that would have run in the interval that has been skipped will be run immediately. Conversely, if time
has moved backward, care is taken to avoid running jobs twice.
Time changes of more than 3 hours are considered to be corrections to the clock or timezone, and the new time is used immediately.
SIGNALS
On receipt of a SIGHUP, the cron daemon will close and reopen its log file. This is useful in scripts which rotate and age log files. Natu-
rally this is not relevant if cron was built to use syslog(3).
FILES
/var/cron/tabs cron spool directory
/etc/crontab system crontab file
/etc/cron.d/ system crontab directory
/var/log/cron log file for cron events
SEE ALSO
crontab(1), crontab(5)
AUTHORS
Paul Vixie <vixie@isc.org>
BSD
October 12, 2011 BSD