SUMMARY: Strange problem with autofs

From: Santithorn Bunchua (keh@abac.au.ac.th)
Date: Wed Aug 24 1994 - 18:26:42 CDT


Finally I found out that the permission of the mount point is
incorrect (drw-r--r--). This was because of my mistake. However,
it took me a long time to find it out because when the filesytem
is mounted .. what you will see from 'ls' is dr-xr-xr-x .. the
the real problem is hidden.

So I restart the machine in single user mode with no directory
mounted and change the permission of /home... then restart again.
The problem is now gone.

Thanks to all that replied,

--keh--

(original question and replies follow ... )

*** My original question ***

>Dear Sun Managers,
>
> I have found strange problems in my system. It occurs only when
>I am under the directories that is mounted by automount eg. /net and /home.
>The problem are:
> - the command like 'pwd' says .. cannot determine current directory
> - the shell escape '!' under program like ftp and vi doesn't work
> it doesn't execute the given command but only print one blank line.
> - the program 'screen' when being invoked under theses automounted
> directory ... exits immediately ... truss says that it get the
> SIGHUP.
>
>My system is SS/1000 with the following patches installed:
>
>Recommended Patches
>===================
>101317-09 lp jumbo patch
>101318-54 Jumbo patch for kernel (includes libc, lockd)
>101327-06 security and miscellaneous tar fixes
>101331-03 fixes for package utilities
>!101344-05 Jumbo NFS patch
>101347-01 system hangs due to mblk memory leak
>101615-02 miscellaneous utmp fixes
>101739-02 sendmail jumbo patch - security
>
>Other Patches
>=============
>101378-07 WIDE scsi negotiation and esp and isp driver fixes
>101409-03 Jumbo linker patch
>101415-02 ptm pts write service routines; process hung in ldtermclose
>101500-02 autofs patch
>101560-01 in.tftpd patch, in.tftpd -s /tftpboot doesn't chroot to /tftpboot
>
>These problem don't happen when I log in (or su) as superuser .. and it
>also doesn't happen when the login shell is 'ksh'. (My default login shell
>is csh).
>
>I hope you can help me...
>
>Thanks,
>
>--keh--
>

***** Here comes the replies *****

>From vjq09r4@shoes.Bell-Atl.Com Wed Aug 24 18:29:19 1994
Date: Tue, 16 Aug 1994 08:08:02 -0400 (EDT)
From: Reggie Beavers <vjq09r4@shoes.Bell-Atl.Com>
Reply to: Reggie Beavers <reginald.w.beavers@bell-atl.com>
To: keh@abac.au.ac.th
Subject: Re: Strange program with autofs

Maybe you have incorrect permissions set for the directory. If you don't
have read and execute permissions similiar things would happen.

Reggie
reginald.w.beavers@bell-atl.com

>From kanishka@lks.csi.com Wed Aug 24 18:29:21 1994
Date: Tue, 16 Aug 94 12:28:27 -0500
From: Kanishka de Lanerolle <kanishka@lks.csi.com>
To: Santithorn Bunchua <keh@abac.au.ac.th>
Subject: Re: Strange program with autofs

I have observed almost the same symptoms as you describe on sunos 4.1.3
server and client systems on rare occasions. I'd appreciate it if you would
summarize whatever useful responses you get to your query. Thanks,

--
Kanishka <kanishka@lks.csi.com>

>From Steve.Hearn@BarwonWater.Vic.Gov.Au Wed Aug 24 18:29:24 1994 Date: Wed, 17 Aug 1994 10:29:55 +1000 From: Steve.Hearn@BarwonWater.Vic.Gov.Au To: keh@abac.au.ac.th Subject: Re: Strange program with autofs

I have recently begun seeing similar problems here. Please let me know what you find out.

All the best.

Stephen Hearn Email : steve@BarwonWater.Vic.Gov.Au Information Systems, Barwon Water Phone : (+61) 52 262364, 61-67 Ryrie Street, Geelong, Australia Fax : (+61) 52 218236

>From todd@water.eng.mcmaster.ca Wed Aug 24 18:29:34 1994 Date: Wed, 17 Aug 1994 11:12:58 -0400 (EDT) From: Todd Pfaff <todd@water.eng.mcmaster.ca> To: Santithorn Bunchua <keh@abac.au.ac.th> Subject: Re: Strange program with autofs

Make sure automount was started with a umask of 022.

Look at permission of mount points under /tmp_mnt to see the problem. There are probably directories in there that are not readable by everyone.

You can...

Reboot to single user mode, clean out everything under /tmp_mnt and then continue booting to multi user mode.

or...

Kill the automount daemon, clean out /tmp_mnt and then restart automount from a shell with umask 022.

This sometimes happens when automount is started manually from a root shell with a umask of 077.

-- Todd Pfaff \ Internet: todd@water.eng.mcmaster.ca Dept. of Mechanical Engineering \ Voice: (905) 525-9140 x27351 McMaster University \ FAX: (905) 572-7944 Hamilton, Ontario, CANADA L8S 4L7 \



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:09:08 CDT