autofs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Fox <mfox@customdatacentre.com>
To: autofs@vger.kernel.org
Subject: Changes to special character escaping?
Date: Fri, 7 Apr 2017 16:56:34 -0600	[thread overview]
Message-ID: <CAFVxx_NaVK6J=tvfCa7AUQDaGLPE0ipZjpcqc1N55N4KrY5kKA@mail.gmail.com> (raw)

Has something changed regarding escaping of special characters? The
methods used to deal with special characters in maps that are included
in distributions (ie. Ubuntu 16.04.2, so automount 5.1.1) no longer
seem to work.

Without special characters, autofs works wonderfully on all sorts of
CIFS shares. However, with a CIFS administrative share (C$), or a
share with an ampersand, I've had no luck. The shares work fine
through smbclient or when mounted by hand, but I haven't stumbled onto
how to get it working under autofs.

My problem setup is simple:

--- /etc/auto.master ---
+auto.master
/cifs /etc/auto.cifs --timeout=300 --ghost
------

--- /etc/auto.cifs ---
CDC1 -fstype=cifs,rw,noperm,credentials=/etc/creds/CDC1 \
     "/C$" "://CDC1/C\$"
------

It doesn't work as configured above. The output from 'automount -f -v' is:

------
attempting to mount entry /cifs/CDC1/C$
>> Retrying with upper case share name
>> mount error(6): No such device or address
>> Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
mount(generic): failed to mount //CDC1/C\$ (type cifs) on /cifs/CDC1/C$
failed to mount /cifs/CDC1/C$
------

If the escaping of '$' is removed from auto.cifs, the last two lines
of output change to:

------
mount(generic): failed to mount //CDC1/C (type cifs) on /cifs/CDC1/C$
failed to mount /cifs/CDC1/C$
------

More slashes don't help.

What is the correct way, if any, to escape a special character in the
situation I've outlined?

This problem aside, autofs has allowed us to greatly simplify the
interaction between our backup system and Windows servers. A heartfelt
thank-you to everyone involved.


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

             reply	other threads:[~2017-04-07 22:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07 22:56 Mark Fox [this message]
2017-04-10  7:49 ` Changes to special character escaping? Ian Kent
2017-04-10  8:07 ` 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='CAFVxx_NaVK6J=tvfCa7AUQDaGLPE0ipZjpcqc1N55N4KrY5kKA@mail.gmail.com' \
    --to=mfox@customdatacentre.com \
    --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 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 read-only IMAP folder(s) and NNTP newsgroup(s).