From: Ian Kent <raven@themaw.net>
To: "Philip Ong Jr." <pongjr@gmail.com>
Cc: autofs@linux.kernel.org
Subject: Re: 5.0.5 non-expiring mounts
Date: Fri, 11 Feb 2011 11:10:34 +0800 [thread overview]
Message-ID: <1297393834.2757.5.camel@perseus> (raw)
In-Reply-To: <4D510D53.7010507@gmail.com>
On Tue, 2011-02-08 at 01:30 -0800, Philip Ong Jr. wrote:
> I've pulled down the 5.0.5 tree and all patches.
>
> I've set the logging level to debug and can see messages of expiring
> mounts in /var/log/messages...but when I check /etc/mtab or /proc/mounts
> or df, i can still see them there. Any ideas if this is a known issue or
> if I can give more info than below?
You will need to post a full debug log somewhere.
Make sure that syslog is capturing daemon.* to the syslog so that you
get all the debug log messages.
>
>
> Linux sc-sim-208-144 2.6.29.4 #8 SMP Tue May 25 14:00:33 PDT 2010 x86_64
> x86_64 x86_64 GNU/Linux
> # automount -V
>
> Linux automount version 5.0.5
>
> Directories:
> config dir: /etc/sysconfig
> maps dir: /etc
> modules dir: /usr/lib/autofs
>
> Compile options:
> DISABLE_MOUNT_LOCKING ENABLE_IGNORE_BUSY_MOUNTS LIBXML2_WORKAROUND
>
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs
next prev parent reply other threads:[~2011-02-11 3:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 9:30 5.0.5 non-expiring mounts Philip Ong Jr.
2011-02-11 3:10 ` Ian Kent [this message]
2011-02-15 1:10 ` Mike Marion
2011-02-15 3:11 ` Ian Kent
2011-02-15 3:37 ` Ian Kent
2011-02-15 5:28 ` Mike Marion
2011-02-15 12:28 ` Ian Kent
2011-02-15 18:11 ` Leonardo Chiquitto
2011-02-16 7:08 ` Ian Kent
2011-02-16 12:18 ` Ian Kent
2011-02-23 20:22 ` Leonardo Chiquitto
2011-02-16 12:58 ` Leonardo Chiquitto
2011-03-04 20:10 ` Leonardo Chiquitto
2011-03-05 5:18 ` Ian Kent
2011-03-24 22:03 ` Leonardo Chiquitto
2011-03-28 3:17 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2011-02-17 1:08 Deke Clinger
2011-02-17 7:57 ` Ian Kent
2011-02-17 19:21 Deke Clinger
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=1297393834.2757.5.camel@perseus \
--to=raven@themaw.net \
--cc=autofs@linux.kernel.org \
--cc=pongjr@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).