I would start by:
What has this job so special compared to the others? For if all others make it there must be something that makes the difference...
try redirect STDOUT to something like $HOME/cronjobID_mailer.log and and 2 >jobID_mailer.err rather than
And see what output you get...
I'm trying to sell the use of gzip instead of compress in our department. One issue I'm having (which is a showstopper) is that I lose the ownership when gzipping and gunzipping, though it's mentioned all over the web that files are supposed to keep ownership.
Example:
-rwxrwxrwx 1 ms32345 ... (3 Replies)
Hi guys
yesterday we made an aplication update runing over solaris10, when finish we have next message every 5 minutes :eek:
sendmail: m4TKt04M014942: Losing ./qfm4TKt04M014942: savemail panic:confused:
Do you now what does it mean? what can I do in order to fix it?
Thanks in... (0 Replies)
I'm using a while read statement to read in lines from a file, if a value (for example) is 1000.10 in a field, the last zero is removed leaving 1000.1 does anyone know a way to keep the field as it is in the original file? (1 Reply)
So here's the scoop. I am working on a project to automate the building of spark based solaris servers. I've got a cursory amount of knowledge of how to use the os after some pretty heavy experience with Linux, and doing a similar project there.
I have a few questions though...
1) how is... (5 Replies)
Hey guys, facing a weird issue - hoping someone might be able to help.
The wireless network on my laptop is configured with a static IP address. (not using nm)
When i take the laptop out of the range (or i power the router down) the essid is becoming "off/any".
When i'm back in range the... (6 Replies)
I'm newbie in UNIX programming, I have a problem with signals. I'm writing multithread program, where threads can die at any moment. When thread dies it generates signal SIGUSR1 to main thread and then thread dies. Main thread gets a signal and waits for thread dead.
I wrote program like this:
... (5 Replies)
Discussion started by: DendyGamer
5 Replies
8. Forum Support Area for Unregistered Users & Account Problems
Hi.
Recently when I'm logged in to site after some seconds, for instance, I lose the connection and need sign in again. It happens on Firefox and Chrome.
Or another example, when I'm logged in to site and click on my nick name (right up corner) I lose the connection to site.
User: tiago
... (0 Replies)
Our Unix system is losing a considerable amount of time each day, and our support service company says our motherboard is the cause. They "upgraded" us 5 years ago to basically the same thing as what we had previously, and are looking to "upgrade" us again now for about $5,000... I think... (23 Replies)
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
LEARN ABOUT XFREE86
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.
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)