[harwoodr]

macshome wrote:

Did you update the user records to match the case change?

Yep – changeip actually did that.

macshome wrote:

Automounter is configureable. Check man automount. You can also edit the mount by hand in NetInfo Manager in case WGM is doing something funky to the case when you save.

I’ll have to look into that…

[harwoodr]

sciron wrote:

Bear with my questions as I am a Unix person thrown into an Apple world.

> The automounter would be looking for:
> /Network/Servers/servername.Psychology.McMaster.CA/Users/username

> While if you looked in /Network/Servers/ you will see:
> /Network/Servers/servername.psychology.mcmaster.ca

assuming that the next item after ‘Servers/’ is the FQDN, there is no issue there. However, why would you specify ‘/Network/Servers/servername.Psychology.McMaster.CA/USERS/username’ to mount? ‘/Users/username’ is NOT part of the FQDN. When specifying mount locations from another machine in Unice-land, you specify it thusly:

FQDN:/Users/username (or servername.psychology.mcmaster.ca:/users/username). The colon is the separator telling the system that that part is not part OF the FQDN name, but an object ON the FQDN object.
I know OSX handles things similarly because 1) it’s FreeBSD based, and 2) check out how to mount NFS, and specifics in FSTAB.

Doesn’t work that way under OSX… especially for OpenDirectory attached clients… (LDAP & AFP… automounter isn’t configurable… and I can’t specify the user’s home directory mount point like that)…

What I’ve done for the time being is revert to a server image I made a while back – 10.4.5 – it’s not worth it…

So, we’ve established a moratorium on upgrading OSX servers for the time being.

I’m going to install OSX server on a non-production system and upgrade it all the way… and see what happens when they next release an update.

[Author]

Posts