I just ran into an odd issue with the init script in 3.0.5. It uses LSB's pidofproc to see if there's already a server running, however, pidofproc uses the full path to the binary to ensure it's looking at the right one, however, since gluster server and client use the same binary (glusterfs is a symlink to glusterfsd), if it's running a client but not a server, it will erroneously return the pid of the client, report that a server instance is already running (though fail to find a pid), and thus prevent the server from starting. Looking at the docs for pidofproc, it's supposed to fail to return a pid if it doesn't find a pid file, however it wasn't in this case. I solved it by stopping the client, then the server started ok, then I remounted the client and it all worked. Marcus
