X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; q=dns; s=default; b=R5/t+
	Afbl4fsBL9nyvfQ50D+fcOuEnJDT/ztV0epc7xRvt8YUWwVFZ71f6fqv1yhYAcd8
	VWVDTZGSLnbLodx6M3C3OFuiIIuDqSgd9fmCeefqbwKzivyqEqW6Jt09eC9C+4hv
	HtrOHGasb4Oa63E6y2rqN3PZ/LeSyHzdEKDtbk=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type; s=default; bh=dNFibwcZY6j
	qETpFP503PuQa2h8=; b=hhqt4uoSjWDakkCRacATrtcU4J2AQJbHAzNV1n0ymeM
	ziaSraUtYXNjs51fwLaILh4/k4QyvVIaLfPiPv0chjJr0TidYkFa/yJbW8+hj7qZ
	twn0ZYTsSanBE8MOOiinX9L6pETkrTBTl0bqHJc6vpNHkAYiTq23h7l6/QJO+s9Q
	=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS,T_FILL_THIS_FORM_SHORT autolearn=ham version=3.3.2 spammy=H*f:sk:UpyLFys, H*i:sk:UpyLFys
X-HELO: mail-in-07.arcor-online.net
X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-09.arcor-online.net 3qmQc06btfzB33g
From: Achim Gratz <Stromeko AT nexgo DOT de>
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin-2.5.0 net share wbadmin no longer working post update
References: <CAN2X4tEmO4H8=757x_CYFWPHtcOr+YMRfR2b07Vg7rFcrNY6tg AT mail DOT gmail DOT com>	<loom DOT 20160414T170618-303 AT post DOT gmane DOT org>	<CAN2X4tFfqgPS5Jc9=rodiv_4mE-mb3akSD925oA1tWy6C5jebA AT mail DOT gmail DOT com>	<87ega8t99o DOT fsf AT Rainer DOT invalid>	<CAN2X4tHMu32aFfAnbz0fC3heNLBHrXPxVkcQvp8+RgT_o7rNbw AT mail DOT gmail DOT com>	<87a8kwt39s DOT fsf AT Rainer DOT invalid>	<CAN2X4tExtHpod9R_LLwt4sFvEJKp_bSh=UpyLFys5SbK1A1XnQ AT mail DOT gmail DOT com>
Date: Fri, 15 Apr 2016 07:10:50 +0200
In-Reply-To: <CAN2X4tExtHpod9R_LLwt4sFvEJKp_bSh=UpyLFys5SbK1A1XnQ@mail.gmail.com>	(Alexandria Gutierrez's message of "Thu, 14 Apr 2016 15:48:24 -0400")
Message-ID: <87r3e7lan9.fsf@Rainer.invalid>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.92 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain

Alexandria Gutierrez writes:
> On the original script I am using -backuptarget=\\\\SERVERNAME\\PATH\\TO\\SHARE
> to avoid the use of quotes. I have several cygwin version installed
> across multiple windows nodes. All of them work correctly.

That only takes care of the first level of quote removal and escape
processing.  This already takes place on the Linux box where you send
the command.  The command sent through ssh will consequently come out as
-backuptarget=\\SERVERNAME\PATH\TO\SHARE on the other side.  This gets
again processed by some shell (whatever you've configured as the login
shell for your user that ssh logs in as and also the shell the user runs
on the local machine).  So, depending on how exactly things are
configured, you'll likely end up with something like
-backuptarget=\SERVERNAMEPATHTOSHARE (the single backslashes might stay
in some cases).

> On the 2 new cygwin-2.5.0 nodes using the same script (already working
> with 2.4.0 and older) does not work. One was a cygwin upgrade, and the
> other was a clean install.

You seem to be relying on some side effect / configuration that is
present on the older installs, but not the newer.  The difference is
most likely what the system determines as your passwd entry and any
startup scripts that user may have.  Also, it makes a difference of
whether you request a TTY for the ssh process or not.

> Just as an update, even if I connect directly via ssh to the node and
> and run either:
>
> /cygdrive/c/windows/Sysnative/wbadmin START BACKUP -user:USERNAME
> -password:PASSWORD -backuptarget:'\\SERVERNAME\PATH\TO\SHARE'
> -allCritical -systemstate -quiet
> or
> /cygdrive/c/windows/Sysnative/wbadmin START BACKUP -user:USERNAME
> -password:PASSWORD -backuptarget:\\\\SERVERNAME\\PATH\\TO\\SHARE
> -allCritical -systemstate -quiet

Since it seems you really need two levels of quotes and the wbadmin
command does not need to have quotes in it (just guessing, and it may
actually need another pair of quotes if the path contains spaces), maybe

-backuptarget:"'\\SERVERNAME\PATH\TO\SHARE'"

is enough.

> it does not work. I do understand what you mean that SSH will strip
> the quotes.

If you want to see the command line that ssh gets, you
can add "-v" to the invocation.  If you want to see what gets run on the
other side, try some variant of

ssh -v user AT host /bin/procps -elfww\; your_command


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple