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 REDHAT
crond
CRON(8) System Manager's Manual CRON(8)NAME
cron - daemon to execute scheduled commands (Vixie Cron)
SYNOPSIS
cron
DESCRIPTION
Cron should be started from /etc/rc or /etc/rc.local. It will return immediately, so you don't need to start it with '&'.
Cron searches /var/spool/cron for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into memory. Cron
also searches for /etc/crontab and the files in the /etc/cron.d/ directory, which are in a different format (see crontab(5)). Cron then
wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute. When execut-
ing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab, if
such exists).
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab) has changed, and if it has,
cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted whenever a crontab
file is modified. Note that the Crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
SEE ALSO crontab(1), crontab(5)AUTHOR
Paul Vixie <paul@vix.com>
4th Berkeley Distribution 20 December 1993 CRON(8)