From: Farkas Levente <lfarkas@bppiac.hu>
To: jmoyer@redhat.com
Cc: autofs@linux.kernel.org, Ian Kent <raven@themaw.net>
Subject: Re: automount never umount
Date: Tue, 29 Nov 2005 13:28:51 +0100 [thread overview]
Message-ID: <438C4983.30504@bppiac.hu> (raw)
In-Reply-To: <17291.9542.484484.306141@segfault.boston.redhat.com>
Jeff Moyer wrote:
> ==> Regarding Re: [autofs] automount never umount; Ian Kent <raven@themaw.net> adds:
>
> raven> On Thu, 24 Nov 2005, Farkas Levente wrote:
>
>>>Jeff Moyer wrote: > lfarkas> a full lsof ? fuser -v for what?
>>>
>>>>For the mount points in question. I guess something like:
>>>>
>>>>fuser -v -m <automountpoint>
>>>>
>>>>lsof +D <automountpoint>
>>>
>>>ok now i use only nfs and no smbfs, uprgade to
>>>kernel-2.6.14-1.1641_FC4.jmoyertest.2 but it doesn't show me any
>>>difference. so here is the current daemon log and that's all:-(
>>>-------------------------------
>>>[root@garfield ~]# fuser -v -m /net/
>>>
>>>USER PID ACCESS COMMAND /net/ root 1919 f.... automount [root@garfield
>>>~]# lsof +D /net/ COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
>>>automount 1919 root 5r DIR 0,20 0 5471 /net/
>>>-------------------------------
>>>new tips?
>
>
> raven> These's still no printk output?
>
> I find that difficult to believe. Farkas, are you using the `dmesg'
> command to look for the printk output? Please do, as I'm certain there are
> a *lot* of messages generated.
opps. sorry i'm just look into daemon log while these are go into kern
log:-(
> Sure, you could enable debug. I just didn't want to get too much
> information. However, at this point, it's probably better that we get as
> much as possible so Farkas doesn't have to keep trying new patches.
>
> Farkas, please look at the output of dmesg and let us know what you find.
> You should see something like this:
# dmesg |sort|uniq
autofs4_revalidate: revalidate called on behalf of application "automount"
autofs4_revalidate: revalidate called on behalf of application
"multiload-apple"
so what can i do? no longer use multiload-applet ? this is a standard
gnome applet included in fc4: "System Monitor 2.10.1"
--
Levente "Si vis pacem para bellum!"
next prev parent reply other threads:[~2005-11-29 12:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 15:31 automount never umount Farkas Levente
2005-11-22 13:27 ` Ian Kent
2005-11-22 9:43 ` Farkas Levente
2005-11-22 13:03 ` Ian Kent
2005-11-22 16:19 ` Farkas Levente
2005-11-22 16:50 ` Jeff Moyer
2005-11-22 21:24 ` Farkas Levente
2005-11-22 23:27 ` Ian Kent
2005-11-23 0:24 ` Jeff Moyer
2005-11-23 9:27 ` Farkas Levente
2005-11-23 13:13 ` Ian Kent
2005-11-23 13:18 ` Farkas Levente
2005-11-23 15:28 ` Jeff Moyer
2005-11-23 15:38 ` Ian Kent
2005-11-23 16:57 ` Jeff Moyer
2005-11-23 17:13 ` Farkas Levente
2005-11-23 17:16 ` Jeff Moyer
2005-11-24 10:05 ` Farkas Levente
2005-11-24 12:10 ` Ian Kent
2005-11-24 23:17 ` Farkas Levente
2005-11-28 15:41 ` Jeff Moyer
2005-11-28 16:11 ` Ian Kent
2005-11-29 12:28 ` Farkas Levente [this message]
2005-12-01 9:31 ` Farkas Levente
2005-12-01 11:03 ` Ian Kent
2005-12-01 11:36 ` Farkas Levente
2005-12-01 12:57 ` Jeff Moyer
2005-12-01 13:41 ` Farkas Levente
2005-12-01 15:02 ` Ian Kent
2005-12-01 13:45 ` Ian Kent
2005-12-01 13:53 ` Farkas Levente
2005-12-01 15:04 ` Ian Kent
2005-11-23 14:26 ` Ian Kent
2005-11-22 23:18 ` 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=438C4983.30504@bppiac.hu \
--to=lfarkas@bppiac.hu \
--cc=autofs@linux.kernel.org \
--cc=jmoyer@redhat.com \
--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.