From: Michael Albinus <michael.albinus@gmx.de>
To: Jason Rumney <jasonr@gnu.org>
Cc: Andreas Schwab <schwab@suse.de>, 18199@debbugs.gnu.org
Subject: bug#18199: 24.4.50; tramp uses wrong arguments to nc
Date: Thu, 07 Aug 2014 11:27:28 +0200 [thread overview]
Message-ID: <87mwbgvedb.fsf@gmx.de> (raw)
In-Reply-To: <87y4v1y6i5.fsf@gnu.org> (Jason Rumney's message of "Wed, 06 Aug 2014 23:36:50 +0800")
Jason Rumney <jasonr@gnu.org> writes:
> Now that I've modified my local tramp to remove the -p, I find that
> though nc -l 51257 does not give any errors, it isn't actually listening
> on the port either. I'm not sure what it is doing.
As said in my other message to Andreas, busybox might not be compiled
with the nc listening feature.
Anyway, I've committed a patch which allows you to overwrite the "nc -l
..." arguments. Tramp's manual says
--8<---------------cut here---------------start------------->8---
The ‘nc’ command will be used with the ‘nc’ method. On the remote
host, a listener will be installed. Unfortunately, the command
line syntax for this has been changed with the different ‘busybox’
versions. TRAMP uses the following syntax (see ‘tramp-methods’):
# nc -l -p 42
If your remote ‘nc’ refuses to accept the ‘-p’ parameter, you could
overwrite the syntax with the following form:
(add-to-list
'tramp-connection-properties
`(,(regexp-quote "192.168.0.1") "remote-copy-args" (("-l") ("%r"))))
with ‘192.168.0.1’ being the IP address of your remote host (*note
Predefined connection information::).
--8<---------------cut here---------------end--------------->8---
Best regards, Michael.
prev parent reply other threads:[~2014-08-07 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 16:01 bug#18199: 24.4.50; tramp uses wrong arguments to nc Jason Rumney
2014-08-06 7:43 ` Michael Albinus
2014-08-06 8:18 ` Andreas Schwab
2014-08-06 9:35 ` Michael Albinus
2014-08-06 15:36 ` Jason Rumney
2014-08-07 9:27 ` Michael Albinus [this message]
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=87mwbgvedb.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=18199@debbugs.gnu.org \
--cc=jasonr@gnu.org \
--cc=schwab@suse.de \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.