04-21-2006
create a file in the /tmp directory and have your script check for it. If it is there then dont start. If it is not there then start and delete the file when you're done.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I'm new to cron and I would like to know if this cron entry looks right.
Every monday to friday, at 9:15 AM execute the script called done_att.sh
Every monday to friday, at 3:15 PM execute the script called start_att.sh
15 09 * * /u54/jobs/done_att.sh
45 15 * *... (1 Reply)
Discussion started by: ted
1 Replies
2. UNIX for Dummies Questions & Answers
I would like to add a job using cron. I have following questions
- cron jobs are launched using what login-id
e.g. is the script launced using my login-id
- In which directory would the cron jobs be launched ?
- where do the environment variables required in the script being lauched come... (3 Replies)
Discussion started by: sharanbr
3 Replies
3. UNIX for Advanced & Expert Users
Before I get a million and one suggestions on all the things that could be wrong with my scripts - let me assure everyone that this is not the issue.
i have a RH EL ES4 server that stopped running all cron jobs except hourly, daily, weekly.
This has affected all users including root. No... (7 Replies)
Discussion started by: bill_k_Lopez
7 Replies
4. UNIX for Dummies Questions & Answers
Hi Everyone,
I have written a korn shell script to shutdown my documentum docbase server and to restart it automatically on a weekly basis. My script is,
When i execute this script manually, i was able to execute it successfully without any issues. I have scheduled this script in cronjob... (1 Reply)
Discussion started by: Sheethal
1 Replies
5. OS X (Apple)
I have a cron job set up to run a script on my Leopard Server every night. The job is set up as root, and when I run the script manually, it runs fine.
The problem is that it is not doing anything when it runs at night. In the cron log, it says it ran, but did not output the results to the file it... (3 Replies)
Discussion started by: yodomino6
3 Replies
6. Shell Programming and Scripting
Hi guys,
I've got a few cron jobs ... porblem is they are running as intended but some of them just tend to stay there in sleeping mode for quite some time ... sometimes even days ... for example when i run the ps command i can see that some are still there although the same script had run many... (6 Replies)
Discussion started by: King Nothing
6 Replies
7. Solaris
Hi,
I am logging into sun solaris unix box as asood user.Then sudo su_appssu
and scheduled my cron jobs.The user appssu is there In the /etc/cron.d/cron.allow . I do not understand why the jobs are not kicking by cron. Do I need to enter directly as appssu ?
Regards
Megh (10 Replies)
Discussion started by: megh
10 Replies
8. Shell Programming and Scripting
Hi
Is it possible to run different cron jobs at the same time? It appears that when I run ones at 15 min granularity that they may prevent ones running later in the day.
Should crons run at same time have impact on one another? (4 Replies)
Discussion started by: rob171171
4 Replies
9. Red Hat
Hi unix.com,
I'm currently experiencing a problem on one of our servers at work where between the hours of approx. 1:00 AM and 2:0 AM no jobs scheduled through cron run.
Now, in the cron logs I do see that all jobs are launched and I'm not seeing any errors anywhere - but - none of the jobs... (2 Replies)
Discussion started by: tunachamp
2 Replies
10. UNIX for Beginners Questions & Answers
on linux redhat, ubuntu systems, what reason would there be for a cron job not running at exactly the time it was scheduled to run, everytime?
meaning, if i put something in cron to run every 120 seconds (2 minutes), why is it that some times, i find that cron would sometimes run the job a few... (1 Reply)
Discussion started by: SkySmart
1 Replies
LEARN ABOUT SUNOS
start-domain
asadmin-start-domain(1AS) User Commands asadmin-start-domain(1AS)
NAME
asadmin-start-domain, start-domain - starts the given domain
SYNOPSIS
start-domain [--domaindir install_dir/domains] [--terse=false] [--echo=false] [--verbose=false] [--debug] [domain_name]
start-domain starts the specified domain. If there is only one domain in the default domain directory (install_dir/domains), then no oper-
and is required to start the domain. However, if there is more than one domain, the domain operand must be specified. This command can only
be run locally.
OPTIONS
--domaindir directory where the domain is to be started. If specified, path must be accessible in the filesystem. If not speci-
fied, the domain is started in the default install_dir/domains directory.
--terse indicates that any output data must be very concise, typically avoiding human-friendly sentences and favoring well-
formatted data for consumption by a script. Default is false.
--echo setting to true will echo the command line statement on the standard output. Default is false.
--verbose by default this flag is set to false. If set to true, detailed server startup output is displayed. Press CTRL-C to
kill the server. Press CTRL- to print a thread dump.
--debug by default this flag is set to false. If set to true, the server is started in debug mode and prints the JPDA port
on the console.
OPERANDS
domain_name name of the domain. Must be a unique name.
Example 1: Using start-domain
asadmin> start-domain sampleDomain
Starting Domain sampleDomain, please wait.
Domain sampleDomain started
Where: the sampleDomain domain is started.
EXIT STATUS
0 command executed successfully
1 error in executing the command
asadmin-create-domain(1AS), asadmin-delete-domain(1AS), asadmin-stop-domain(1AS), asadmin-list-domains(1AS)
J2EE 1.4 SDK March 2004 asadmin-start-domain(1AS)