If you are starting your daemons from the /etc/inittab, you can set them up like the cron daemon to automatically respawn it if it is killed or dies. You can see here I kill my cron daemon and the system automatically restarts it because of the "respawn" in the /etc/inittab.
There is no logging doing it this way, but it will keep your processes running even if they are killed.
---------- Post updated at 03:46 PM ---------- Previous update was at 03:45 PM ----------
As to who is killing them... it has to be either root or the owner of the processes. I don't think you can kill some one else's running processes.
Hi everyone.
Now, i want to permit for an user to start, stop and reconfig some of daemon on Redhat system without root permission.
So how can i do ?
Tks all. (2 Replies)
I have two processes that I need to keep running. The first process is a server, the second is basically a canvas for creating images which get saved to a directory. So I plan on using launchd (Mac OS 10.5) on a server to check every minute or so to make sure two things are true:
1) Both apps... (3 Replies)
I have install centos on my server,.. then after rebooting 2 ,3 times , hal deamon cannot start, and system hang on boot.. when i google, i found the solution which is off the hal daemon service... my question is, what is the effect if i off the deamon service ?:confused:
tq (2 Replies)
snmpget -v 1 -c COMMUNITYSTR hostname OID
what OIDs would I use to get information on all the processes and disk space information that are on a particular host.
where can i find out information on all of this?
thanks (3 Replies)
Hi Team,
I have over 100 users,working on LINUX machine & all they use firefox. I want to monitor traffic from every IP and mainly CPU USAGE TAKEN BY FIREFOX PROCESSES ON EACH MACHINE. Is there any tool which runs on lunux and will help me to monitor firefox processes of our entire LAN?
... (2 Replies)
GM,
Can you pls help how to write a script to monitor different processes on different unix servers and send the output to a /tmp/report file, earlier my boss asked me to write a script to monitor just one process running on different servers and send the output to a file so I wrote this
exec... (0 Replies)
Hi Guys,
Monitoring 'Total Processes' on Linux servers has been always something you 'should' do.
My question is - why? Is it relevant anymore?
If you monitor memory and cpu params, you have a pretty good idea about what's going on.
Is the number of processes really matter?
Thanks (1 Reply)
Hi ,
i have enclosed a picture of gkrellm configuration.
MX16 Debian Jessie Linux.
For showing the temperature the software needs a hddtemp daemon running on port 7634 !
How to make that daemon ?
A cool task. I dont know anything about that.
Perhaps the commandline tool hddtemp is... (2 Replies)
Sorry if this is the wrong forum
Searching for Saas Monitor service which monitor my servers which are sitting in different providers .
This monitor tool will take as less CPU as possible , and will send info about the server to main Dashboard.
The info I need is CPU / RAM / my servers status (... (1 Reply)
Discussion started by: umen
1 Replies
LEARN ABOUT OPENDARWIN
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)