Shadowed ‘Classic’ volume sticking at logout

[peet1]

This has truly been baking my noodle for the last week. I’ve worked on this problem for about 30 hours and have finally isolated all the symptoms.

Here’s the setup. I’ve got a single xServe and a large ATA to SCSI RAID that is serving a simple shared netinfo addressed @ 10.8.159.10 and “network”. I’m working with 4 clients right now and trying to propagate to about 30 or 40 machines.

Client machines are authenticating correctly and mounting users shared home directories. (i.e. automount dynamically, guest access enabled everywhere it needs to be, automounted over afp et all).

So here’s the rub if I mount classic with the shadow file in the user’s home directory on the server, the next login has a ‘stuck’ Classic volume in the Volumes folder and the dev appears to still be there. The name ‘Classic’ will be there with or without an icon, but the moment you clic it it disappears. It is however IMPOSSIBLE TO UNMOUNT after it gets to this point. I’ve tried every command that I can find. (tell finder eject, umount, umount -f, disktool -e and disktool -u). If the user manually stops classic, then manually unmounts the ‘Classic’ volume everything is good. That, of course is not an option in a managed environment. (The fact that I can get them to login is pretty amazing).

The script that I use to mount the volume is very simple;

do shell script “/usr/bin/hdid /Library/Management/Classic.dmg -shadow ~/Library/Classic/Shadow_Classic”

I have it in a statically mounted automount in ‘/Network/Volumes/Applications’ and it’s set as a login item in workgroup manager. I’m not sure if it’s possible to script a logout hook that could stop classic and unmount the ‘Classic’ volume before the damage is done. I’m not exactly sure the precise moment a logout script is run. Moreover, the above script represents the extent of my scripting ability.

To make things more confounding on (at least for me) if I change the script to use a local folder to store the shadow file EVERYTHING WORKS. ie

do shell script “/usr/bin/hdid /Library/Management/Classic.dmg -shadow /Temp/.shadows/Shadow_Classic”

This presents two problems.

1. It forces me to have another r/w area on the local drives (really a very minor issue)

2. Much more importantly it doesn’t allow users to have their own personal shadow file so they can set specific preferences for applications like quark … which must run on an unlocked volume.

I’ve attached text files of the output i get from mount, disktool and umount. There are also two screen shots showing the “Volumes” folder after ‘Classic’ sticks.

Thank you very much for your time. Like I said I’ve really hit a wall here and any help would be appreciated.

thanks.peet

[Author]

Posts