Sponsored Content
Full Discussion: crontab -e error
Operating Systems Linux crontab -e error Post 302131378 by kahuna on Friday 10th of August 2007 09:31:00 AM
Old 08-10-2007
Quote:
Originally Posted by sysgate
Apparently it's permission issue, do a "ls -la /usr/bin/crontab" most probably it will be owned by root.
I assume that you mean the crontab data file (in /var/spool/cron/crontabs?) is owned by root, rather than the program file /usr/bin/crontab (which should be owned by root). Or are you suggesting that perhaps the setuid bid is not set on /usr/bin/crontab?
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

unexpected crontab error

Yesterday i installed a new cron on solaris box. After a few minutes after loading the cron, i got the following error. Your "crontab" on machine_name ! unexpected end of line This entry has been ignored. Do any of you have any idea about this error ? (12 Replies)
Discussion started by: dhanamurthy
12 Replies

2. UNIX for Dummies Questions & Answers

Crontab error

So I'm trying to set up a simple cron job to copy the contents of a folder to my local machine. When it's ran the following output is produced: sh: syntax error at line 1: `(' unexpected Here's line 1: scp -r user@host:/cygdrive/c/logfolder1/ /log_files/$(date +%m_%d_%Y) (2 Replies)
Discussion started by: kclerks11
2 Replies

3. UNIX for Advanced & Expert Users

crontab : bad minute error

when i say $crontab z it says ==> "z":6: bad minute "z":6: bad minute errors in crontab file, can't install. any clue why its happening? (1 Reply)
Discussion started by: crackthehit007
1 Replies

4. Shell Programming and Scripting

Crontab error

I have a script which is called in a crontab. The script calls for 2 args when ran on the command line The crontab line: 05 0-23 * * 0-6 /path/name %arg1 %arg1 I get the following output Your "cron" job on server /path/name produced the following output: Must be attached to... (4 Replies)
Discussion started by: Pablo_beezo
4 Replies

5. Solaris

Crontab error

Hi, I have following crontab en my user: */5 * * * * command it's don't run every Five minutes, why? Anyone know what is it happend? Thankyou. (2 Replies)
Discussion started by: peluso
2 Replies

6. UNIX for Dummies Questions & Answers

Error using crontab -e

I am trying to create a crontab job for my Oracle logon. I added oracle to the cron.allow file but when I try the crontab -e I get: Xlib:connection to 0:0 refused by server Xlib:Client is not authorized to connect to server Error:Cannot open display "0:0" crontab temporary file empty when... (3 Replies)
Discussion started by: dman110168
3 Replies

7. UNIX for Dummies Questions & Answers

Getting error when running script through crontab

Hi all, I wrote small script for Solaris and when I am running it through command prompt its ok, but when I trying to run it using crontab, i am getting error like: ld.so.1: dbloader: fatal: libACE.so: open failed: No such file or directory /tmp/file.sh: line 5: 8304 Killed ... (4 Replies)
Discussion started by: nypreH
4 Replies

8. UNIX for Dummies Questions & Answers

Error when trying to edit crontab

Hi Guys, I need to edit the crontab on one of my unix systems. When I execute crontab -e, nothing happens, then I get an error '666' and can't type anything else at the cli. I tried resizing the window, but still got the same error. I'm using the run user and I've checked the permissions on... (0 Replies)
Discussion started by: bbbngowc
0 Replies

9. Shell Programming and Scripting

Crontab setting error

Hi All, I have created crontab using following steps- 1) crontab -e (edited the file with) 0 10 * * 1-5 /home/user01/exercise/cron.sh 2) then saved this file with :wq 3) cron.sh contains the code- #!/bin/bash DAY=`date +%a` mkdir abc_${DAY} 4) done the execut permision... (3 Replies)
Discussion started by: pspriyanka
3 Replies

10. Solaris

crontab error

Hi, I run crontab -l ,then i got error message like "crontab: can't open your crontab file." I checked for entry in cron.allow and entry was present, nothing in cron.deny. Note: It is working for another user. Can someone suggest? (2 Replies)
Discussion started by: Mani_apr08
2 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 08:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy