summaryrefslogtreecommitdiff
path: root/filesystems
diff options
context:
space:
mode:
authormanu <manu>2011-06-07 07:27:11 +0000
committermanu <manu>2011-06-07 07:27:11 +0000
commitb14226273b73ae004a132e8ab1b933a819ddbcb3 (patch)
tree8dceea505e075fb6d266680111732d5f1a97b799 /filesystems
parent96389fcc9b2c9d6ff12bf2accb44c710a4f72367 (diff)
downloadpkgsrc-b14226273b73ae004a132e8ab1b933a819ddbcb3.tar.gz
Fix typos in patch description. I must have been talking with soemone
else while typing it in the dirst place.
Diffstat (limited to 'filesystems')
-rw-r--r--filesystems/glusterfs/distinfo4
-rw-r--r--filesystems/glusterfs/patches/patch-bq10
2 files changed, 7 insertions, 7 deletions
diff --git a/filesystems/glusterfs/distinfo b/filesystems/glusterfs/distinfo
index ddb93b8ed80..8440305e8ae 100644
--- a/filesystems/glusterfs/distinfo
+++ b/filesystems/glusterfs/distinfo
@@ -1,4 +1,4 @@
-$NetBSD: distinfo,v 1.4 2011/06/06 15:53:13 manu Exp $
+$NetBSD: distinfo,v 1.5 2011/06/07 07:27:11 manu Exp $
SHA1 (glusterfs-3.2.0.tar.gz) = a8095e04feedce81aa21634639f278b3810398b8
RMD160 (glusterfs-3.2.0.tar.gz) = a69f47efd396a413ffb350e1711345ff49557325
@@ -25,4 +25,4 @@ SHA1 (patch-bm) = 71156d3bd9dcc02b09db022ee20852f4b52e7306
SHA1 (patch-bn) = d806dc6319568279d79fcc7b14fddd76771aa210
SHA1 (patch-bo) = 3c564fc3854847d26e512ded60082715745a0b1c
SHA1 (patch-bp) = 28363fc5468ef0bc930fe2551a78bed818ec2585
-SHA1 (patch-bq) = 52723f6fbb5c5e262a31ed8f9340f988dec4fbd9
+SHA1 (patch-bq) = 55c71e2c143271fd10afa04b168f94b23acbb982
diff --git a/filesystems/glusterfs/patches/patch-bq b/filesystems/glusterfs/patches/patch-bq
index e2d953d9557..3773bbd965d 100644
--- a/filesystems/glusterfs/patches/patch-bq
+++ b/filesystems/glusterfs/patches/patch-bq
@@ -1,13 +1,13 @@
-$NetBSD: patch-bq,v 1.1 2011/06/06 15:53:14 manu Exp $
+$NetBSD: patch-bq,v 1.2 2011/06/07 07:27:11 manu Exp $
-Make sur glusterfsd uses the same address family as gluserd.
+Make sur glusterfsd uses the same address family as glusterd.
glusterfsd uses getaddrinfo and picks the first entry for its
-listening address. The first entru is of inet7 family on
+listening address. The first entry is of inet6 family on
NetBSD. Even if glusterd was started with option
transport.address-family inet, we ended with glusterfsd
-started with inet6, and the client could not connect to it
-if the letwork lack IPv6
+using inet6. Since the client assumes glusterd and glusterfsd
+use the same address family, it could not reach glusterfsd.
--- xlators/mgmt/glusterd/src/glusterd-utils.c.orig 2011-06-06 10:28:42.000000000 +0200
+++ xlators/mgmt/glusterd/src/glusterd-utils.c 2011-06-06 16:17:30.000000000 +0200