chaostic

Group: Members
Posts: 328
Joined: Mar. 2005 |
 |
Posted: May 29 2008,19:32 |
 |
Quote (Jason W @ May 29 2008,11:54) | In the System>Daemons menu, starting nfs-common starts /etc/init.d/nfs-common without starting any other services. I have always found that portmap needs to be running for nfs-common to work. If that is correct, it would be nice if starting nfs-common from the menu would check if portmap is running and start it if needed. Thanks |
Yea, nfs-common starts rpc.statd, but that fails if there's no portmap enabled, and any start-stop-daemon messages are disabled because of "--quiet". RPC.statd should still error to syslog (if you have it enabled)
Thing is, I'm on 3.4.11, and it seems to be the same thing. Has noone used the nfs-common at all? Has noone needed to use a nfs server since who know's when?
That's funny
|