I honestly don't know. The initial patches from April 12th of 2017 were all
I needed and I haven't messed with it since.
On Wed, Jun 6, 2018, 09:20 Andreas Hasenack,
wrote:
> @mark-fox, were those two patches the only changes you needed, or was
> the change to the awk script (re
And the second part of the patch.
** Patch added: "Part 1/1"
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1680224/+attachment/4860739/+files/patch_1.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ian produced a patch that addresses the problem, at least as far as I've
tested it. Whether the target is properly escaped or quoted, it works as
expected.
The patches (to AutoFS 5.1.2, available from git.kernel.org) are
attached and will likely be integrated into AutoFS 5.1.3.
** Patch added:
Thanks Josh. I actually tried using ASCII codes for the characters the
day I filed the report. No dice. I've managed to make contact with Ian,
an (the?) autofs maintainer. He thinks he's narrowed the problem down to
a particular commit. If we make any progress, I'll share it here.
--
You
Experimenting with this a bit, shares with spaces in their names work
fine, but anything with $ or & fails. Ampersands are particularly
troublesome, crashing the automounter if not escaped properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
This is probably related to #385244.
I've been unable to get a Windows administrative share (ie. C$) mounted
through Autofs. Non-administrative shares work fine. Administrative
shares are accessible with the same credentials from other Windows 10
workstations and through
