Summary: | net-fs/nfs-utils-1.2.9 - exportfs: Failed to resolve p01.fir.local -//- /etc/init.d/nfs: line 48: 1754 Killed ${exportfs} -r | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Cedric Sodhi <manday> |
Component: | [OLD] Core system | Assignee: | Network Filesystems <net-fs> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | manday |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge --info output |
Description
Cedric Sodhi
2014-12-09 13:21:12 UTC
Please post your `emerge --info' output in a comment. Created attachment 391364 [details]
emerge --info output
After enabling logging RC Start, I have the following in the rc.log * Exporting NFS directories ... exportfs: Failed to resolve p01.fir.local /etc/init.d/nfs: line 48: 1754 Killed ${exportfs} -r [ !! ] (In reply to Cedric Sodhi from comment #3) exportfs timed out because your network wasn't fully up. the init script then killed it to prevent the system from hanging. you need to make sure the network is fully functional before launching nfs. Couldn't NFS keep "retrying" in the background? Network is in rc default as it would be on pretty much every normal box, but this surely isn't the normal behaviour one would like to have. So I propose that either something is wrong with the rc dependencies or the script should rather (and preferably) keep spinning in the background and try to resolve until the network is up. In any case, the current situation can hardly be called "working fine" for a pretty normal setup, in my opinion. |