I don't believe your line is incorrect. I'm using build 117 with nfs/server disabled and my auto_home line reads:

* localhost:/export/home/&

Admittedly this spews some noise into the messages file every so often, but it has worked since I first installed OpenSolaris b86 (or whatever the first release was).

I do recall having problems initially with the automounter when I specified usernames explicitly (I don't recall the details), so I fell back to the wildcard spec and all has worked OK since (apart from the messages file noise, which I can live with for now). I never investigated this further to log a bug.

Hope that helps as an alternative workaround, and IMO, this is an automounter bug.

Brian



Danek Duvall wrote:
I had on my laptop (wumpus) a line in /etc/auto_home that read:

    duvall wumpus:/zool/&

(zool/duvall is the ZFS dataset on that machine where my home directory
lives).  Up through 2009.06 (build 111), this worked great -- the machine
would boot up, I'd log in as duvall in gdm, and I'd be on my way.

However, when I upgraded to build 116, this no longer worked.  Ditto on
build 118.  Logged in as root, I found that accessing /home/duvall gave me
permission denied.  The automount point existed, but nothing got mounted
there.  Fiddling around with the debugging in /etc/default/autofs, I saw in
the log:

    automountd: pingnfs: wumpus: RPC: Program not registered
    automountd: server wumpus not responding
    automountd: mount of /home/duvall failed

which made sense in that I didn't have NFS service enabled, but that wasn't
any different than it had been in my build 111 BE.

I managed to work around the problem by changing the line in /etc/auto_home
to follow something I found in one of the man pages:

    duvall -fstype=lofs :/zool/&

Question is -- was the first line ever right, and something broke in the
automounter between 111 and 116, or was it always wrong, and the bug or bad
assumption I was relying on finally went away?

Interestingly, in all of this I tried changing "wumpus" to "localhost",
which also didn't work, and neither did "127.0.0.1".  For that matter, I
couldn't resolve "localhost" despite it being in /etc/hosts, and pinging
the IPv4 loopback address failed (though the IPv6 one did).  This all
happened well before I set up any physical networking devices.  I don't
know whether this is related to the automounter issue or not, but in case
it is, I'm wrapping it all up, and sending to both these lists.

Thanks,
Danek
_______________________________________________
networking-discuss mailing list
[email protected]

--
Brian Ruthven                                        Sun Microsystems UK
Solaris Revenue Product Engineering             Tel: +44 (0)1252 422 312
Sparc House, Guillemont Park, Camberley, GU17 9QG

_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to