06-29-2001
Make a mistake on reply
Sorry, I simply create a new thread on another place.
I am sure the cron job was being executed. The only thing is, the mail cannot be send, or in another way, the receiver cannot receive the email.
What can I do? Any ideas?
Thanks.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am getting a "connection to the server has failed" error when trying send out internal email. this will be like this for maybe four hours then it will start working for no reason. then it will stop again. the only constant i have is if i reboot the server the send mail will work for about an... (1 Reply)
Discussion started by: jrblanton
1 Replies
2. Solaris
Dear All,
Now I use solaris 10 and I try to forward mail from /var/mail/username to their external mail so what should I do?
thank u in advance (2 Replies)
Discussion started by: unitipon
2 Replies
3. Shell Programming and Scripting
I've a lot of file with an hyphen on filename, so I use rename for remove him ad substitute with an underscore but it fails
$ rename 's/\-/\_/' *
Unknown option: _
Unknown option: i
Unknown option: r
Unknown option: e
Unknown option: e
Unknown option: _
Unknown option: g
Unknown... (12 Replies)
Discussion started by: cv313x
12 Replies
4. Shell Programming and Scripting
Hi
Am having 2 files.
I have one data file.
before inserting in to the table am taking cout of the data file and store as data 1.
After insert in to the table and am taking the count from the table and store as data2.
If i try to compare those values
If
then
echo "data match"... (5 Replies)
Discussion started by: bobprabhu
5 Replies
5. UNIX for Advanced & Expert Users
i have sun machines having solaris 9 & 10 OS . Now i need to send mail from the machines to my outlook account . I have the ip adress of OUTLOOK mail server. Now what are the setting i need to do in solaris machines so that i can use mailx or sendmail.
actually i am trying to automate the high... (2 Replies)
Discussion started by: amitranjansahu
2 Replies
6. AIX
This is a LPAR that i created earlier.
I want to set an IP address to en0 but it failed.
Command: failed stdout: yes stderr: no
Before command completion, additional instructions may appear below.
en0
devdbm01
inet0 changed
Method error (/usr/lib/methods/chgif):
... (8 Replies)
Discussion started by: wingcross
8 Replies
7. Shell Programming and Scripting
Hello,
I am stuck... i dunno why does my test fail... any idea ?
#!/bin/bash
dos2unix info.txt
Distor=Distributeur
LINE=$(cat info.txt | sed -n 1p)
echo $LINE
echo $Distor
echo ""
echo "123-$LINE-123"
echo "123-$Distor-123"
if ; then
LINE2=$(cat info.txt | sed -n 2p)
echo $Distor... (14 Replies)
Discussion started by: patx
14 Replies
8. Shell Programming and Scripting
Hi Team,
I have a file named as follows: aaa.tar.gz
Now I need to verify if the untar fails, then the script has to send a mail. In order to check this condition, I need a tar.gz file which is unable to untar it. Can anyone help me to create a file which I will be able to unzip successfully... (2 Replies)
Discussion started by: kmanivan82
2 Replies
9. Forum Support Area for Unregistered Users & Account Problems
After inputted all required fields in registration page, the below message is shown and cannot go on.
A required field called Custom Date & Time Formats is missing or has an invalid value. (2 Replies)
Discussion started by: Unregistered
2 Replies
10. UNIX for Advanced & Expert Users
I am having trouble getting mail to work on a red hat server. At first I was getting this message.
Diagnostic-Code: X-Postfix; delivery temporarily suspended: connect to :25: Connection refused
Then added the port to my firewall. Then I temporarily turned off selinux. I then copied this file... (1 Reply)
Discussion started by: cokedude
1 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)