From: Tom Georgoulias <tom.georgoulias@freescale.com>
To: raven@themaw.net
Cc: autofs mailing list <autofs@linux.kernel.org>
Subject: Re: mount point created if automount map is empty during daemon startup?
Date: Tue, 04 May 2004 10:26:08 -0500 [thread overview]
Message-ID: <4097B610.6090405@freescale.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0405042248180.17014@donald.themaw.net>
raven@themaw.net wrote:
> Can you try killing and then starting that automount process by hand.
There wasn't any daemon running for that mount, so I started it by hand
and the mount is now functional.
I'm really confused as to why there wasn't a daemon running in the first
place. There should've been, right? I just checked a second system
where this was an issue and it is the same, not automount running for
/sync. Starting it manually also gets the mount working.
[root@hatfield12 init.d]# ps -ef | grep sync
root 1952 30817 0 09:57 pts/1 00:00:00 grep sync
[root@hatfield12 init.d]# /usr/sbin/automount /sync yp auto.sync
-rw,hard,intr rsize=32768,wsize=32768
[root@hatfield12 init.d]# ls /
bin designs eng home lost+found proc sbin sync usr
boot dev etc initrd mnt proj sea tmp var
design docs extern lib opt root soc _TOOLS_
[root@hatfield12 init.d]# cd /sync
[root@hatfield12 sync]# ls
[root@hatfield12 sync]# cd cache/tx30/tec/moccasin/s9a/
[root@hatfield12 s9a]# ls
s9a003a358100a3fb-1.1-1066343169-0 s9a8254af9c23b915-1.21-1079127946-0
s9a01243cb66ae420-1.5-1077918456-0 s9a8254af9c23b915-1.22-1082349030-0
s9a01d98600756aeb-1.1-1078525174-dir s9a8254af9c23b915-1.23-1083337330-0
s9a020e8a919ca408-1.1-1061176253-0 s9a82a9998c51e8c9-1.1-1058813656-0
s9a021d52f809fdbc-1.2-1078845514-0 s9a83027946cc8cd7-1.2-1046231817-0
>
> Just send a normal (TERM) kill and see if it exits normally.
>
> I would be interested in seeing anything in the log.
There doesn't seem to be anything related to this map, save for the
event when I ran a script that sends a HUP to the daemon responsible for
this map and noticed this problem all together.
Is there a particular string you'd like for me to search against?
[root@hatfield12 log]# grep auto.sync messages
Feb 20 09:57:34 hatfield12 automount[1597]: starting automounter version
4.1.0, path = /sync, maptype = yp, mapname = auto.sync
Feb 20 15:33:42 hatfield12 automount[25801]: starting automounter
version 4.1.0, path = /sync, maptype = yp, mapname = auto.sync
Feb 20 15:59:47 hatfield12 automount[1609]: starting automounter version
4.1.0, path = /sync, maptype = yp, mapname = auto.sync
Feb 20 16:35:52 hatfield12 automount[1605]: starting automounter version
4.1.0, path = /sync, maptype = yp, mapname = auto.sync
Mar 20 08:50:41 hatfield12 automount[1257]: starting automounter version
4.1.0, path = /sync, maptype = yp, mapname = auto.sync
Mar 21 11:38:57 hatfield12 automount[1273]: starting automounter version
4.1.0, path = /sync, maptype = yp, mapname = auto.sync
May 4 08:26:51 hatfield12 in.rshd[23849]: root@bender as root:
cmd='pkill -HUP -f auto.sync'
--
Tom Georgoulias
POPI Classification
[x] General Business Information
[] Freescale Semiconductor Internal Use
[] Freescale Semiconductor Confidential Proprietary
next prev parent reply other threads:[~2004-05-04 15:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 12:58 An offer to host autofs.org raven
2004-05-03 17:55 ` Tim Hockin
2004-05-04 0:32 ` Axel Thimm
2004-05-04 1:10 ` Ian Kent
2004-05-04 1:09 ` Tim Hockin
2004-05-04 1:21 ` humm " Alvin Oga
2004-05-04 12:25 ` Axel Thimm
2004-05-04 14:37 ` mount point created if automount map is empty during daemon startup? Tom Georgoulias
2004-05-04 14:53 ` raven
2004-05-04 15:26 ` Tom Georgoulias [this message]
2004-05-04 15:37 ` raven
2004-05-04 15:43 ` Tom Georgoulias
2004-05-04 15:52 ` raven
2004-05-04 15:27 ` raven
2004-05-04 15:05 ` Jeff Moyer
2004-05-04 15:22 ` raven
2004-05-04 15:37 ` Tom Georgoulias
2004-05-04 15:57 ` raven
2004-05-04 20:41 ` Tom Georgoulias
2004-05-05 1:08 ` Ian Kent
2004-05-04 18:04 ` An offer to host autofs.org H. Peter Anvin
2004-05-04 18:21 ` fork - " Alvin Oga
2004-05-04 18:26 ` Michael Blandford
2004-05-04 21:16 ` Mike Waychison
2004-05-04 21:50 ` Axel Thimm
2004-05-04 22:04 ` Mike Waychison
2004-05-05 1:16 ` Ian Kent
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4097B610.6090405@freescale.com \
--to=tom.georgoulias@freescale.com \
--cc=autofs@linux.kernel.org \
--cc=raven@themaw.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.