06-28-2012
The environment, including CLASSPATH and PATH has to be defined. It is not by default. You have to be sure your environment is the same in cron as it is for you on the command line.
10 More Discussions You Might Find Interesting
1. Solaris
Hi,
I was trying to use this particular option of grep
grep -r 'Search_pattern' *
This command should ideally search all the occurrences of Search_pattern recursively within a directory & print it on shell prompt. But this command is not doing what is expected. It just displays nothin!
... (8 Replies)
Discussion started by: harishmitty
8 Replies
2. UNIX for Dummies Questions & Answers
Hi,
I am trying to figure out which version I am running of sendmail, but I am buffed.
This is what I get
sendmail -d0.1 -bt < /dev/null
sendmail: illegal option -- d
Telneting to my host:
~]$ telnet localhost 25
Trying 127.0.0.1...
Connected to localhost.
Escape character is... (1 Reply)
Discussion started by: saariko
1 Replies
3. AIX
Greetings everybody,
I have an IBM P520 AIX 5.3 server machine and trying to use crontab to periodically excute a script that contains a command belongs to my software (Fast/Tools SCADA software)
I added the following line after using crontab -e
01 * * * * /mypath/myscript
I have two... (3 Replies)
Discussion started by: ayman metwally
3 Replies
4. UNIX for Dummies Questions & Answers
#! /usr/tsch
foreach f (`cat contacts.list`)
awk '{printf ($2 in a) ? ","$5 : (NR>1) ? RS $2 FS $5 : $2 FS $5; a} END{print e}' $f > $f_inter.map
end
My file: cat contacts.list is just a list of files.
I get this error:
doit_contacts2intermap.sh: Command not found.
Thanks! (1 Reply)
Discussion started by: lost
1 Replies
5. Shell Programming and Scripting
Greetings all. :)
I would like to use sed to join all non-blank lines together in a particular file. I was thinking I could do this by simply replacing the terminating, new-line character on every line which is not blank, but I must be missing something in my sed line:
$ sed... (3 Replies)
Discussion started by: SteveB-in-LV
3 Replies
6. Shell Programming and Scripting
awk 'BEGIN{print '1.2449'**0.5}'
awk: line 1: syntax error at or near *
can someone help me troubleshoot the above command?
i'm trying to do the square root of 1.2449. this command works on Red Hat, but for some reasonn isn't working on kubuntu (latest version).
shell is bash.
i... (3 Replies)
Discussion started by: SkySmart
3 Replies
7. Shell Programming and Scripting
Hi.
I'm new to this forum, my English perhaps is not so good, but here is my question:
In bash you can use ] for tests, and how I understand it the variable names should be expanded automatically. So this should give "yes":
xx=hello
$ ] && echo yes || echo no
no # not giving "yes"
These two... (2 Replies)
Discussion started by: 244an
2 Replies
8. Shell Programming and Scripting
Hi
I want export input data ...
echo "month: "
read m
export m=$m
also export m is not working ?
the month-variable should be exportet for the use in other scripts,
but it is not working like this. What i'm doing wrong?
Thanks in advance!
IMPe (10 Replies)
Discussion started by: IMPe
10 Replies
9. Shell Programming and Scripting
My git user has permission in sudoers to run a wrapper script to move files into my webroot.
Everything is working fine except for the chown line. After the script has run, the files ar still root:root instead of apache:apache.
Scratching my head...:confused:
#!/bin/sh
echo
echo "****... (4 Replies)
Discussion started by: dheian
4 Replies
10. HP-UX
Hi All,
I've tried starting syslogd on our hp-ux 11.31 server. However, it is not getting started nor it is updating the syslog file.
There is no space issue also. However, the mail.log file is approx 2GB, can that be of any issue. Please find the details below:
# /sbin/init.d/syslogd... (2 Replies)
Discussion started by: Kits
2 Replies
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.
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), smf(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.
DIAGNOSTICS
A history of all actions taken by cron is stored in /var/cron/log and possibly in /var/cron/olog.
SunOS 5.10 5 Aug 2004 cron(1M)