11-29-2001
It probably should be
EDITOR=/usr/bin/vi
export EDITOR
I would stop and restart cron correctly. Sun's script will remove the fifo, a step which you omitted. I'm not sure how the fifo is used, but you could have left some garbage in the fifo which may have confused cron.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi there,
this time a have a other problem :)
i will start a script over the cron.
if i start the script manual (per command) it works without any problems, but over the cron it doesent work.
my cron looks like this:
26 15 * * * /path/scriptname.sh 2> /path/error.log
there is no... (3 Replies)
Discussion started by: scotty
3 Replies
2. Programming
how to store a date into file?
and how we can access date from the file?
---------- Post updated at 06:09 AM ---------- Previous update was at 06:08 AM ----------
how we can store date in file? (1 Reply)
Discussion started by: causalmodi777
1 Replies
3. UNIX and Linux Applications
Hi all!!
I have a nerve-wracking concept (probably for me!!) which is not understood. My crontab entry looks this way.
33 09 22 3 * /home/myexp.sh "Bgp4 ALL" >/dev/null 2>&1
But cron gets started occasionally. Sometimes it does. Sometimes it does not. And sometimes it hangs in the middle (I... (1 Reply)
Discussion started by: dhivyasuresh
1 Replies
4. Shell Programming and Scripting
Hi,
I have written a shell script to transfer files to a SFTP server passing the filername, source and dest directory as parameters and it runs well. :)
I want to schedule this script to run periodically using a cron job.
root@pingu # cat /etc/crontab
SHELL=/bin/bash... (1 Reply)
Discussion started by: chetancrsp18
1 Replies
5. UNIX for Dummies Questions & Answers
Hi friends,
today i created a cron job , registered the crontab file associated but dont know why the cron is not getting executed at the right time.??
content of Crontab file :
21 15 * * * /subrat/myt
i wanted to execute the script myt on 15:21 PM of everyday.
the script myt... (2 Replies)
Discussion started by: paras.oriental
2 Replies
6. Ubuntu
Hi guys. This is my first post so bear with me.
I'm trying to get cron to run a shell script in my home directory (/home/server) that checks the temperature of my HDD. The script works fine, however I can't run it in cron. I've checked the syslog and I have only seen two errors:
- Exited with... (11 Replies)
Discussion started by: Rautoner
11 Replies
7. UNIX for Dummies Questions & Answers
I am trying to setup a cron that runs a script to update my ip for my domain name every time I reboot and checks if my ip changes every 5 minutes and if it does then I update it. I am running Ubuntu server 12.04.
The file /etc/cron.d/ipupdate contains
#
#
# Run ipupdate
#
#
/5 * ... (3 Replies)
Discussion started by: Bros2
3 Replies
8. Shell Programming and Scripting
I am new to creating crontab file , i just wrote below
(40 19 * 3 * /root/maths/practisecron.sh), the script just prints "Hi".
When ever i save the above file i am getting this .
# crontab -e
crontab: installing new crontab
Can you please check where it went wrong.. (1 Reply)
Discussion started by: vkiyv05
1 Replies
9. UNIX for Dummies Questions & Answers
Good evening, ive got this cron to be run:
if i run this manually it doesnt work,it takes me to the prompt again
/export/app/CO/opge/scr/Informe_parametros_colombia.ksh >/dev/null 2>&1
here is the code fragment:
coopge@coopge: opge PRODUCCION>more... (1 Reply)
Discussion started by: alexcol
1 Replies
10. UNIX for Beginners Questions & Answers
Hi I want to set up a cron for every 15 minutes between some hours.
Can you tell whether the below command will work.
Getting confuse because my time goes from night to next day morning.
i want to setup 8 PM to next day 10 AM.
*/15 20-10 * * * sh abc.sh (1 Reply)
Discussion started by: raju2016
1 Replies
CRONTAB(1) BSD General Commands Manual CRONTAB(1)
NAME
crontab -- maintain crontab files for individual users (V3)
SYNOPSIS
crontab [-u user] file
crontab [-u user] { -l | -r | -e }
DESCRIPTION
The crontab utility is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user
can have their own crontab, and they are not intended to be edited directly.
(Darwin note: Although cron(8) and crontab(5) are officially supported under Darwin, their functionality has been absorbed into launchd(8),
which provides a more flexible way of automatically executing commands. See launchctl(1) for more information.)
If the /usr/lib/cron/cron.allow file exists, then you must be listed therein in order to be allowed to use this command. If the
/usr/lib/cron/cron.allow file does not exist but the /usr/lib/cron/cron.deny file does exist, then you must not be listed in the
/usr/lib/cron/cron.deny file in order to use this command. If neither of these files exists, then depending on site-dependent configuration
parameters, only the super user will be allowed to use this command, or all users will be able to use this command. The format of these
files is one username per line, with no leading or trailing whitespace. Lines of other formats will be ignored, and so can be used for com-
ments.
The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename '-' is given.
The following options are available:
-u Specify the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines ``your'' crontab, i.e.,
the crontab of the person executing the command. Note that su(1) can confuse crontab and that if you are running inside of su(1) you
should always use the -u option for safety's sake.
-l Display the current crontab on standard output.
-r Remove the current crontab.
-e Edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. The specified editor must edit
the file in place; any editor that unlinks the file and recreates it cannot be used. After you exit from the editor, the modified
crontab will be installed automatically.
FILES
/usr/lib/cron/cron.allow
/usr/lib/cron/cron.deny
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
SEE ALSO
crontab(5), compat(5), cron(8), launchctl(1)
STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2''). The new command syntax differs from previous versions of Vixie Cron, as well
as from the classic SVR3 syntax.
AUTHORS
Paul Vixie <paul@vix.com>
BSD
December 29, 1993 BSD