Sponsored Content
Full Discussion: Problem with crontab file
Top Forums UNIX for Dummies Questions & Answers Problem with crontab file Post 302546039 by bobble14988 on Wednesday 10th of August 2011 09:21:39 AM
Old 08-10-2011
Quote:
Originally Posted by jpradley
How did you change the file? If you edited it directly, that's incorrect. Try crontab -e.
I made crontab point to a different file. (Can't remember exactly how I did this but, by using crontab -l, I can see it worked).

Whenever I edit the crontab I do use crontab -e however.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

crontab problem

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)
Discussion started by: guest100
19 Replies

2. UNIX for Dummies Questions & Answers

Problem with crontab

I am trying to schedule a job to run through cron that checks for high CPU usage. The 'top' command is run and the output is logged to a file. A calculation is done in the file to check if CPU runs above 80%. If this happens an email is sent out. The problem I am having is that when I run this... (4 Replies)
Discussion started by: shehnaaz
4 Replies

3. UNIX for Advanced & Expert Users

crontab problem

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)
Discussion started by: NIMISH AGARWAL
4 Replies

4. Shell Programming and Scripting

CRONTAB problem

Hi i was working on an Unix server/ While logging out i used to type the command exit and log out. Yesterday when i was logging out i got an message saying "YOU HAVE STOPPED JOBS". i have not done anything other than giving exit. What could the reason the message was displayed. I thought i had... (3 Replies)
Discussion started by: venkidhadha
3 Replies

5. Shell Programming and Scripting

Crontab problem

Hi all, I made few changes to the script (under the directory mentioned in crontab) scheduled under crontab and the problem is that crontab doesnt pickup those changes and somehow runs the old copy of the script from somewhere. Any help would be appreciated. (8 Replies)
Discussion started by: vinoo128
8 Replies

6. AIX

Problem with crontab

Hi, Can anyone let me know the functionality of the following command in Unix crontab ;l Thanks, Wajith.M (3 Replies)
Discussion started by: Wajith
3 Replies

7. UNIX for Dummies Questions & Answers

Crontab problem!

Hi All, i added a sh script to crontab, it run but there is sqlplus expression that generate a spool file(gun.lst). this expression didnt run. Summary, 1- my main script is topl.sh that i added it to Cron via "crontab -e" command 2- There is "sqlplus username/password@serverA @umt.sql"... (6 Replies)
Discussion started by: temhem
6 Replies

8. UNIX for Dummies Questions & Answers

Problem with my crontab file, using mysqldump

My crontab file tells cron to run a certain shell script at 10:30 AM every day. The shell script backs up my database with mysqldump and then runs a sed script that does some editing of the backup file. I have programmed the shell script to write an error message to a file I have in my home... (1 Reply)
Discussion started by: Ultrix
1 Replies

9. Shell Programming and Scripting

Problem with crontab

Hi, I have one script which takes data from table and spools it into a file. When i am running manually all is fine but while trying same script thru crontab the spooled file is not getting generated..... :confused: The mail part is working fine....only prob is the spooled file. Please... (15 Replies)
Discussion started by: fidelis
15 Replies

10. Solaris

crontab problem

online* 22:25:22 svc:/system/cron:default cron service not able to start i tried to disble it is not working. showing online* status. thanks (1 Reply)
Discussion started by: sunnybee
1 Replies
CRONTAB(1)							   User Commands							CRONTAB(1)

NAME
crontab - maintains crontab files for individual users SYNOPSIS
crontab [-u user] file crontab [-u user] [-l | -r | -e] [-i] [-s] crontab -n [ hostname ] crontab -c DESCRIPTION
Crontab is the program used to install, remove or list the tables used to serve the cron(8) daemon. Each user can have their own crontab, and though these are files in /var/spool/, they are not intended to be edited directly. For SELinux in MLS mode, you can define more crontabs for each range. For more information, see selinux(8). In this version of Cron it is possible to use a network-mounted shared /var/spool/cron across a cluster of hosts and specify that only one of the hosts should run the crontab jobs in the particular directory at any one time. You may also use crontab(1) from any of these hosts to edit the same shared set of crontab files, and to set and query which host should run the crontab jobs. Running cron jobs can be allowed or disallowed for different users. For this purpose, use the cron.allow and cron.deny files. If the cron.allow file exists, a user must be listed in it to be allowed to use cron If the cron.allow file does not exist but the cron.deny file does exist, then a user must not be listed in the cron.deny file in order to use cron. If neither of these files exists, only the super user is allowed to use cron. Another way to restrict access to cron is to use PAM authentication in /etc/security/access.conf to set up users, which are allowed or disallowed to use crontab or modify system cron jobs in the /etc/cron.d/ directory. The temporary directory can be set in an environment variable. If it is not set by the user, the /tmp directory is used. OPTIONS
-u Appends the name of the user whose crontab is to be modified. If this option is not used, crontab examines "your" crontab, i.e., the crontab of the person executing the command. Note that su(8) may confuse crontab, thus, when executing commands under su(8) you should always use the -u option. If no crontab exists for a particular user, it is created for him the first time the crontab -u command is used under his username. -l Displays the current crontab on standard output. -r Removes the current crontab. -e Edits 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. -i This option modifies the -r option to prompt the user for a 'y/Y' response before actually removing the crontab. -s Appends the current SELinux security context string as an MLS_LEVEL setting to the crontab file before editing / replacement occurs - see the documentation of MLS_LEVEL in crontab(5). -n This option is relevant only if cron(8) was started with the -c option, to enable clustering support. It is used to set the host in the cluster which should run the jobs specified in the crontab files in the /var/spool/cron directory. If a hostname is supplied, the host whose hostname returned by gethostname(2) matches the supplied hostname, will be selected to run the selected cron jobs subsequently. If there is no host in the cluster matching the supplied hostname, or you explicitly specify an empty hostname, then the selected jobs will not be run at all. If the hostname is omitted, the name of the local host returned by gethostname(2) is used. Using this option has no effect on the /etc/crontab file and the files in the /etc/cron.d directory, which are always run, and considered host-specific. For more information on clustering support, see cron(8). -c This option is only relevant if cron(8) was started with the -c option, to enable clustering support. It is used to query which host in the cluster is currently set to run the jobs specified in the crontab files in the directory /var/spool/cron , as set using the -n option. 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
An informative usage message appears if you run a crontab with a faulty command defined in it. AUTHOR
Paul Vixie <vixie@isc.org> Colin Dean <colin@colin-dean.org> cronie 2012-11-22 CRONTAB(1)
All times are GMT -4. The time now is 03:27 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy