03-23-2011
Quote:
Originally Posted by
rob171171
so something else is preventing it run in cron??
It could be your environment or it could be the script. Try running it in cron with out redirection. In other words, remove any "
> /dev/null 2>&1" in the crontab entry.
Also, I am not familiar with Perl, but is there a switch you can put in the first line of the script that will show each line as it is executed? I am thinking of something similar to "
-x" in Korn Shell.
This User Gave Thanks to bluescreen For This Post:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
hi..
i wolud like to know if itīs possible use the crontab command in my script.
the idea is what the script starts automatically, but i donīt know how to do it.
please, help me....
thanks
jonathan (1 Reply)
Discussion started by: DebianJ
1 Replies
2. UNIX for Dummies Questions & Answers
I want to add one line to the end of my crontab using a script.
I have tried piping in the editor commands, but I can't get it to work.
crontab -e user << EX
$a
This is the text I want to add.
.
wq
EX
This doesn't work. Is there an easier way to do this? (2 Replies)
Discussion started by: johnmsucpe
2 Replies
3. Shell Programming and Scripting
I know my question maybe eazy, but it realy cause a problem for me
I have a Perl script to run and get some output, I run this script using perl /moutaz/ciscolog/telnet.pl
I made another script as follow:(/moutaz/ciscolog/script)
#!/bin/bash
perl /moutaz/ciscolog/telnet.pl
cp... (6 Replies)
Discussion started by: moutaz1983
6 Replies
4. Shell Programming and Scripting
Hi!
We are on AIX 5.3
I have a script that must be run once every hour.
How do i add this to the crontab?
I know how to access crontab which is, crontab -e.
What do i do after that ? If i have the path to the script?
Thank you!!! (4 Replies)
Discussion started by: atechcorp
4 Replies
5. Shell Programming and Scripting
Hi All,
I am running a script to find the CPU and memory utilization of the server. Script name is atul. When i run this script then it gives the desired output as DATE, CPU and MEMORY utilization....as mentioned below:
$
$ cat atul
A=`date| cut -d" " -f1-4; top -d 1 -n 1 | awk '/^CPU... (5 Replies)
Discussion started by: atulbassi83
5 Replies
6. UNIX for Dummies Questions & Answers
Hi guys
Can someone help me with a crontab script please?
I have to sort the files from /bin and put the first 3 of then (with size and path) in /home/user/bin_size
i write the command:
find /bin/ | xargs ls -lS | awk 'FNR<4{print($5, $9)}' > /home/user/bin_size which is working but when I... (2 Replies)
Discussion started by: G30
2 Replies
7. UNIX for Dummies Questions & Answers
Hi guys
Can someone help me with a crontab script please?
I have to sort the files from /bin and put the first 3 of then (with size and path) in /home/user/bin_size
i write the command:
find /bin/ | xargs ls -lS | awk 'FNR<4{print($5, $9)}' > /home/user/bin_size
which is working but when... (6 Replies)
Discussion started by: G30
6 Replies
8. UNIX for Dummies Questions & Answers
Hi guys today i'll bring to you a new problem that i need to execute.
So what i need to do it's create a script that:
conect to some database
logon
run a .sql script
logoff
and close the connection
after that, put this script on the crontab
To set up the crontab it's ok for me, i think... (3 Replies)
Discussion started by: Newer
3 Replies
9. UNIX for Dummies Questions & Answers
Hi All,
I am having the below script to be run from crontab, it it doesnt run.
1 * * * * /home/cobr_ext/test.sh > /home/cobr_ext/temp.txt
when i run i manally it runs without any issues.
Could please help me as to why doesnt it run the script.:( (7 Replies)
Discussion started by: abhi_123
7 Replies
10. UNIX for Dummies Questions & Answers
I have crontab setup via crontab -e
I was wondering if its possible to create a cron job from a script so when the script is run the cron job is created? (3 Replies)
Discussion started by: scriptnewbie
3 Replies
LEARN ABOUT OPENSOLARIS
cron
cron(1M) System Administration Commands cron(1M)
NAME
cron - clock daemon
SYNOPSIS
/usr/sbin/cron
DESCRIPTION
cron starts a process that executes commands at specified dates and times.
You can specify regularly scheduled commands to cron according to instructions found in crontab files in the directory
/var/spool/cron/crontabs. Users can submit their own crontab file using the crontab(1) command. Commands which are to be executed only once
can be submitted using the at(1) command.
cron only examines crontab or at command files during its own process initialization phase and when the crontab or at command is run. This
reduces the overhead of checking for new or changed files at regularly scheduled intervals.
As cron never exits, it should be executed only once. This is done routinely by way of the svc:/system/cron:default service. The file
/etc/cron.d/FIFO file is used as a lock file to prevent the execution of more than one instance of cron.
cron captures the output of the job's stdout and stderr streams, and, if it is not empty, mails the output to the user. If the job does not
produce output, no mail is sent to the user. An exception is if the job is an at(1) job and the -m option was specified when the job was
submitted.
cron and at jobs are not executed if your account is locked. Jobs and processses execute. The shadow(4) file defines which accounts are not
locked and will have their jobs and processes executed.
Setting cron Jobs Across Timezones
The timezone of the cron daemon sets the system-wide timezone for cron entries. This, in turn, is by set by default system-wide using
/etc/default/init. The timezone for cron entries can be overridden in a user's crontab file; see crontab(1).
If some form of daylight savings or summer/winter time is in effect, then jobs scheduled during the switchover period could be executed
once, twice, or not at all.
Setting cron Defaults
To keep a log of all actions taken by cron, you must specify CRONLOG=YES in the /etc/default/cron file. If you specify CRONLOG=NO, no log-
ging is done. Keeping the log is a user configurable option since cron usually creates huge log files.
You can specify the PATH for user cron jobs by using PATH= in /etc/default/cron. You can set the PATH for root cron jobs using SUPATH= in
/etc/default/cron. Carefully consider the security implications of setting PATH and SUPATH.
Example /etc/default/cron file:
CRONLOG=YES
PATH=/usr/bin:/usr/ucb:
This example enables logging and sets the default PATH used by non-root jobs to /usr/bin:/usr/ucb:. Root jobs continue to use
/usr/sbin:/usr/bin.
The cron log file is periodically rotated by logadm(1M).
FILES
/etc/cron.d Main cron directory
/etc/cron.d/FIFO Lock file
/etc/default/cron cron default settings file
/var/cron/log cron history information
/var/spool/cron Spool area
/etc/cron.d/queuedefs Queue description file for at, batch, and cron
/etc/logadm.conf Configuration file for logadm
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
svcs(1), at(1), crontab(1), sh(1), logadm(1M), svcadm(1M), queuedefs(4), shadow(4), attributes(5), rbac(5), smf(5), smf_security(5)
NOTES
The cron service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/cron:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command. Most administrative actions may be delegated to users with the solaris.smf.man-
age.cron authorization (see rbac(5) and smf_security(5)).
DIAGNOSTICS
A history of all actions taken by cron is stored in /var/cron/log and possibly in /var/cron/olog.
SunOS 5.11 4 Feb 2009 cron(1M)