Thanks to Mr. Anvin, and a few others. I now have entries in auto.home that are without the double colon, I can look at the map via 'ypcat -k auto.home' and see the entries correctly. However, I still cannot mount the home directory correctly. Perhaps I should be shot, but I can't figure out why the automounter isn't mounting the home directory...
Scenario: My workstation (RedHat 7.3, when yp.conf has the old NIS master (Solaris 7 box) listed, everything works fine with the defaults, no auto.home file in /etc on the workstation here). Courty, in this case, is the NIS master, and Homer is the, hopefully, new NIS master in the near future. ypcat -k auto.home results in : wsarka homer:/export/home:& tmp courty:/export/scratch When I switch to the "new" NIS master, which was a former NIS slave (I imported the NIS source files, auto.home auto.master passwd group, etc), the automounter, for whatever reason doesn't want to mount my home directory, BUT I can still mount the /home/tmp directory off of Courty. I'm exporting /export/home from /etc/exports with just rw permissions, nothing special. The fact that I can mount /home/tmp (from the old NIS master) proves to me that the maps are now correct, so that the problem is narrowed down to the interaction between the automounter and the NFS server on the Linux box? ypcat -k auto.home results in: wsarka homer:/export/home/wsarka tmp courty:/export/scratch I've updated the auto.home map on the Linux box and removed the double-colon entries, and now just have the single colon entries as described above. auto.master on Linux box: # $Id: auto.master,v 1.2 1997/10/06 21:52:03 hpa Exp $ # Sample auto.master file # Format of this file: # mountpoint map options # For details of the format look at autofs(8). /home yp:auto.home /misc /etc/auto.misc --timeout=60 auto_master on Solaris box: # Master map for automounter # +auto_master /net -hosts -nosuid,nobrowse /home auto_home /xfn -xfn As a test, I edited the /etc/yp.conf on my workstation to point to the old NIS master and then the new NIS master, each time stopping autofs and ypbind and then restarting them with the change I implemented. After the change, I would su - wsarka, as root, to test whether or not the automounter was working. Here's the relevant parts of the /var/log/messages file: edit yp.conf, point to Courty, Solaris NIS master: May 30 12:28:21 dim-4100-l1 ypbind: bound to NIS server courty.boulder.emperative.com May 30 12:28:29 dim-4100-l1 automount[18947]: starting automounter version 3.1.7, path = /home, maptype = yp, mapname = auto.home May 30 12:28:29 dim-4100-l1 autofs: automount startup succeeded May 30 12:28:29 dim-4100-l1 automount[18947]: using kernel protocol version 3 May 30 12:29:15 dim-4100-l1 automount[18947]: attempting to mount entry /home/wsarka May 30 12:29:15 dim-4100-l1 su(pam_unix)[18960]: session opened for user wsarka by root(uid=0) edit yp.conf, point to Homer, Linux NIS master: May 30 12:31:12 dim-4100-l1 ypbind: bound to NIS server homer.boulder.emperative.com May 30 12:31:27 dim-4100-l1 automount[19206]: starting automounter version 3.1.7, path = /home, maptype = yp, mapname = auto.home May 30 12:31:27 dim-4100-l1 automount[19231]: starting automounter version 3.1.7, path = /misc, maptype = file, mapname = /etc/auto.misc May 30 12:31:27 dim-4100-l1 autofs: automount startup succeeded May 30 12:31:27 dim-4100-l1 automount[19231]: using kernel protocol version 3 May 30 12:31:49 dim-4100-l1 automount[19206]: attempting to mount entry /home/wsarka May 30 12:31:49 dim-4100-l1 automount[19242]: >> mount: special device /export/home/wsarka does not exist May 30 12:31:49 dim-4100-l1 automount[19242]: mount(bind): failed to mount --bind /export/home/wsarka on /home/wsarka, trying symlink Any help in this matter would be appreciated. Just trying to pry the last vestiges of the Solaris box out of the network, and this is the last piece. If there is something obvious that I'm missing, or if there is another piece of information I forgot, please let me know. Thanks in advance, Will
