12-10-2010
8 More Discussions You Might Find Interesting
1. High Performance Computing
Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris.
More... (0 Replies)
Discussion started by: Linux Bot
0 Replies
2. High Performance Computing
Dear All,
Can anyone explain about Pros and Cons of SUN and Veritas Cluster ?
Any comparison chart is highly appreciated.
Regards,
RAA (4 Replies)
Discussion started by: RAA
4 Replies
3. Solaris
Yesterday my customer told me to expect a vcs upgrade to happen in the future. He also plans to stop using HDS and move to EMC.
Am thinking how to migrate to sun cluster setup instead.
My plan as follows leave the existing vcs intact as a fallback plan.
Then install and build suncluster on... (5 Replies)
Discussion started by: sparcguy
5 Replies
4. UNIX for Advanced & Expert Users
I currently have in root's crontab:
20 4 * * 0,3 /usr/cluster/lib/sc/newcleventlog /var/cluster/logs/eventlog
20 4 * * 0,3 /usr/cluster/lib/sc/newcleventlog /var/cluster/logs/DS
20 4 * * 0,3 /usr/cluster/lib/sc/newcleventlog /var/cluster/logs/commandlog
there is no man page on... (1 Reply)
Discussion started by: rkruck
1 Replies
5. Solaris
Hi experts,
I would have a question on boot archive files on solaris10 platform running on T5220 cluster servers.
When we check the /platform/sun4v directory , and perform boot archive-list , we see that on both units same files exist. And when we mount the boot archive we see that all files... (0 Replies)
Discussion started by: dyavuzy1
0 Replies
6. Solaris
Hello experts -
I am planning to install a Sun cluster 4.0 zone cluster fail-over. few basic doubts.
(1) Where should i install the cluster s/w binaries ?. ( global zone or the container zone where i am planning to install the zone fail-over)
(2) Or should i perform the installation on... (0 Replies)
Discussion started by: NVA
0 Replies
7. Red Hat
Hi Everybody,
I would like to know meaning of following parameters in cluster.conf file in linux
<device name="blade_fence" blade="2" option="off"
<clusternode name="Blade1-int" votes="1" nodeid="1">
what do you mean by "option=off" and "votes=1"
Thanks (1 Reply)
Discussion started by: mastansaheb
1 Replies
8. AIX
Hello,
I am working on applications on an AIX 6.1 two-node cluster, with an active and passive node. Is there a command that will show me which mount points / file systems are shared and 'swing' from one node to the other when the active node changes, and which mount points are truly local to... (6 Replies)
Discussion started by: Clovis_Sangrail
6 Replies
LEARN ABOUT DEBIAN
cmannotifyd
cmannotifyd(8) CMAN Notification Daemon cmannotifyd(8)
NAME
cmannotifyd - CMAN Notification Daemon
SYNOPSIS
cmannotifyd [-f] [-d]
DESCRIPTION
The cmannotifyd daemon talks to CMAN and provides a mechanism to notify external entities about cluster changes.
CMAN dispatches 3 kind of notifications:
- CMAN_REASON_TRY_SHUTDOWN when cman requests to all clients if it is allowed to shutdown.
- CMAN_REASON_STATECHANGE when cman detects a node joining or leaving the cluster.
- CMAN_REASON_CONFIG_UPDATE when a configuration change event has been detected/requested.
These notifications are then dispatched to the shell script cman_notify in the environment variable CMAN_NOTIFICATION.
cman_notify will then execute all the scripts in the configured notification directory (default: /etc/cluster/cman-notify.d) passing a very
minimal set of envvars including, of course, the CMAN_NOTIFICATION= type. The execution order is set by the filename as shown by "LC_ALL=C
ls -las".
cmannotifyd logs are stored in the default log file (/var/log/cluster/cmannotifyd.log).
cman_notify logs are stored in the default log file (/var/log/cluster/cman_notify.log). By default the output from the scripts executed by
cman_notify is redirected to /dev/null. Users can either set CMAN_NOTIFICATION_DEBUG=1 in their environment or set proper debug configura-
tion in cluster.conf to redirect scripts output to the cman_notify log file.
NOTES
cmannotifyd does not block on cman_notify nor check the exit status of the script.
Notifications are dispatched in the same order as they arrive, one by one.
CMAN_REASON_TRY_SHUTDOWN is passed to scripts for information only, they can not influence cman's decsion about whether or not to shut
down.
CMAN_REASON_STATECHANGE also implies CMAN_NOTIFICATION_QUORUM exported in the environment. CMAN_NOTIFICATION_QUORUM will be set to 1 (when
the node is part of a quorate cluster) or 0 (otherwise).
A template for cman_notify scripts can be found in the doc/ directory.
OPTIONS
-f Run in the foreground (do not fork / daemonize).
-d Enable debug output.
November 2008 cmannotifyd(8)