Ah I see! I have an additional comment/question though.
I've noticed that when I unmount a gluster volume on a client the
[glusterfs] process is still running. Perhaps it thinks my cleint spec
is a server.
I have no instance of "type protocol/server" in the client spec. What
does it use to determine weather it's a client or a server?
-Mickey Mazarick
Anand Avati wrote:
Mickey,
in the latest codebase, there are no more server and client programs.
there is just one glusterfs (and glusterfsd is a symlink to
glusterfs). it behaves either as a client or server according to the
volume spec file given.
if the glusterfs program is passed a mountpoint it attaches a fuse
translator in a hardcoded way, so this preserves backward
compatibility. The new model also allows both protocol/server and
mount/fuse (mountability) in the same spec file which can be a
performance improvement in NUFA mode of operations.
avati
2008/2/29, Mickey Mazarick <mic@xxxxxxxxxxxxxxxxxx
<mailto:mic@xxxxxxxxxxxxxxxxxx>>:
This is very minor but it did break a kill script I wrote.
When I run the latest build, the server daemon shows up as:
[glusterfs]
in the process list.
Just an FYI :-)
Thanks!
-Mickey Mazarick
--
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx <mailto:Gluster-devel@xxxxxxxxxx>
http://lists.nongnu.org/mailman/listinfo/gluster-devel
--
If I traveled to the end of the rainbow
As Dame Fortune did intend,
Murphy would be there to tell me
The pot's at the other end.
--
