06-25-2007
Hi
Tip I can give you is from SunSolaris, I allways create crontab file and edit it with vi and then activate it.
crontab -l > root.crontab
vi root.crontab
(Do your changes)
crontab -r
crontab root.crontab
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello All,
I did very stupid mistake and lost all my crontab enteries on root prompt.
Please help me to solve this issue.
i did entry on root prompt like this.
crontab /home/back.cron
and enters
but when i enter crontab -l so its only showing 1 entry defined in back.cron
and all... (2 Replies)
Discussion started by: wakhan
2 Replies
2. AIX
Good morning everybody. I have just receiedv a complaint from our DBA saying that if he create a scripts to run some Oracle performance scripts using crontab and the scheduling part is ok but the job is failed when I checked on /var/adm/cron/log.
I have tried his scripts using Oracle id directly... (4 Replies)
Discussion started by: kwliew999
4 Replies
3. Solaris
So I'm having a problem with crontab -e. It seems like it should work. And it seems like I should know the answer to this question.
$ su -
# echo $SHELL
/bin/sh
# crontab -e
372
Any thoughts? (2 Replies)
Discussion started by: adelsin
2 Replies
4. UNIX for Dummies Questions & Answers
Hi All,
Ref: "build crontab from a text file" in same forum. (I am not allowed to post URL's in the first post)
We are reorganizing our UNIX Crontab file by first making changes in a word pad text file. The intent is to then copy it back to Crontab. Will this work? Copy and Paste does not... (6 Replies)
Discussion started by: nivedhitha
6 Replies
5. Solaris
Hi everyone,
I got error which is "!bad user (root)" in crontab...
I tried changing password,
I checked etc/cron/cron.allow and cron.deny,
And also I checked the permissions of my files,
its(my crontab script) still not working....
Please help... (12 Replies)
Discussion started by: ijustneeda
12 Replies
6. Red Hat
Greetings/
I have a script listed in my roots crontab
07 9 * * * /opt/HLRSDATA_2010_OCT/HLRS_Scheduler_sp.sh > /opt/HLRSDATA_2010_OCT/logs/HLRTKJob.log
This script contains the following
#!/bin/bash
echo HLRSData Scheduler
cd /opt/HLRSDATA_2010_OCT
/usr/bin/java -Xms32m -Xmx1024m -cp... (6 Replies)
Discussion started by: RedSpyder
6 Replies
7. BSD
Someone can told me where from get the default crontab settings of root for NetBSD 6.0 please :)
### SOLVED ###
The default crontab rules are in etc.tgz /var/cron/tabs/root
# $NetBSD: crontab,v 1.15 2002/11/27 15:09:17 perry Exp $
#
# /var/cron/tabs/root - root's crontab for NetBSD
#... (0 Replies)
Discussion started by: batence
0 Replies
8. Linux
I have a customer who is trying to have files saved as owner root in an application home directory. I've tried setting the sticky bit and but am not having luck. They do not have full root or sudo access.
User = user123
Group = group123
Files are being saved as user123:group123 but they... (2 Replies)
Discussion started by: rkruck
2 Replies
9. UNIX for Beginners Questions & Answers
Hi,
Is there any safe method to provide read access to root's crontab to another user? Just read no other permissions. (1 Reply)
Discussion started by: ctrld
1 Replies
10. Shell Programming and Scripting
Hi,
i have two servers say server A and server B. i have a sudo user say user1 with full privilges on server A and B. i am trying to append the crontab entry of root from server A of server B with the following command. But its appending on A. i need to append it on server B.
please find the... (4 Replies)
Discussion started by: venkitesh
4 Replies
CRONTAB(1) General Commands Manual CRONTAB(1)
NAME
crontab - maintain crontab files for individual users (ISC Cron V4.1)
SYNOPSIS
crontab [-u user] file
crontab [-u user] [-l | -r | -e]
DESCRIPTION
Crontab is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in ISC Cron. Each user can have
their own crontab, and though these are files in /var, they are not intended to be edited directly.
If the cron.allow file exists, then you must be listed therein in order to be allowed to use this command. If the cron.allow file does not
exist but the cron.deny file does exist, then you must not be listed in the cron.deny file in order to use this command. If neither of
these files exists, only the super user will be allowed to use this command.
If the -u option is given, it specifies 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(8) can confuse crontab and that if you are running
inside of su(8) you should always use the -u option for safety's sake.
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 -l option causes the current crontab to be displayed on standard output.
The -r option causes the current crontab to be removed.
The -e option is used to edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit
from the editor, the modified crontab will be installed automatically.
SEE ALSO
crontab(5), cron(8)
FILES
/etc/cron.allow
/etc/cron.deny
STANDARDS
The crontab command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax differs from previous versions of Vixie Cron, as
well as from the classic SVR3 syntax.
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
AUTHOR
Paul Vixie <vixie@isc.org>
4th Berkeley Distribution 29 December 1993 CRONTAB(1)