This is the mail archive of the
cluster-cvs@sources.redhat.com
mailing list for the cluster.
cluster/gnbd server/device.h server/extern_req ...
- From: bmarzins at sourceware dot org
- To: cluster-cvs at sources dot redhat dot com
- Date: 17 Mar 2005 16:16:33 -0000
- Subject: cluster/gnbd server/device.h server/extern_req ...
CVSROOT: /cvs/cluster
Module name: cluster
Branch: RHEL4
Changes by: bmarzins@sourceware.org 2005-03-17 16:16:29
Modified files:
gnbd/server : device.h extern_req.c local_req.h
gnbd/tools/gnbd_import: gnbd_import.c
Log message:
Now, when a server is started with the -n option, you cannot use fence_gnbd
with it. This is because when the server is started with -n, you have no
idea if you are actually banning the correct client. The node will be
fenced by it's cluster nodename, but gnbd uses uname -n to identify connections.
If these don't match, you get false successes. So the solution is to simply
disallow fencing when you specify -n.
Patches:
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/server/device.h.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.2&r2=1.2.2.1
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/server/extern_req.c.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.3&r2=1.3.2.1
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/server/local_req.h.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.3.2.1&r2=1.3.2.2
http://sources.redhat.com/cgi-bin/cvsweb.cgi/cluster/gnbd/tools/gnbd_import/gnbd_import.c.diff?cvsroot=cluster&only_with_tag=RHEL4&r1=1.11.2.1&r2=1.11.2.2