03-31-2002
Crontab Usage & ToubleShooting.....
Hi
------------------------------------------------------------------------------------
CRONTAB USAGE : For Using "crontab" utility to Edit Cron Files
using Vi as the Editor, perform the below mentioned Steps.
# EDITOR=vi; export EDITOR;
# crontab -e <username>
U will get a Vi Editor Screen for editing the mentioned User's Cron File. { Only use this way to edit any Cron File, as directly editing the Cron files might corrupt the File }
------------------------------------------------------------------------------------
CRONTAB TROUBLESHOOTING : If Ur Cronjob is not getting executed correctly, Then check for the below mentioned....
1. Check for the Permissions of the Cron File and Syntax of its contents.
# ls -l /var/spool/cron/crontabs/
total 4
-r-------- 1 root other 310 Mar 31 12:50 backup_user
-r-------- 1 root root 424 Feb 21 21:41 root
2. Check the UserName Entries present in the below mentioned Files.
/etc/cron.d/cron.allow
/etc/cron.d/cron.deny
3. Check whether Daemon for Cron is running or not.
# ps -ef |grep cron |grep -v grep
root 183 1 0 Mar 28 ? 0:03 /usr/sbin/cron
4. If the Daemon is not running, Restart the Daemon as mentioned below
# /etc/init.d/cron stop
# /etc/init.d/cron start
5. If U are executing any customised Shell Scripts using Cron,
then U have to check whether proper Execute Permissions are
provided for that Cron User.
------------------------------------------------------------------------------------
If U still face any problem, Kindly get back with Proper Error Messages updated in the /var/adm/messages File.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a server running 5.9 and I'm trying to cron in the following.
00 01 * * 7 cd /data/apache/logs && find . -type f -name "access.*" -mtime +1 -print |xargs rm > /dev/null 2>&1
But I keep get the following error....
00 01 * * 7 cd /data/apache/logs && find . -type f -name "access.*"... (2 Replies)
Discussion started by: Zak
2 Replies
2. Shell Programming and Scripting
HI,
i am working on linux.
i have crontab problem
i wrote a small script and put it in a crontab .
but the script is not running..
i have given following way in crontab -e
02 06 * * * /bin/csh /home/vr_test.csh
but the above script is not running
please rectify my... (26 Replies)
Discussion started by: rajan_ka1
26 Replies
3. UNIX for Dummies Questions & Answers
I'm trying to get crontab to run a script, but to test crontab I tried out a very simple command: `echo bob`
here is my crontab file (I edited it by using `crontab -e`):
-----------------
#!/bin/sh
23 10 * * * echo bob
and at 10:23 every day I get a new message:
in /var/mail/a... (3 Replies)
Discussion started by: cleansing_flame
3 Replies
4. UNIX for Dummies Questions & Answers
i added to my crontab file:
* * * * * echo "hello"
it works, i receive a message into my /var/mail/username
and i receive: bob
in addition to a large text add-on
any help appreciated (1 Reply)
Discussion started by: cleansing_flame
1 Replies
5. UNIX for Advanced & Expert Users
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
6. Shell Programming and Scripting
Dear All ,
I have .sh script wich has the following inside
getFileName=Listportfolio.txt.`date +'%Y%m%d`
ftp -n 172.10.10.1<<EOF
user xxx xxx
bin
cd /home/gbs/FTP_Script
get /home/gbs/FTP_Script/$getFileName
bye
EOF
EOF
when I run the... (3 Replies)
Discussion started by: habuzahra
3 Replies
7. Shell Programming and Scripting
Hi All,
Am facing an issue while updating the crontab.Getting below error while updating the cron.
cron/tmp.XXXX5fXBR6: No space left on device
crontab: edits left in /tmp/crontab.XXXXEJX5gw
Is there any file where i need to alter using root user so that i can update the cron.
TIA... (9 Replies)
Discussion started by: Ashok_oct22
9 Replies
8. AIX
Hi to all.
Guys, i have a truble with oracle user crontab.
He work if i'm do
0-59 * * * * echo LOL> ~/test.txt
But not work if me set realy norm date
For example
14 17 28 12 * echo LOL> ~/test.txt
In 17:14 28 December .
In log file /var/adm/cron/log nothing....
Please... (3 Replies)
Discussion started by: jess_t03
3 Replies
9. UNIX for Advanced & Expert Users
hi..
i have a program (tf.sh), and i want what it runs automatically with a "lapsus" of 2 hours. (1,3,5,7,9,11,13,15,17,19,21,23 hrs.)
i know what i have to do it using crontab, but i donīt know how to do it.
i have the next idea, but the problem is what it doesnīt run on my server... (11 Replies)
Discussion started by: DebianJ
11 Replies
10. Solaris
hi all
does any on has explanation for this result
bash-3.00$ crontab -e
"/var/tmp/Ex1kayUW" No space left on device
The crontab file was not changed.
bash-3.00$ (2 Replies)
Discussion started by: osmannix
2 Replies
LEARN ABOUT CENTOS
passwd
PASSWD(5) Linux Programmer's Manual PASSWD(5)
NAME
passwd - password file
DESCRIPTION
The /etc/passwd file is a text file that describes user login accounts for the system. It should have read permission allowed for all
users (many utilities, like ls(1) use it to map user IDs to usernames), but write access only for the superuser.
In the good old days there was no great problem with this general read permission. Everybody could read the encrypted passwords, but the
hardware was too slow to crack a well-chosen password, and moreover the basic assumption used to be that of a friendly user-community.
These days many people run some version of the shadow password suite, where /etc/passwd has an 'x' character in the password field, and the
encrypted passwords are in /etc/shadow, which is readable by the superuser only.
If the encrypted password, whether in /etc/passwd or in /etc/shadow, is an empty string, login is allowed without even asking for a pass-
word. Note that this functionality may be intentionally disabled in applications, or configurable (for example using the "nullok" or
"nonull" arguments to pam_unix.so).
If the encrypted password in /etc/passwd is "*NP*" (without the quotes), the shadow record should be obtained from an NIS+ server.
Regardless of whether shadow passwords are used, many system administrators use an asterisk (*) in the encrypted password field to make
sure that this user can not authenticate him- or herself using a password. (But see NOTES below.)
If you create a new login, first put an asterisk (*) in the password field, then use passwd(1) to set it.
Each line of the file describes a single user, and contains seven colon-separated fields:
name:password:UID:GID:GECOS:directory:shell
The field are as follows:
name This is the user's login name. It should not contain capital letters.
password This is either the encrypted user password, an asterisk (*), or the letter 'x'. (See pwconv(8) for an explanation of 'x'.)
UID The privileged root login account (superuser) has the user ID 0.
GID This is the numeric primary group ID for this user. (Additional groups for the user are defined in the system group file; see
group(5)).
GECOS This field (sometimes called the "comment field") is optional and used only for informational purposes. Usually, it contains
the full username. Some programs (for example, finger(1)) display information from this field.
GECOS stands for "General Electric Comprehensive Operating System", which was renamed to GCOS when GE's large systems division
was sold to Honeywell. Dennis Ritchie has reported: "Sometimes we sent printer output or batch jobs to the GCOS machine. The
gcos field in the password file was a place to stash the information for the $IDENTcard. Not elegant."
directory This is the user's home directory: the initial directory where the user is placed after logging in. The value in this field is
used to set the HOME environment variable.
shell This is the program to run at login (if empty, use /bin/sh). If set to a nonexistent executable, the user will be unable to
login through login(1). The value in this field is used to set the SHELL environment variable.
FILES
/etc/passwd
NOTES
If you want to create user groups, there must be an entry in /etc/group, or no group will exist.
If the encrypted password is set to an asterisk (*), the user will be unable to login using login(1), but may still login using rlogin(1),
run existing processes and initiate new ones through rsh(1), cron(8), at(1), or mail filters, etc. Trying to lock an account by simply
changing the shell field yields the same result and additionally allows the use of su(1).
SEE ALSO
login(1), passwd(1), su(1), getpwent(3), getpwnam(3), crypt(3), group(5), shadow(5)
COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2012-05-03 PASSWD(5)