12-24-2010
Sometimes stuff is hard to do because everyone else discovered you should not do it that way!
I am just trying to get a handle on what you are monitoring with your sql rows. The monitoring of clients is better done on the server, as clients can have problems saying "I am broke, gone" because they are broke or gone. Servers can tell if connections are broken, but web apps do not need continuous connection. Even tcp connections are not that good an indication, with all the keep-alive faking on the networks to reduce congestion. An application level keep-alive heartbeat is sometimes necessary for real monitoring.
The purpose of monitoring may be status (is everyone on?) or history (has everyone been on 8 hours 5 days this week?, How many are on, on average>).
This is a bit like removing the appendix through the left nostril -- limited perception or available action!
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Working on AIX 4.3
I have an active exe that accepts files for processing on our RS6000. Day to day i store these files in a secure place and at the end of the day I mv them one by one. After some reading and ofcourse trial and error i figured out that this helps...
mv `ls -l |head -l | awk... (2 Replies)
Discussion started by: buRst
2 Replies
2. Programming
Hi,
I have a doubt in introducing a delay in the programs.
We know that we do have a sleep() function/api using which
we can bring a delay in terms of seconds.
A minimum delay can be atleast 1 second.
Now I'm bothered about how to introduce a delay that is just
less than a second. Like... (3 Replies)
Discussion started by: S.Vishwanath
3 Replies
3. Solaris
Hi Experts,
I am running solris 9. Sun-Fire 880.
How do i shutdowon the whole server using ALOM i.e sc> console.
If the server is down or somehow hang How do i Restart from sc>
//purple (6 Replies)
Discussion started by: thepurple
6 Replies
4. UNIX for Dummies Questions & Answers
I have Oracle 9i R2 on AIX 5.2. My Database is running in shared server mode (MTS).
Sometimes when I shutdown the database it shutsdown cleanly in 4-5 mints and sometimes it takes good 15-20 minutes and then I get some ora-600 errors and only way to shutdown is by opening another session and... (7 Replies)
Discussion started by: aixhp
7 Replies
5. Emergency UNIX and Linux Support
I've got critical patching this weekend on 6 HP UX machines, back to back and the customer has requested to shutdown, and halt the machines and to bring it up at a later period. The thing is the servers are located offshore and we are just the support team. I have a special login thru a console... (16 Replies)
Discussion started by: hedkandi
16 Replies
6. Shell Programming and Scripting
Hi
I'm looking for scripts to backup & restore Gnome Desktop and all settings in Gnome. (0 Replies)
Discussion started by: ccc
0 Replies
7. UNIX for Dummies Questions & Answers
I have a list of URLs that I need to download in a file.
I know I can use the -i option to load the URLs from the file, but how can I make Wget wait a couple secs between each URL download? (4 Replies)
Discussion started by: rlopes
4 Replies
8. Shell Programming and Scripting
Hi,
I am trying to understand what would happen if ther is a loop without any delay like sleep statement, I feel that would add a lot of load onto the CPU. Trying to understand how the load is reduced by the introduction of sleep().
Thanks and regards
Zulfi (3 Replies)
Discussion started by: zulfi123786
3 Replies
LEARN ABOUT OPENDARWIN
rpc.statd
RPC.STATD(8) BSD System Manager's Manual RPC.STATD(8)
NAME
rpc.statd -- host status monitoring daemon
SYNOPSIS
rpc.statd [-d]
DESCRIPTION
The rpc.statd utility is a daemon which co-operates with rpc.statd daemons on other hosts to provide a status monitoring service. The daemon
accepts requests from programs running on the local host (typically, rpc.lockd(8), the NFS file locking daemon) to monitor the status of
specified hosts. If a monitored host crashes and restarts, the remote daemon will notify the local daemon, which in turn will notify the
local program(s) which requested the monitoring service. Conversely, if this host crashes and re-starts, when the rpc.statd re-starts, it
will notify all of the hosts which were being monitored at the time of the crash.
The following option is available:
-d Cause debugging information to be written to syslog, recording all RPC transactions to the daemon. These messages are logged with
level LOG_DEBUG and facility LOG_DAEMON. Error conditions are logged irrespective of this option, using level LOG_ERR.
-n Just send SM_NOTIFY messages to notify any hosts of a restart. Do not start daemon.
The rpc.statd utility must NOT be invoked by inetd(8) because the protocol assumes that the daemon will run from system start time. Instead,
it should be run from rc(8) after the network has been started.
FILES
/var/db/statd.status non-volatile record of currently monitored hosts.
/usr/include/rpcsvc/sm_inter.x RPC protocol specification used by local applications to register monitoring requests.
SEE ALSO
syslog(3), rc(8), rpc.lockd(8)
BUGS
There is no means for the daemon to tell when a monitored host has disappeared permanently (eg. catastrophic hardware failure), as opposed to
transient failure of the host or an intermediate router. At present, it will re-try notification attempts at frequent intervals for 10 min-
utes, then hourly, and finally gives up after 24 hours.
The protocol requires that symmetric monitor requests are made to both the local and remote daemon in order to establish a monitored rela-
tionship. This is convenient for the NFS locking protocol, but probably reduces the usefulness of the monitoring system for other applica-
tions.
The current implementation uses more than 1Kbyte per monitored host in the status file (and also in VM). This may be inefficient for NFS
servers with large numbers of clients.
STANDARDS
The implementation is based on the specification in X/Open CAE Specification C218, "Protocols for X/Open PC Interworking: XNFS, Issue 4",
ISBN 1 872630 66 9
BSD
September 19, 1995 BSD