From: Farkas Levente <lfarkas@bppiac.hu>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: automount never umount
Date: Fri, 25 Nov 2005 00:17:36 +0100 [thread overview]
Message-ID: <43864A10.4090801@bppiac.hu> (raw)
In-Reply-To: <Pine.LNX.4.63.0511242003250.2069@donald.themaw.net>
Ian Kent wrote:
> 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?
>
>
> These's still no printk output?
>
> So no explanation of what is wrong.
>
> Jeff we could enable DEBUG in the kernel module.
> What do you think.
>
> If it would be better I could take the source from the kernel you have and
> put together a tarball. Farkas could then compile and install it so that
> the original module can restored with a "make uninstall" when we are done.
i try what you want, althugh i prefer rpms.
--
Levente "Si vis pacem para bellum!"
next prev parent reply other threads:[~2005-11-24 23:17 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 [this message]
2005-11-28 15:41 ` Jeff Moyer
2005-11-28 16:11 ` Ian Kent
2005-11-29 12:28 ` Farkas Levente
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=43864A10.4090801@bppiac.hu \
--to=lfarkas@bppiac.hu \
--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.