All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Urlings <tom.urlings@gmail.com>
To: autofs@linux.kernel.org
Subject: using --ghost with 'program' type maps
Date: Mon, 6 Apr 2009 11:17:10 +0200	[thread overview]
Message-ID: <200904061117.10949.tom.urlings@gmail.com> (raw)

hi all,
i have been using autofs for a long time now, using it to dynamically gather 
multimedia mounts using aufs locally and across local network..
however, ghosting is not supported for 'program' maps.. which makes sharing a 
autofs mount a bit odd..

example:
server:/srv/multimedia -> automounted locally on server
: uses aufs locally to mount all multimedia type directories on local storage

client:/opt/multimedia -> automounted locally on client
: uses aufs locally to mount all multimedia type directories on local storage 
and on automounted samba shares (also on server)

when server automount is mounted on client, server:/srv/multimedia is mounted, 
but (as spec'ed) ghosting is not performed, giving an empty directory..

looks like the lookup_ghost on client does nothing as there are no cached 
entries from the mapfile (program) available.. same goes on 
server:/srv/multimedia..

could this be easily integrated into the automount source?

i have been looking into it today, but it looks a bit quirky to just 
copy/paste the lookup_file.c:lookup_read_map into 
lookup_program.c:lookup_read_map (with all ancilliaries)..

idea is to have the program maps return a complete 'file' map when given no 
key on the commandline, and to 're-use' the lookup_file.c:lookup_read_map 
functionality in the lookup_program.c:lookup_read_map

do any of you have a direction into where i should start looking?

thanks in advance..

best regards,
tom urlings

-- 
Met vriendelijke groeten,
Best regards,

Tom Urlings

             reply	other threads:[~2009-04-06  9:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06  9:17 Tom Urlings [this message]
2009-04-12 14:20 ` using --ghost with 'program' type maps 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=200904061117.10949.tom.urlings@gmail.com \
    --to=tom.urlings@gmail.com \
    --cc=autofs@linux.kernel.org \
    /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.