12-13-2008
Execution problems with crontab
I need your help please
Inin a production system i found crontab entries was removed because i typed crontab -l with username corasc and didn't show anything.
i asked the administrador to restored the mentioned crontab, he restored the crontab:
The problem is when restored the crontab file is not executing any entry:
What happenned:?
i checked up the /usr/lib/cron/cron.allow and the username corasc is included, also checkup the /usr/lib/cron/cron.deny and it doesn exist
i checked up the crontab file and permissions and:
ls -lrt /var/spool/cron/crontabs/corasc
-r-------- 1 root colombia 1072 Dec 4 02:50/var/spool/cron/crontabs/corasc
BEFORE BEING REMOVED THE CRONTAB, IT WAS WORKING, si i show you the crontab lines
corasc@altamira00 : corasc > crontab -l
#Logs maintainance
0 0 * * * /usr/bin/find /export/app/CO/rasc/log/xa -name "*.trc" -mtime +2 -exec rm -f {} \; > /dev/null 2>&1
0 0 * * * /usr/bin/find /export/app/CO/rasc/log/ULOG -name "ULOG." -mtime +2 -exec rm -f {} \; > /dev/null 2>&1
0 0 * * * /usr/bin/find /export/app/CO/rasc/log/MAS "*.log" -mtime +2 -exec rm -f {} \; > /dev/null 2>&1
# Generacion Pines
00 2 * * * /export/app/CO/rasc/scr/lanza_generacion_pines.sh > /dev/null 2>&1
# Informes
0 3 1 * * /export/app/CO/rasc/scr/Informe_Tarjetas.ksh > /dev/null 2>&1
52 05 08 * * /export/app/CO/rasc/scr/Informe_Tarjetas.ksh > /export/app/CO/rasc/scr/log_Tarjetas.txt > /dev/null 2>&1
# Generacion de estadisticas
5 0 * * * /export/home/corasc/scripts/EstadisticasTUX.ksh > /export/app/CO/rasc/log/EstadisticasTUX.log > /dev/null 2>&1
I'd appreciate your help thanks
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
is it possible to soecify time overnight in 5 days for example:
0 18-7 * * 1-5 /mycode
is this okay to use 18-7 because im not getting the results correctly? (4 Replies)
Discussion started by: vadharah
4 Replies
2. UNIX for Dummies Questions & Answers
Hi All,
Do apologise, for it has been a long while since I was last on the forum. I've been doing documentation and primiarily Windows efforts for some while now. :(
We are running a HP-UX 11.23 unit. This morning two separate crontab users executed shutdown scripts of their respective... (14 Replies)
Discussion started by: Cameron
14 Replies
3. UNIX for Dummies Questions & Answers
Hi
I have shell script to excute the SQL script.And i have scheduled those shell script in crontab.But the Shell script is not running timely and i got the below error
Crontab entry
15 05 17 7 * /export/home/vcpsapp/vcps/stat.sh
Output
Your "cron" job on uspxivus16... (3 Replies)
Discussion started by: mak_boop
3 Replies
4. Shell Programming and Scripting
i have been working on this for a about 12 hours today say's end of file un expected any idea's
using the bourne shell and its driving me nuts worked fine in bash but prof says make it work in bourne and good luck worth 13%
any help would be awesome
#!/bin/sh
trap "rm mnt2/source/tmp/* 2>... (1 Reply)
Discussion started by: mrhiab
1 Replies
5. Shell Programming and Scripting
Hi,
I have shell script "A" which is executing oracle pl/sql procedure and initiate its multiple threads at a time as below on given user value in an other script "B".
I want to execute script "A" after every second with out cron tab as " A " will keep on executing after every second till... (1 Reply)
Discussion started by: saad.imran@gmai
1 Replies
6. Shell Programming and Scripting
Hi All,
I am facing a problem with crontab.I made an entry in crontab like this
05 07 * * * /afs2/cdwfullacc/current/exe/cdw_generate_special_klant.sh > /afs2/cdwfullacc/current/scratch/cdw_gen_cron.log
But job was not getting executed.
Entry in crontab was made with same user by whom... (4 Replies)
Discussion started by: krishna_gnv
4 Replies
7. Shell Programming and Scripting
this my source file
************* fixed ***************
Begin
equipmentId : d9
processor : fox
number : bhhhhhh
Variable # 1:
Id : 100
Type : 9
nType : s
gType : 5f
mType : 4
LField : England
DataField : london
Length ... (6 Replies)
Discussion started by: teefa
6 Replies
8. UNIX for Dummies Questions & Answers
Dear Folks,
I have written a shell script which internally connects to oracle database through sqplplus command line.
The script runs fine when run manually.
Now I am scheduling it to run (Linux environment) from crontab.
In crontab it is failing with an error:
sqlplus command... (6 Replies)
Discussion started by: tamojitc
6 Replies
9. HP-UX
Hi Guys,
I need help to clear my doubt w.r.t Crontab execution.
uname -a
HP-UX myservername B.11.31 U ia64 1422528451 unlimited-user licenseI created a crontab entry to execute particular job on Saturday 11/15/2014 11:22
Below is the cron entry
#refresh DEVDB from PRODDB
22 11 15 11 6... (6 Replies)
Discussion started by: rocky.community
6 Replies
10. UNIX for Beginners Questions & Answers
How to find a word in a directory which contains many files?
i just want to count how many such words are present in all the files?
This is the code which i tried for a single file
echo "Enter the file name:"
read file
echo "Enter the word to search:"
read word
if
then
echo "The count... (4 Replies)
Discussion started by: Meeran Rizvi
4 Replies
LEARN ABOUT MINIX
crontab
CRONTAB(1) General Commands Manual CRONTAB(1)
NAME
crontab - maintain crontab files for individual users (Vixie Cron)
SYNOPSIS
crontab [ -u user ] file
crontab [ -u user ] [ -i ] { -e | -l | -r }
DESCRIPTION
crontab is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user can have
their own crontab, and though these are files in /var/spool/cron/crontabs, they are not intended to be edited directly.
If the /etc/cron.allow file exists, then you must be listed (one user per line) therein in order to be allowed to use this command. If the
/etc/cron.allow file does not exist but the /etc/cron.deny file does exist, then you must not be listed in the /etc/cron.deny file in order
to use this command.
If neither of these files exists, then depending on site-dependent configuration parameters, only the super user will be allowed to use
this command, or all users will be able to use this command.
If both files exist then /etc/cron.allow takes precedence. Which means that /etc/cron.deny is not considered and your user must be listed
in /etc/cron.allow in order to be able to use the crontab.
Regardless of the existance of any of these files, the root administrative user is always allowed to setup a crontab. For standard Debian
systems, all users may use this command.
If the -u option is given, it specifies the name of the user whose crontab is to be used (when listing) or modified (when editing). 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. See the note under DEBIAN SPECIFIC below.
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. If neither of the environment variables is defined, then the default
editor /usr/bin/editor is used.
The -i option modifies the -r option to prompt the user for a 'y/Y' response before actually removing the crontab.
DEBIAN SPECIFIC
The "out-of-the-box" behaviour for crontab -l is to display the three line "DO NOT EDIT THIS FILE" header that is placed at the beginning
of the crontab when it is installed. The problem is that it makes the sequence
crontab -l | crontab -
non-idempotent -- you keep adding copies of the header. This causes pain to scripts that use sed to edit a crontab. Therefore, the default
behaviour of the -l option has been changed to not output such header. You may obtain the original behaviour by setting the environment
variable CRONTAB_NOHEADER to 'N', which will cause the crontab -l command to emit the extraneous header.
SEE ALSO
crontab(5), cron(8)
FILES
/etc/cron.allow
/etc/cron.deny
/var/spool/cron/crontabs
There is one file for each user's crontab under the /var/spool/cron/crontabs directory. Users are not allowed to edit the files under that
directory directly to ensure that only users allowed by the system to run periodic tasks can add them, and only syntactically correct
crontabs will be written there. This is enforced by having the directory writable only by the crontab group and configuring crontab com-
mand with the setgid bid set for that specific group.
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.
cron requires that each entry in a crontab end in a newline character. If the last entry in a crontab is missing the newline, cron will
consider the crontab (at least partially) broken and refuse to install it.
AUTHOR
Paul Vixie <paul@vix.com> is the author of cron and original creator of this manual page. This page has also been modified for Debian by
Steve Greenland, Javier Fernandez-Sanguino and Christian Kastner.
4th Berkeley Distribution 19 April 2010 CRONTAB(1)