06-15-2013
you do not need crontab entries to run scripts unless you just want them ... the user in question may be running the script directly on the command line or using at so there is no need to modify crontab ... also, the issue may be that it is running in a user's crontab so you may want to check the user crontab files for the entry ... i think your suspect is very likely running the script manually based on your description ...
if you need to restrict the script to one process only while it is running, modify your shell script to use a marker file or at least check for an existing PID of the process prior to continuing the script ... a search of the forums or google should show you how to do so ...
8 More Discussions You Might Find Interesting
1. Forum Support Area for Unregistered Users & Account Problems
Hi,
I need you help with my research project that attempts to determine the
link between users and manufacturers of IT Products such as Unix.
This is part of an MBA program that I'm currently pursuing. My challenge is that I cannot possibly find out how I can send my research... (1 Reply)
Discussion started by: Tdludlu
1 Replies
2. UNIX for Dummies Questions & Answers
I am doing a "research" paper for school and i'm having a hard time finding accurate information. I am supposed to choose three differant versions of unix, give a brief explination of each, tell why there each differant from each other. I have found a ton of web sites but the information is so vast... (1 Reply)
Discussion started by: pantsusan
1 Replies
3. Windows & DOS: Issues & Discussions
I am researching the reasons why Unix / Linux is the chosen operating system versus Windows. I have had difficutly narrowing down resources. I am wondering if anyone has any favorite sources that they would care to share.
Thanks
Dan (2 Replies)
Discussion started by: isenhart
2 Replies
4. Shell Programming and Scripting
menu should look at least like the following:-
RESEARCH PAPER LIBRARY - Main Menu
0 : EXIT this program
1 : EDIT menu
2 : REPORTS Menu
Enter your choice>
program should check for invalid choice and display error message and re-display the main-menu. If EDIT is... (1 Reply)
Discussion started by: SHakur_BIG
1 Replies
5. UNIX for Dummies Questions & Answers
hi friends i have just completed my graduation and applied for Post graduation
i have to submit a research proposal of OS in the interview
i m a beginner & only read galvin & silbershcatz book on operating systems
can anyone help me in that ...
thanks in advance (3 Replies)
Discussion started by: iet.manish
3 Replies
6. UNIX for Dummies Questions & Answers
Hi,
how to look for an expression like :
or
Client ChkAeStatus4 service
in VI ?
For a word , of cours :
/word (2 Replies)
Discussion started by: big123456
2 Replies
7. UNIX for Dummies Questions & Answers
Hi there, please could you assist me. I have no knowledge at all about Unix and I have applied for a job and they have given me a test and said that I can obtain the answers in any kind of way. There are 3 questions that I need answers for. I have tried researching the answers to these questions... (12 Replies)
Discussion started by: zakl
12 Replies
8. UNIX for Beginners Questions & Answers
Good Afternoon,
Are most NASs compatible with Solaris/RedHat? Specifically, I'm looking at Western Digital ones but none of them say they are - I like My Cloud Pro Series PR4100
My Cloud Pro Series PR4100 – Network Attached Storage | Western Digital (WD) (3 Replies)
Discussion started by: Stellaman1977
3 Replies
CRONTAB(1) BSD General Commands Manual CRONTAB(1)
NAME
crontab -- maintain crontab files for individual users (V3)
SYNOPSIS
crontab [-u user] file
crontab [-u user] { -l | -r | -e }
DESCRIPTION
The crontab utility 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 they are not intended to be edited directly.
(Darwin note: Although cron(8) and crontab(5) are officially supported under Darwin, their functionality has been absorbed into launchd(8),
which provides a more flexible way of automatically executing commands. See launchctl(1) for more information.)
If the /usr/lib/cron/cron.allow file exists, then you must be listed therein in order to be allowed to use this command. If the
/usr/lib/cron/cron.allow file does not exist but the /usr/lib/cron/cron.deny file does exist, then you must not be listed in the
/usr/lib/cron/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. The format of these
files is one username per line, with no leading or trailing whitespace. Lines of other formats will be ignored, and so can be used for com-
ments.
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 following options are available:
-u Specify the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines ``your'' crontab, i.e.,
the crontab of the person executing the command. Note that su(1) can confuse crontab and that if you are running inside of su(1) you
should always use the -u option for safety's sake.
-l Display the current crontab on standard output.
-r Remove the current crontab.
-e Edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. The specified editor must edit
the file in place; any editor that unlinks the file and recreates it cannot be used. After you exit from the editor, the modified
crontab will be installed automatically.
FILES
/usr/lib/cron/cron.allow
/usr/lib/cron/cron.deny
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
SEE ALSO
crontab(5), compat(5), cron(8), launchctl(1)
STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2''). The new command syntax differs from previous versions of Vixie Cron, as well
as from the classic SVR3 syntax.
AUTHORS
Paul Vixie <paul@vix.com>
BSD
December 29, 1993 BSD