Comment 6 for bug 925364
Revision history for this message
| David Ambrose-Griffith (d-e-ambrose-griffith) wrote | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Once rpc_pipefs is manually mounted, then yes, rpc.gssd -fvvv works as expected and I've managed to get an NFSv4 with Kerberos mount against our NetApp filer.
On boot however I'm getting...
Starting NFSv4 id <-> name mapper [ OK ]
repeatedly, with things like Automounter starting in and around it
Finally...
Starting NFSv4 id <-> name mapper [ Fail ]
*Then* it appears to start the network, and waits an additional 60 seconds for the network (the machine in question is just connected to eth0 and gets its address from an Infoblox DHCP appliance)
Once booted /run/rpc_pipefs isn't mounted (but can be mounted manually) and idmapd (and gssd) are both not running.
Networking is up once booted, I don't know exactly what order things are coming up however.
rpc.idmapd -fvvv also requires the "-p /run/rpc_pipefs" argument which I can't spot in the /etc/init/
I'll try and reproduce these issues on a clean re-install of this machine next.
Best regards,
David