All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Ken Gillett <KenGroups@ukgb.net>, autofs@vger.kernel.org
Subject: Re: space(s) in key or location names
Date: Mon, 23 Nov 2015 09:40:37 +0800	[thread overview]
Message-ID: <1448242837.3733.11.camel@themaw.net> (raw)
In-Reply-To: <B75A85DC-1A7A-475F-AE15-7FBF60FCE936@ukgb.net>

On Fri, 2015-11-20 at 09:42 +0000, Ken Gillett wrote:
> I’m really struggling with this and hope someone can point me to a
> solution.
> 
> I need to automount onto a mountpoint (directory, i.e. folder as it’s
> on OS X) that has a space in the name and I cannot change that. I’ve
> read many suggestions to escape the space with a ‘\’ or ‘\040’ or
> quote the path, but nothing I’ve tried works. It either simply fails
> to work or creates the mountpoint that includes the escape chars in
> its name.
> 
> To clarify, other mounts that have no space involved work fine, so
> the basic setup is sound and if the automount is configured in a
> local (LDAP) directory, the space is no problem. However, I don’t
> want to use that method and really need to use simple map files in
> /etc, but there seems to be this issue with how they are parsed. I am
> clearly not the only person with this problem.
> 
> I’d really appreciate it if someone could explain how to overcome
> this and allow for spaces in pathnames used in map files.

The handling of spaces in automounting when using Sun format maps is
difficult because of the syntax of the map format, it allows for
ambiguity which make quoting difficult.

So I'm not surprised to here this.
But sadly I don't think we can help you because OSX uses a different
implementation to Linux autofs which I know nothing about.

Ian
--
To unsubscribe from this list: send the line "unsubscribe autofs" in

  reply	other threads:[~2015-11-23  1:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-20  9:42 space(s) in key or location names Ken Gillett
2015-11-23  1:40 ` Ian Kent [this message]
2015-11-23  1:53   ` 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=1448242837.3733.11.camel@themaw.net \
    --to=raven@themaw.net \
    --cc=KenGroups@ukgb.net \
    --cc=autofs@vger.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.