Bug 751339 - rpc.idmapd doesn't autoconfigure domain on startup
Summary: rpc.idmapd doesn't autoconfigure domain on startup
Keywords:
Status: CLOSED DUPLICATE of bug 748275
Alias: None
Product: Fedora
Classification: Fedora
Component: nfs-utils
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-04 12:15 UTC by Jeff Layton
Modified: 2011-11-14 17:30 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-14 17:30:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jeff Layton 2011-11-04 12:15:58 UTC
I recently switched my main workstation at home to f16. Since then, rpc.idmapd does not properly pick set the idmapping domain at boot time. If I go in after
booting and do a "service nfs-idmap restart" then it will work properly. It
also works properly if I set the domain explicitly in /etc/idmap.conf.

I suspect the problem is a boot-time ordering issue. rpc.idmapd is likely being started before the hostname is properly set on the machine. I'm not sure exactly how to fix this -- we may need some systemd expertise.

In any case -- perhaps it's time to move to the new idmapper anyway?

Comment 1 Steve Dickson 2011-11-14 17:30:36 UTC

*** This bug has been marked as a duplicate of bug 748275 ***


Note You need to log in before you can comment on or make changes to this bug.