• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1110
  • Last Modified:

Solaris NIS: Auto.direct not mounting “ksh: /mountpoint: not found”

Hey!

So, I cannot get the auto.direct to function with an otherwise working NIS.  I inherited this setup, so I am be unfamiliar with parts of it.

Basically, we have automount maps for /home, /share and “auto direct”.  

The home and share works flawlessly, but the auto.direct was filled with mounts that were no longer available (all to a non-existent server.)

I emptied out all the non-existent mounts and added a couple of existing ones, pushed out the map but the mounts won’t work.

When I “ypcat –k auto.direct” on any of the client machines, it shows the correct changes...but when I go to /mountpoint...I get a “/mountpoint: not found” error.  

It doesn’t matter if I mkdir a “/mountpoint” dir on the client (Solaris in this case) or not.

It also doesn’t matter if I restart “/etc/init.d/autofs” or “/etc/init.d/nscd” (solaris client)

Here’s what the auto.master looks like:
/-   auto.direct
/home   auto.home
/share   auto.share

What am I missing?

Thanks!
M
0
Mike R.
Asked:
Mike R.
1 Solution
 
yuzhCommented:
To use auto_direct, please have a look at the instructions in the following doc:
http://docs.hp.com/en/5990-7199/ch03s06.html

(It is for HP-UX, it can also apply to Solaris).

also please check your /etc/nsswitch.conf to make sure automount use "nis"
eg:
automount: files nis

Here're some NIS FAQ/How-To  docs:
http://www.unix.org.ua/orelly/networking_2ndEd/nfs/ch09_02.htm
http://mleahu.home.cern.ch/mleahu/doc/unix/net/nis%20faq.htm
http://yolinux.com/HOWTO/NIS-HOWTO.html
http://www.softpanorama.org/Net/NIS/nis_maps.shtml
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now