10 More Discussions You Might Find Interesting
1. 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
2. HP-UX
Hello Anyone:
I have run into an issue that I have never seen or heard of.
Recently on a specific server I have encountered a random issue that I've not been able to repliate on demand... When I view the processes status of a certain process, the information returned to the screen has a... (2 Replies)
Discussion started by: DEN1022
2 Replies
3. 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
4. Shell Programming and Scripting
Hi All,
I am trying to execute a python script from a user's crontab.
/home/user1/UDE/scripts/UdeManager.py
I am at /home/user1.
If I run the command "/home/user1UDE/scripts/UdeManager.py" from the users home directory its working fine.
But when I try to run from user's cron tab its... (3 Replies)
Discussion started by: Tuxidow
3 Replies
5. Solaris
hi,
how can i assign a crontab to my username "user1", here is my current list details;
$ who
root console Nov 15 14:38
user1 pts/1 Dec 14 21:07 (192.168.1.75)
$ pwd
/etc/cron.d
$ ls -alh
total 20
drwxr-xr-x 2 root sys 512 Nov 15 14:37 .... (3 Replies)
Discussion started by: fspalero
3 Replies
6. UNIX for Dummies Questions & Answers
Hi Guys,
Our user crontab files are located at /var/spool/cron/crontabs.
I have to make some modifications to it.
I have all the crontab entries in a file called 'crontab.actual'. I made changes to this file and now I want to reload these changes from the crontab.actual file to my crontab... (12 Replies)
Discussion started by: vandi
12 Replies
7. 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
8. UNIX for Dummies Questions & Answers
Hi All,
I am user of partcular user of alinux machine. I want have some cronjobs to be done by machine. But i don't have crontab file for me. However i do have crontab installed as /usr/bin/crontab.
Could anyone please suggest how to creat a new cron file for a user? Any help will be highly... (3 Replies)
Discussion started by: bisla.yogender
3 Replies
9. UNIX for Dummies Questions & Answers
Hi!
I'm a bit noob on Unix/Linux world, so sorry any lame question i may make...
Oh.. and my english too.. is not so famous lol..
The deal is to use crontab to change my admin password every weak to something like "mypasswordcurrrentday" that is... i want evey weak to change my password but... (2 Replies)
Discussion started by: OdinPT
2 Replies
10. Linux
How can dump the user account detail? like how long need to change password, password naming policy, how many times will lock account if login failed..
thk a lot (1 Reply)
Discussion started by: zp523444
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)