02-04-2010
yes, its periodic monitoring like hourly
9 More Discussions You Might Find Interesting
1. Solaris
Hello !
Can anybody help me with the following:
my sparc server ( solaris 10 06/07) has 1 global and 4 non-global zones running
we are using one of the non-global-zones for a jboss application server
we want to levitate the JBOSS process within the non_global_zone with: < priocntl -s -c FX -p... (1 Reply)
Discussion started by: moofoo
1 Replies
2. Solaris
Log File: /var/tmp/server1.install.18730.log
Source: /vmpool/tmp/server1.flar
Installing: This may take several minutes...
Postprocessing: This may take several minutes...
Postprocess: ERROR: p2v module S40_setup_preload failed: 0
Postprocess: ERROR: Postprocessing failed.
... (0 Replies)
Discussion started by: cornsnap
0 Replies
3. Solaris
Is solaris 6 container support available ? Say, If I have a machine with Solaris 10 operating system.. Can i install Solaris 6 container on this machine, so that the machine will have Solaris 6 virtual environment...
Does sun support Solaris 6 container ?
Any ideas over this ? (1 Reply)
Discussion started by: shafi2all
1 Replies
4. Solaris
Hi,
I've got a UPS connected to my Solaris 10 machine and I'm planning to run containers/zones on there.
At the moment if the UPS agent sends the signal to the solaris machine to shutdown, all the apps shutdown gracefully and then the host goes down.
If I setup containers for the apps, does... (9 Replies)
Discussion started by: fastexit
9 Replies
5. Solaris
Hi All,
We have a server with Solaris 10 installed. The total memory of the server is 64GB. In order to check the memory info of the server I use "top" utility that gives me total and free memory in real-time.
I have also installed a Sun container (non-global zone) on top of parent operating... (4 Replies)
Discussion started by: Slayer
4 Replies
6. Solaris
Hi people,
I dont have a real problem, its also a so strange issue.
When i connect to my system from a ssh session or telnet normaly from putty and execute the command "date" its show me the correctly time in BRT format for root and all other users.
But when i connect from the global... (3 Replies)
Discussion started by: anonymouzz
3 Replies
7. Solaris
kindly share what are difference b/w solaris zones and containers.... (8 Replies)
Discussion started by: Rajesh_Apple
8 Replies
8. Solaris
Hi everyone!
I am in dire need to know what are the differences between a solaris zone and a solaris container.. Explanations over the net are very confusing. Please help. Thanks! (8 Replies)
Discussion started by: arah
8 Replies
9. Solaris
Hello,
This is Solaris-10 server, running with 4 non-global zones.
This server was hung today and I had to reboot it forcefully from console. Then root file-system was not clean and I had to run fsck from failsafe mode. After it came back in run-level-3, lot of services are showing in... (3 Replies)
Discussion started by: solaris_1977
3 Replies
LEARN ABOUT FREEBSD
rpc.statd
RPC.STATD(8) BSD System Manager's Manual RPC.STATD(8)
NAME
rpc.statd -- host status monitoring daemon
SYNOPSIS
rpc.statd [-d] [-h bindip] [-p port]
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.
-h bindip
Specify specific IP addresses to bind to. This option may be specified multiple times. If no -h option is specified, rpc.statd will
bind to INADDR_ANY. Note that when specifying IP addresses with -h, rpc.statd will automatically add 127.0.0.1 and if IPv6 is
enabled, ::1 to the list.
-p The -p option allow to force the daemon to bind to the specified port, for both AF_INET and AF_INET6 address families.
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)
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
BUGS
There is no means for the daemon to tell when a monitored host has disappeared permanently (e.g. 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
minutes, 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.
BSD
November 1, 2007 BSD