All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stef Bon <stef@bononline.nl>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: autofs@linux.kernel.org
Subject: Re: make an executable map rerun.
Date: Wed, 25 Mar 2009 17:43:47 +0100	[thread overview]
Message-ID: <49CA5F43.6070408@bononline.nl> (raw)
In-Reply-To: <x498wmtkayg.fsf@segfault.boston.devel.redhat.com>

Jeff Moyer wrote:
> Stef Bon <stef@bononline.nl> writes:
>
>   
>> Hello,
>>
>> I've been working on a solution to make networkresources available via 
>> autofs on a dynamic way. After login with help
>> from ConsoleKit a mountpoint is added to the master file of the 
>> automounter. This mountpoint is in the homedirectory of the user logging in.
>>
>> This way I've a browseable network map in my home directory for Windows 
>> Networks (via cifs), FTP (via curlftpfs/FUSE) and SSH (with sshfs/FUSE). 
>> Others, like Novell should be possible.
>>     
>
> This sounds like interesting work.  Do you have it posted somewhere?
>   

Yes, look at:

http://linux.bononline.nl/linux/automountsmbshares/index.php
>   
>> It works with executable maps. Now for some reasons I would like some 
>> control over rerrunning the executable map, to make the automounter 
>> refresh the autofs data. Now I do not see how to do that. I reload 
>> signal does not do that.
>>
>> Is there a way to do this?
>>     
>
> No caching is done for program maps.  They are consulted for every
> single lookup, so you shouldn't have to do anything special.  Is this
> not the behaviour you are observing?
>   
No,

after activating the executable map once, the data provided by the 
executable map is kept. I've tested this by
letting the executable map write to an logfile, and it's running seldom.

I can look at the contents of /proc/mounts and here I see the autofs 
tree, which is kept. So I do not understand your remark
saying it is consulted every single lookup. Does the option -browse 
mather here? I'm using that and because this forces the automounter to 
remember the data right?

Stef
> Cheers,
> Jeff
>
>   

  reply	other threads:[~2009-03-25 16:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25  9:21 make an executable map rerun Stef Bon
2009-03-25 13:07 ` Jeff Moyer
2009-03-25 16:43   ` Stef Bon [this message]
2009-03-25 17:25     ` Jeff Moyer
2009-03-25 17:47       ` Stef Bon
2009-03-26  3:13       ` Ian Kent
2009-03-26  8:35         ` Stef Bon
2009-03-26 10:30           ` 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=49CA5F43.6070408@bononline.nl \
    --to=stef@bononline.nl \
    --cc=autofs@linux.kernel.org \
    --cc=jmoyer@redhat.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 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.