[ChrisOwens]

[QUOTE][u]Quote by: macshome[/u][p][QUOTE][u]Quote by: ChrisOwens[/u][p][i]Additional data point:

I also noticed that when I accessed /foo from another machine via AFP, and I authenticated as user bar, user bar’s home directory was available as a share, even though it had never been set up as one. In other words, user home directories seem to be shared auto-magically.[/i]

[/p][/QUOTE]

Auto-sharing of the home folders has been the default for some time now. 10.4 at least, but I think even 10.3 did it.[/p][/QUOTE]

Is that something you can turn off?

[ChrisOwens]

[QUOTE][u]Quote by: macshome[/u][p]I’m a bit confused here. Although it probably shouldn’t error out on you, why would you want to loopback via the network to a directory on the server itself? [/p][/QUOTE]

If I want every machine in my domain to mount the [b]bar[/b] sharepoint on host [b]foo[/b], i’d create a mount record that mounts [b]foo:/bar[/b] in [b]/Network/Servers/foo[/b].

But what happens on [b]foo[/b] itself? It’s part of the domain, too, so it sees the mount request also. Automount is smart about this — it recognizes that the mount request refers to the local host, and instead of doing a mount, it just creates a symlink from /Network/Servers/foo to /

That means that you can always refer to /Network/Servers/foo/bar, and it will work correctly whether you are running on foo or whether you are running on any other machine in the domain.

[ChrisOwens]

Additional data point:

On a Leopard Workstation (not server) — I did the following:

1 mkdir /foo

2 use the GUI (“Sharing” control panel item) to share /foo with read/write by everyone

3 reboot the machine.

The log shows the -14135 error identical to what is in your log quoted above

Other hosts can mount and use the sharepoint

.DS_Store, Temporary Items, and Network Trash Folder do not show up in the directory

I also noticed that when I accessed /foo from another machine via AFP, and I authenticated as user bar, user bar’s home directory was available as a share, even though it had never been set up as one. In other words, user home directories seem to be shared auto-magically.

[ChrisOwens]

[QUOTE][u]Quote by: luke[/u][…] The user’s home directory will be saved as /Network/Servers/primary.workstation.organization.com/Users/username/. On a workstation that is not their primary workstation, that directory will be available over AFP. On the primary workstation, that directory will be available because it will be symlinked to the actual /Users directory. [/QUOTE]

The symlinking is what I don’t understand.. where does the magic happen? if I’m logged into primary.ws.org.com, what is it that causes /Network/Servers/primary.ws.org.com/Users to be symlinked to /Users? Should I manually create this? I was under the belief that manually messing with anything in /Network/Servers was un-Kosher.

Aside, it is, as you point out, probably more reasonable to use a central home directory server and portable home directories on all the user machines. Problem is, my available server for that purpose is a Linux machine, and the Linux afp server (netatalk) seems to have a hard time with OS X permissions and ACLs.

[edit: D’OH!!!!!! If I had not made a typo in my DNS zone records, all would have been fine a day ago. The symlinking magic happens, but only if the name of the Mount record in OD exactly matches (including case) the FQDN of the host. It was the case sensitivity that got me]

[Author]

Posts