topic Simple Autofs question. in Operating System - HP-UX

Simple Autofs question.

Belinda Dermody — Wed, 29 Jan 2003 19:55:16 GMT

I have been using hard nfs mounts for years between our Production and Development systems and starting to use autoFS and have a problem, getting a invalid subdirectory on client side after a cd to mount point hangs and I do a cntl C. I can never get to see the files on the client side.

HP-UX 11.00 on host and client.
nsfconf file AUTOFS=1
AUTOMOUNT=0

/usr/ud/HARRIS in export file on host and exportfs -a ran.

auto-master on client looks like
/net -hosts -nosuid
/- /etc/auto_direct

auto-direct on client looks like
/ASPEN_SCHED2 -nosuid aspen:/usr/ud/HARRIS

Question the mountpoint ASPEN_SCHED2 does that have to exist or does it make it

Yes, I have read the man pages and HP info notes, I have problems reading and understanding things in depth. I like to work from small and add on or have really good examples to follow and take apart

Re: Simple Autofs question.

Belinda Dermody — Wed, 29 Jan 2003 20:15:10 GMT

Also, I did run /usr/sbin/automount

I also umounted the hard mount for /ASPEN_HARRIS prior to doing this and commented it out of the /etc/fstab file.

Re: Simple Autofs question.

Sridhar Bhaskarla — Wed, 29 Jan 2003 20:20:59 GMT

Hi,

You will need to set AUTOMOUNT=1 if you intend to use AUTOFS. Stop and start /sbin/init.d/nfs.client after the change.

You do not need to create /ASPEN_SCHED2 directory. Once the client is restarted, it will created. And once you cd to it, it will get mounted.

-Sri

Re: Simple Autofs question.

Paul Sperry — Wed, 29 Jan 2003 22:02:19 GMT

yes you have to create you mount points

cd /
mkdir ASPEN_SCHED2

Re: Simple Autofs question.

Jim Butler — Wed, 29 Jan 2003 22:15:51 GMT

On the server -
/etc/rc.config.d directory - check the following files
nfsconf
- Make sure SERVER=1
- CLIENT=1 is optional

namesvrs
Check nis domain (are you using NIS?) - If so, good, what is the NIS domain.

If not - then make sure the hosts files reference each other as nodenames, specifically so that the client sees the server as "aspen" and not aspen.domain.region.

So far so good.

Now - on the server run
/sbin/init.d/nfs.server stop;/sbin/init.d/nfs.server start -

on the client run
/sbin/init.d/nfs.client stop; /sbin/init.d/nfs.client start

This will restart everything for you.

If you answered that you have a nis domain above, then reference /etc/nsswitch.conf and make sure it is set up appropriately
automount: files nis

or
automount: files [notfound=CONTINUE] nis

Good Luck