07-08-2010
how to monitor deamon processes
we have several deamon processes which were killed for some unknown reasons. we have to bring the deamon back manually everytime. Deamons running on 2 identical instances. It is ok on one instance but be killed 3 or 4 times a day on another. Any idea how to monitor it? like who/how the processes be killed? AIX 5.3, Oracle 10g.
Thanks
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
hi
how to write deamon program
i specified in detail i want to write c++ program when it run it run like deamon process (1 Reply)
Discussion started by: munnu
1 Replies
2. Red Hat
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)
Discussion started by: quan0509
2 Replies
3. Shell Programming and Scripting
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)
Discussion started by: Solerous
3 Replies
4. Linux
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)
Discussion started by: ultramen7
2 Replies
5. Infrastructure Monitoring
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)
Discussion started by: SkySmart
3 Replies
6. Ubuntu
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)
Discussion started by: paragnehete
2 Replies
7. Shell Programming and Scripting
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)
Discussion started by: baders
0 Replies
8. Linux
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)
Discussion started by: DjDeaf
1 Replies
9. Debian
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)
Discussion started by: Zabo
2 Replies
10. Infrastructure Monitoring
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 PHP
systemd.kill
SYSTEMD.KILL(5) systemd.kill SYSTEMD.KILL(5)
NAME
systemd.kill - Process killing procedure configuration
SYNOPSIS
service.service, socket.socket, mount.mount, swap.swap, scope.scope
DESCRIPTION
Unit configuration files for services, sockets, mount points, swap devices and scopes share a subset of configuration options which define
the killing procedure of processes belonging to the unit.
This man page lists the configuration options shared by these five unit types. See systemd.unit(5) for the common options shared by all
unit configuration files, and systemd.service(5), systemd.socket(5), systemd.swap(5), systemd.mount(5) and systemd.scope(5) for more
information on the configuration file options specific to each unit type.
The kill procedure configuration options are configured in the [Service], [Socket], [Mount] or [Swap] section, depending on the unit type.
OPTIONS
KillMode=
Specifies how processes of this unit shall be killed. One of control-group, process, mixed, none.
If set to control-group, all remaining processes in the control group of this unit will be killed on unit stop (for services: after the
stop command is executed, as configured with ExecStop=). If set to process, only the main process itself is killed. If set to mixed,
the SIGTERM signal (see below) is sent to the main process while the subsequent SIGKILL signal (see below) is sent to all remaining
processes of the unit's control group. If set to none, no process is killed. In this case, only the stop command will be executed on
unit stop, but no process be killed otherwise. Processes remaining alive after stop are left in their control group and the control
group continues to exist after stop unless it is empty.
Processes will first be terminated via SIGTERM (unless the signal to send is changed via KillSignal=). Optionally, this is immediately
followed by a SIGHUP (if enabled with SendSIGHUP=). If then, after a delay (configured via the TimeoutStopSec= option), processes still
remain, the termination request is repeated with the SIGKILL signal (unless this is disabled via the SendSIGKILL= option). See kill(2)
for more information.
Defaults to control-group.
KillSignal=
Specifies which signal to use when killing a service. This controls the signal that is sent as first step of shutting down a unit (see
above), and is usually followed by SIGKILL (see above and below). For a list of valid signals, see signal(7). Defaults to SIGTERM.
Note that, right after sending the signal specified in this setting, systemd will always send SIGCONT, to ensure that even suspended
tasks can be terminated cleanly.
SendSIGHUP=
Specifies whether to send SIGHUP to remaining processes immediately after sending the signal configured with KillSignal=. This is
useful to indicate to shells and shell-like programs that their connection has been severed. Takes a boolean value. Defaults to "no".
SendSIGKILL=
Specifies whether to send SIGKILL to remaining processes after a timeout, if the normal shutdown procedure left processes of the
service around. Takes a boolean value. Defaults to "yes".
SEE ALSO
systemd(1), systemctl(1), journalctl(8), systemd.unit(5), systemd.service(5), systemd.socket(5), systemd.swap(5), systemd.mount(5),
systemd.exec(5), systemd.directives(7), kill(2), signal(7)
systemd 237 SYSTEMD.KILL(5)