All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Latrell" <is85022@cis.nctu.edu.tw>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org, ramana@intraperson.com
Subject: Re: Large number of mount request.
Date: Fri, 7 Jul 2006 12:04:45 +0800	[thread overview]
Message-ID: <00b201c6a17a$8050d160$251a17ac@ZyXEL.com> (raw)
In-Reply-To: 1152187091.8761.6.camel@raven.themaw.net

There will be an automount daemon for 1 ftp session (used to mount shares 
under home directory).
I sent SIGTERM to automount when my FTP session close (because the 
corresponding automount daemod need to be killed).
In my scenario, there should be multi-sessions need to be closed. Thus, 
SIGTERM will not be unique.

My autofs version is 4.1.4 with patch autofs4-2.4.29-20050404.patch.
kernel is 2.4.31 (no autofs patch for 2.4.31)

Thanks, for your comment,
Latrell.
----- Original Message ----- 
From: "Ian Kent" <raven@themaw.net>
To: "Latrell" <is85022@cis.nctu.edu.tw>
Cc: <ramana@intraperson.com>; <autofs@linux.kernel.org>
Sent: Thursday, July 06, 2006 7:58 PM
Subject: Re: [autofs] Large number of mount request.


> On Thu, 2006-07-06 at 11:52 +0800, Latrell wrote:
>> Do you mean my ghost option didn't make it in time thus "cd share1" 
>> failed?
>> I got the following message whenever there's "Failed to change directory"
>> error:
>>
>> automount[2306]: aquire_lock: can't lock lock file interrupted:
>> /var/lock/autofs
>
> And what is sending the SIGQUIT, SIGTERM or SIGINT to autofs to cause it
> to stop waiting and return a interrupted fail?
>
>> automount[2306]: failed to mount autofs path /tmp/users/shares/1034
>>
>> automount[2306]: /ramdisk/mnt/var1/tmp/users/shares/1034: mount failed!
>>
>> I also checked the ghost did create directory share1 under the home
>> directory. Could the lock problem cause cd share1 fail?
>>
>> Thanks for your comment,
>> Latrell.
>>
>> ----- Original Message ----- 
>> From: "ramana" <intraperson@yahoo.com>
>> To: "Latrell" <is85022@cis.nctu.edu.tw>; <autofs@linux.kernel.org>
>> Sent: Friday, June 23, 2006 7:27 PM
>> Subject: Re: [autofs] Large number of mount request.
>>
>>
>> > --- Latrell <is85022@cis.nctu.edu.tw> wrote:
>> >
>> >> Hi, all:
>> >>
>> >> I have a problem with the mount and umount packet.
>> >> My problem is when I have a large number of mount requests, some
>> >> mount request packets are missing. Thus, when I "cd share1", I will
>> >> get "fail to change directory" because share1 is not mounted. Fewer
>> >> mount requests work normally.
>> >
>> > I am afraid, this is ENOENT bug.
>> >
>> > Thanks in advance.
>> >
>> > Regards
>> > ramana
>> >
>> > __________________________________________________
>> > Do You Yahoo!?
>> > Tired of spam?  Yahoo! Mail has the best spam protection around
>> > http://mail.yahoo.com
>> >
>> > __________________________________________________
>> > Do You Yahoo!?
>> > Tired of spam?  Yahoo! Mail has the best spam protection around
>> > http://mail.yahoo.com
>> >
>>
>> _______________________________________________
>> autofs mailing list
>> autofs@linux.kernel.org
>> http://linux.kernel.org/mailman/listinfo/autofs
> 

  reply	other threads:[~2006-07-07  4:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-14  7:14 Large number of mount request Latrell
2006-06-15 13:21 ` Jeff Moyer
2006-06-23 11:27 ` ramana
2006-07-06  3:52   ` Latrell
2006-07-06 11:29     ` Ian Kent
2006-07-06 11:58     ` Ian Kent
2006-07-07  4:04       ` Latrell [this message]
2006-07-07  9:03         ` Ian Kent
2006-07-07 12:09           ` Latrell
2006-07-07 14:40             ` Jeff Moyer
2006-07-08  5:01               ` Ian Kent
2006-07-08  5:53                 ` ramana
2006-07-10  1:40                   ` Latrell
2006-07-10  5:41                     ` Ian Kent
2006-07-10  7:23                       ` Latrell

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='00b201c6a17a$8050d160$251a17ac@ZyXEL.com' \
    --to=is85022@cis.nctu.edu.tw \
    --cc=autofs@linux.kernel.org \
    --cc=ramana@intraperson.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.