Re: PATCH 19/20: fix remote driver read only socket

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The remote_internal.c file is checkign VIR_CONNECT_RO instead of VIR_DRV_OPEN_RO
when determining what socket to open. Since these have different values, the
readonly socket is never used for a read only connection.

 remote_internal.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 
diff -r d8efa4ffb380 src/remote_internal.c
--- a/src/remote_internal.c	Thu Jun 21 20:33:39 2007 -0400
+++ b/src/remote_internal.c	Thu Jun 21 20:34:15 2007 -0400
@@ -347,7 +347,7 @@ remoteOpen (virConnectPtr conn, const ch
 
     case trans_unix: {
         if (!sockname) {
-            if (flags & VIR_CONNECT_RO)
+            if (flags & VIR_DRV_OPEN_RO)
                 sockname = strdup (LIBVIRTD_UNIX_SOCKET_RO);
             else
                 sockname = strdup (LIBVIRTD_UNIX_SOCKET);

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]