Randall R Schulz wrote:
On Wednesday May 13 2009, Per Jessen wrote:
Randall R Schulz wrote:
The nfs (client) daemon / service is already running by the time I can log in. It's enabled in run levels 3 and 5. I did mention that.
Yep - and you've probably/perhaps also verified that the scripts are in fact run during a boot-up? If not, check /var/log/boot.msg
I did. Here are all the lines mentioning NFS in boot.msg:
-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==- Starting kernel based NFS server: idmapd mountd statd nfsd sm-notifydone Starting NFS client services: sm-notify idmapdmount: rpc_pipefs already mounted or /var/lib/nfs/rpc_pipefs busy mount: according to mtab, rpc_pipefs is already mounted on /var/lib/nfs/rpc_pipefs -==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==-
I'm not certain, but could this be a conflict between an nfs server and an nfs client? It looks like you're starting an nfs server first, and then the nfs client complains about something being already mounted - I'm wondering if that causes the nfs client script to stop at that point (sm_notify). If you don't need the nfsserver, perhaps it's worth disabling it and see what happens on the next boot? /Per -- Per Jessen, Zürich (18.3°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org