Sponsored Content
Operating Systems AIX how to monitor deamon processes Post 302435932 by hamiltonhall on Thursday 8th of July 2010 02:44:47 PM
Old 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

deamon process

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

Permissionfor some deamon

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

perl script to monitor 2 processes

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

Hal deamon..

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

Using SNMP to monitor remote processes and disk space

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

How to monitor firefox processes?

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

script to monitor different processes on different Unix servers

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

Linux Total Processes - Why monitor it?

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

Gkrellm Linux HD Monitor needs a hddtemp deamon ?

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

Searching for Saas Monitor service which monitor my servers which are sitting in different providers

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
ifplugd(8)                                                    System Manager's Manual                                                   ifplugd(8)

NAME
ifplugd - A link detection daemon for ethernet devices SYNOPSIS
ifplugd [options] DESCRIPTION
ifplugd is a daemon which will automatically configure your ethernet device when a cable is plugged in and automatically unconfigure it if the cable is pulled. This is useful on laptops with on-board network adapters, since it will only configure the interface when a cable is really connected. It uses your distribution's native ifup/ifdown programs, but can be configured to do anything you wish when the state of the interface changes. It may ignore short unplugged whiles (-d option) or plugged whiles (-u option). ifplugd may be used in "compatibility mode" by specifying -F on the command line. Than ifplugd will treat network drivers which do not sup- port link beat querying as always online. OPTIONS
-a | --no-auto Do not enable interface automatically (default: off) -n | --no-daemon Do not daemonize (for debugging) (default: off) -s | --no-syslog Do not use syslog, use stdout instead (for debugging) (default: off). -b | --no-beep Do not beep (off), overrides --no-beep-up and --no-beep-down. -U | --no-beep-up Do not beep on interface up (off) -D | --no-beep-down Do not beep on interface down (off) -f | --ignore-fail Ignore detection failure, retry instead. Failure is treated as "no link". (default: off) -F | --ignore-fail-positive Ignore detection failure, retry instead. Failure is treated as "link detected". (default: off) -i | --iface= IFACE Specify ethernet interface (default: eth0) -r | --run= EXEC Specify program to execute when link status changes (default: /etc/ifplugd/ifplugd.action) -I | --ignore-retval Don't exit on nonzero return value of program executed on link change. (default: off) -t | --poll-time= SECS Specify poll time in seconds (default: 1) -T | --poll-utime= USECS Specify poll time in microseconds, added to -t (default: 0) -u | --delay-up= SECS Specify delay for configuring interface (default: 0) -d | --delay-down= SECS Specify delay for deconfiguring interface (default: 5) -m | --api-mode= MODE Force a specific link beat detection ioctl() API. Possible values are auto, iff, wlan, ethtool, mii, and priv for automatic detec- tion, interface flag (IFF_RUNNING), wireless extension, SIOCETHTOOL, SIOCGMIIREG resp. SIOCPRIV. Only the first character of the argument is relevant, case insensitive. (default: auto) -p | --no-startup Don't call the script to bring up network on deamon start (default: off) -q | --no-shutdown Don't call the script for network shutdown on deamon quit (default: off) -w | --wait-on-fork When daemonizing, wait until the background process finished with the initial link beat detection. When this is enabled, the parent process will return the link status on exit. 2 means link beat detected, 3 stands for link beat not detected, everything else is an error. -W | --wait-on-kill When killing a running daemon (with -k) wait until the daemon died. -x | --extra-arg= ARG Specify an extra argument to be passed to the action script. -M | --monitor Don't fail when the network interface is not available, instead use NETLINK to monitor device avaibility. The is useful for PCMCIA devices and similar. -h | --help Show help -k | --kill Kill a running daemon (Specify -i to select the daemon instance to kill) -c | --check-running Check if a daemon is running for a given network interface. Sets the return value to 0 if a daemon is already running or to 255 if not. -v | --version Show version -S | --supend Suspend a running daemon. The daemon will no longer check the link status until it is resumed (-R) again. (Specify -i to select the daemon instance to suspend.) -R | --resume Resume a suspended daemon. (Specify -i to select the daemon instance to resume.) -z | --info Request that a running daemon shall write its status information to syslog. (Specify -i to select the daemon instance to send the request to.) FILES
/etc/default/ifplugd: this file is sourced by the init script /etc/init.d/ifplugd and contains the interface to be monitored and the options to be used. /etc/ifplugd/ifplugd.action: this is the script which will be called by the daemon whenever the state of the interface changes. It takes two areguments: the first is the interface name (eg. eth0), the second either "up" or "down". /var/run/ifplugd.<iface>.pid: the pid file for ifplugd. ENVIRONMENT
The action script will be called with two environment variables set: IFPLUGD_PREVIOUS The previous link status. Either "up", "down", "error" or "disabled". The former values should be obvious, the latter is set on daemon startup. IFPLUGD_CURRENT The current link status. See above for possible values. SIGNALS
SIGINT, SIGTERM ifplugd will quit, possibly running the shutdown script. This is issued by passing -k to ifplugd. SIGQUIT ifplugd will quit, the shutdown script is never run. SIGHUP ifplugd will write its status information to syslog. This is issued by -z. SIGUSR1 ifplugd will go to suspend mode. (-S) SIGUSR2 ifplugd will resume from suspend mode. (-R) AUTHOR
ifplugd was written by Lennart Poettering <mzvscyhtq (at) 0pointer (dot) de>. ifplugd is available at http://0pointer.de/lennart/projects/ifplugd/ SEE ALSO
ifplugd.conf(5), ifup(8), interfaces(5), ifconfig(8), ifplugstatus(8) COMMENTS
This man page was written using xmltoman(1) by Oliver Kurth. Manuals User ifplugd(8)
All times are GMT -4. The time now is 02:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy