On Wed, May 20, 2009 9:25 am, Mike Frysinger wrote: > On Tuesday 19 May 2009 18:39:47 Neil Brown wrote: >> sm-notify : >> - is a 'client' for the "SM" protocol. >> - must be run at boot time, and after that is not needed. >> >> statd : >> - is a 'server' for the "SM" protocol. >> - only needs to be running when either nfsd is running or an >> nfs mount which supports locks is active > > that last part -- any nfs mount with locks -- means that pretty much every > nfs > client out there needs it running. > > sm-notify is pretty minuscule, so the overhead of having that run on a > server > is negligible, especially when combined with the already required statd. > -mike > The point is that sm-notify should really be run at boot whenever it is installed. statd, being a server that listens to request from the network, should only be run if it is needed (because most people like the policy of only running network services that are actually needed). If all nfs mounts are performed manually, then you might not want to run statd for quite a long time after boot. But you need to run sm-notify immediately after boot to ensure that any locks you held before the reboot get released. They really are separate functions. NeilBrown -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
