When I start autofs using /etc/init.d/autofs start I get the following message * no automount maps defined and it seems to fail This is correct because I don't have any defined I then try and stop the service + I get * Stopping automounter... [!!] When I change the file to include some mount points and (re)start the service I get *WARNING: "autofs" has already been started Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: The initial autofs start should have properly cleaned up what ever files it uses and I should be able to attempt to (re)start the service if the first one fails.
output of 'emerge info' please? what version of autofs are you using? does it still happen with the latest ~x86 version?
When I unmaked the package, and emerged the version there. I'm still getting the same problem. I'm also noticing that when I have it set up to look over NIS for automount points it will mount / over mine. While I can see this is useful for somethings I was suprised that this was turned on by default.
could you provide your exact configuration for the two cases? (the initial bug report, and your NIS configuration) also post your emerge info output in this bug for others to see.
Emerge Info: # emerge info Portage 2.0.51-r15 (default-linux/x86/2004.3, gcc-3.3.5, glibc-2.3.4.20040808-r1, 2.6.10-gentoo-r6 i686) ================================================================= System uname: 2.6.10-gentoo-r6 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 9 2005, 20:48:54)] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.5, 1.9.4, 1.6.3, 1.7.9-r1, 1.4_p6, 1.8.5-r3 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -mcpu=i686 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="ftp://ftp.caliu.info/pub/gentoo/ http://mirror.datapipe.net/gentoo http://mirror.datapipe.net/gentoo http://mirrors.acm.cs.rpi.edu/gentoo/" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X apm arts avi bash-completion berkdb bitmap-fonts crypt cups encode f77 fam font-serverfoomaticdb fortran gdbm gif gpm gtk gtk2 imlib ipv6 java jpeg junit kde libg++ libwww mad mikmod mmap motif mpeg ncurses oggvorbis opengl oss pam pdflib perl png posix python qt quicktime readline ruby sdl spell ssl svga tcpd tetex threads tiff truetype truetype-fonts type1-fonts xml2 xmms xvzlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
where is the rest of the data I asked for? I need to know: - what version of autofs are you using? - your NIS configuration (the map data from NIS) - your configuration in /etc/autofs (whatever you have changed there, namely auto.master). please reopen with the required information.
- what version of autofs are you using? 4.1.3-r3 - your NIS configuration (the map data from NIS) I'm unsure of how to get this. Can you e-mail me with directions on how to get this? - your configuration in /etc/autofs (whatever you have changed there, namely auto.master). Nothing is changed in there.
For the NIS data, please run these commands (and attach their output as two seperate files). /usr/bin/ypcat -k auto.master /usr/bin/ypcat -k auto_master also, I'd like to know the output of: grep 'auto' /etc/nsswitch.conf
$ /usr/bin/ypcat -k auto.master /swapps auto.swapps -ro,intr /hwapps auto.hwapps -ro,intr /disks auto.disks -ro,intr /snfs auto.snfs -ro,intr /emc auto.emc -rw,intr /- auto.home -rw,intr $ /usr/bin/ypcat -k auto_master No such map auto_master. Reason: No such map in server's domain $ grep 'auto' /etc/nsswitch.conf automount: files
ok, the original problem you posted is fixed with -r4. As for the NIS mounting it's / over your /, I'm not certain what the correct workaround is, or if / should even be exported like that.
i'm closing this for now, since I feel all of the present behavior is correct, as per my previous message.
