Okay, you can do "logger -p debug7.crit test $RANDOM" and you will see a timestamp (probably on console, but also on every terminal) of what syslog thinks is the current time. You can then put in a cron job that runs every minute...
Then check the cron log to see the times output. If there's still a discrepancy, stop the cron daemon, stop the syslog server, then start syslog and then cron. Test again.
Hello,
I look at "man logger" I donot see "debug7.crit test $RANDOM" ? when I run this command I receive
Hi,
I trying to include a script in my crontab as user. I used "crontab -e" to include my script there but does not seem to work. If I understand correctly it is set to run at 11:20 every day, correct?
Can anybody identify any error?
<pre>
#Sun Microsystems Inc. SunOS 5.7 Generic... (19 Replies)
HI,
i am working on linux.
i have crontab problem
i wrote a small script and put it in a crontab .
but the script is not running..
i have given following way in crontab -e
02 06 * * * /bin/csh /home/vr_test.csh
but the above script is not running
please rectify my... (26 Replies)
I'm trying to get crontab to run a script, but to test crontab I tried out a very simple command: `echo bob`
here is my crontab file (I edited it by using `crontab -e`):
-----------------
#!/bin/sh
23 10 * * * echo bob
and at 10:23 every day I get a new message:
in /var/mail/a... (3 Replies)
i added to my crontab file:
* * * * * echo "hello"
it works, i receive a message into my /var/mail/username
and i receive: bob
in addition to a large text add-on
any help appreciated (1 Reply)
hi all
while using crontab -e im receiving
754 as output
im unable to add a entry in crontab
crontab -l is working fine
OS: sun5.8
can some one please assist me (4 Replies)
Dear All ,
I have .sh script wich has the following inside
getFileName=Listportfolio.txt.`date +'%Y%m%d`
ftp -n 172.10.10.1<<EOF
user xxx xxx
bin
cd /home/gbs/FTP_Script
get /home/gbs/FTP_Script/$getFileName
bye
EOF
EOF
when I run the... (3 Replies)
Hi All,
Am facing an issue while updating the crontab.Getting below error while updating the cron.
cron/tmp.XXXX5fXBR6: No space left on device
crontab: edits left in /tmp/crontab.XXXXEJX5gw
Is there any file where i need to alter using root user so that i can update the cron.
TIA... (9 Replies)
Hi to all.
Guys, i have a truble with oracle user crontab.
He work if i'm do
0-59 * * * * echo LOL> ~/test.txt
But not work if me set realy norm date
For example
14 17 28 12 * echo LOL> ~/test.txt
In 17:14 28 December .
In log file /var/adm/cron/log nothing....
Please... (3 Replies)
hi..
i have a program (tf.sh), and i want what it runs automatically with a "lapsus" of 2 hours. (1,3,5,7,9,11,13,15,17,19,21,23 hrs.)
i know what i have to do it using crontab, but i donīt know how to do it.
i have the next idea, but the problem is what it doesnīt run on my server... (11 Replies)
hi all
does any on has explanation for this result
bash-3.00$ crontab -e
"/var/tmp/Ex1kayUW" No space left on device
The crontab file was not changed.
bash-3.00$ (2 Replies)
Discussion started by: osmannix
2 Replies
LEARN ABOUT SUSE
cron
CRON(8) System Manager's Manual CRON(8)NAME
cron - daemon to execute scheduled commands (ISC Cron V4.1)
SYNOPSIS
cron [-l load_avg] [-n]
DESCRIPTION
Cron should be started from /etc/rc or /etc/rc.local. It will return immediately, so you don't need to start it with '&'. The -n option
changes this default behavior causing it to run in the foreground. This can be useful when starting it out of init.
Cron searches /var/spool/cron for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into memory. Cron
also searches for /etc/crontab and the files in the /etc/cron.d directory, which are in a different format (see crontab(5)). 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 execut-
ing 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).
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab) 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 whenever a crontab
file is modified. Note that the Crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
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.
PAM Access Control
On SUSE LINUX systems, crond now supports access control with PAM - see pam(8). A PAM configuration file for crond is installed in
/etc/pam.d/crond . crond loads the PAM environment from the pam_env module, but these can be overriden by settings in the crontab file.
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.
Naturally this is not relevant if cron was built to use syslog(3).
CAVEATS
In this version of cron, /etc/crontab must not be writable by any user other than root. No crontab files may be links, or linked to by any
other file. No crontab files may be executable, or be writable by any user other than their owner.
SEE ALSO crontab(1), crontab(5), pam(8)AUTHOR
Paul Vixie <vixie@isc.org>
4th Berkeley Distribution 10 January 1996" CRON(8)