10-18-2012
So it is enabled. If you don't need it, then disable it temporarily with setenforce 0, then try running your cron job again.
10 More Discussions You Might Find Interesting
1. SCO
I have 2 questions :
----------------------------------
1 - How can I execute a program when Unix Sco reboot?
For example I have two script (two sockets) that I have to
start from 2 different users (root and toto).
I heard something about "etc/init.d" directory, but I don't know what to... (4 Replies)
Discussion started by: soshell
4 Replies
2. UNIX for Dummies Questions & Answers
hello. we are porting over from HPUX Shell to Linux.
my default shell is bash so i can no longer schedule to execute a sh script in crontab.
can anyone pls help me out? I searched the site but didnt find any details.
thanks! (1 Reply)
Discussion started by: jigarlakhani
1 Replies
3. UNIX for Dummies Questions & Answers
sh filename
and it gives me an error saying the file doesnt exist but it definately does. (4 Replies)
Discussion started by: iago
4 Replies
4. UNIX for Dummies Questions & Answers
Hi guys, my first post time here, so hello to everyone :)
I've got a problem running one of my scripts at work. I can get crontab working on simple scripts (i.e. one that just outputs date to a temp file). but it won't correctly execute the script i want to use.
My script is a PHP script. It... (6 Replies)
Discussion started by: renegadeice
6 Replies
5. Shell Programming and Scripting
i have logged in as user.
I want to write a script to login into root and execute commands for eg. ifconfig or other command.
kindly help me out. (6 Replies)
Discussion started by: pradeepreddy
6 Replies
6. Shell Programming and Scripting
Can anybody help me with this small script , the script works fine and launches the IE from
c:\documents and settings \test\my documents>ksh prompt
$RunURL1.sh
this scitpt works and launches the ie from ksh , but when i schedule it to run the script then i get the error box saying command:1... (2 Replies)
Discussion started by: venu
2 Replies
7. Shell Programming and Scripting
Im using a script that writes a random line to a text file then executes another shell script. My problem is that the lottery shell script will not execute. Im not receiving an errors when running the shell script, and it copies a random line of text to mtest.txt fine.
#!/bin/bash
nscripts=2... (3 Replies)
Discussion started by: kylecn
3 Replies
8. Shell Programming and Scripting
Hello All,
I have a crontab schedule and its executing a script that is calling another script and does not execute.
Crontab : ***** /test.sh
and in test.sh
/usr/local/file.sh
and in file.sh
webproxy -l 192.168.1.151
But when I run the script (test.sh) directly it works. But using... (1 Reply)
Discussion started by: Shaan_Shaan
1 Replies
9. Shell Programming and Scripting
Hi,
So I've created /etc/rc.local
#!/bin/sh
polipo -c /opt/etc/polipo/polipo.conf
exit 0
if I run it with ./rc.local it does what its supposed to do and the proxy starts but not at startup.
any idea whats wrong?
thanks (1 Reply)
Discussion started by: deon
1 Replies
10. Shell Programming and Scripting
Can someone please help me on how to schedule script to run every 45 days in crontab ?
Thanks,
Prince (5 Replies)
Discussion started by: prince1987
5 Replies
LEARN ABOUT OPENDARWIN
queuedefs
queuedefs(4) File Formats queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.10 1 Mar 1994 queuedefs(4)