04-11-2001
Hi, I need some help, because I'm trying to create a process runing all the time (not invoqued by a crontab), like a daemon, to detect the creation of a new file in a specific directory and axecute a process wich do something with this new file.
Can you help me?
For your information my Unix is a Unixware 7.1.1.
TKS.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
1. Do I need syslog running in my services?
2. Is there such a critter for counterstrike installer for linux or do i need to use winex (2 Replies)
Discussion started by: amicrawler2000
2 Replies
2. AIX
Hi,
I am elango. I am working with UNIX AIX version 5.
I am facing tow problem whenever I am trying to run a script.
1. The moment I run the script 3 more jobs are getting started automatically.
I used PS -ef command to check the running Jobs, I found totally 4 jobs
are running for... (4 Replies)
Discussion started by: Elango
4 Replies
3. Shell Programming and Scripting
I am working on a project, which need to constantly watch the process, and check its status, if it was dead, it should be restart automatically.
Please kindly refer me to URL which teach how to write this kind of script, or service.
Thanks. (1 Reply)
Discussion started by: dragondad
1 Replies
4. AIX
Hello,
I am creating oracle connection from one aix5.2 machine to another aix5.2 database machine. Oracle connection i am reusing it always. If there is now work for java thread to process, oracle instance will be idle and will be active once java thread processes.
We have installed OS... (1 Reply)
Discussion started by: balareddy
1 Replies
5. Shell Programming and Scripting
Hi all,
I'm doing automation task for my team and I just started to learn unix scripting so please shed some light on how to do this:
1) I have 2 sets of datafiles - datafile A and B. These datafiles must be loaded subsequently and cannot be loaded concurrently.
2) So I loaded datafile A... (10 Replies)
Discussion started by: luna_soleil
10 Replies
6. UNIX Desktop Questions & Answers
Hi,
I'm new to Linux.
I have a windows server that run many processes on it.
In some cases the processes doesn't exit properly or just stop working and the process needs to be killed.
I was wondering how i can automatically (couple of times a day) check which process doesn't use any CPU... (3 Replies)
Discussion started by: ramikom
3 Replies
7. Red Hat
Hello,
I am in the process of learning Linux OS.
How do I run the below lines of code automatically as root on server startup.
cd /opt/program_folder/ServiceManager/bin
nohup ./servce_manager DEV &
Currently, as soon as the server is up and running I log in as root (as this... (6 Replies)
Discussion started by: rparavastu
6 Replies
8. Shell Programming and Scripting
The `bash` below uses the oldest folder in the specified directory and logs it. The goes though an analysis process and creates a log. My problem is that if there are 3 folders in the directory folder1,folder2,folder3, the bash is using folder2 for the analysis eventhough folder1 is the oldest... (0 Replies)
Discussion started by: cmccabe
0 Replies
9. Shell Programming and Scripting
Hi ,
I have scheduled the script using cron between 25-31 of the month.
My script will trigger the ETL job once file is available in Windows path between these days(every 2 hours between 26 - 30 of every month ).
So my question : "if the ETL job completes cron should stop the running the... (5 Replies)
Discussion started by: Jaganjag
5 Replies
LEARN ABOUT MOJAVE
crontab
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