From: Michael Albinus <michael.albinus@gmx.de>
To: joakim@verona.se
Cc: 14142@debbugs.gnu.org
Subject: bug#14142: 24.3.50; documentation bug in TRAMP
Date: Fri, 05 Apr 2013 11:02:20 +0200 [thread overview]
Message-ID: <87r4ip2vvn.fsf@gmx.de> (raw)
In-Reply-To: <m34nflh1j0.fsf@chopper.vpn.verona.se> (joakim@verona.se's message of "Fri, 05 Apr 2013 09:36:35 +0200")
joakim@verona.se writes:
Hi Joakim,
> There is a possible documentation bug in TRAMP.
>
> The TRAMP docs say:
>
> ,----
> | Opening `/sudo:randomhost.your.domain:' would connect first
> | `randomhost.your.domain' via `ssh' under your account name, and perform
> | `sudo -u root' on that host afterwards. It is important to know that
> | the given method is applied on the host which has been reached so far.
> | `sudo -u root', applied on your local host, wouldn't be useful here.
> `----
You should quote the whole documentation about:
,----
| If you, for example, wants to work as 'root' on hosts in the domain
| 'your.domain', but login as 'root' is disabled for non-local
| access, you might add the following rule:
|
| (add-to-list 'tramp-default-proxies-alist
| '("\\.your\\.domain\\'" "\\`root\\'" "/ssh:%h:"))
|
| Opening '/sudo:randomhost.your.domain:' would connect first
| 'randomhost.your.domain' via 'ssh' under your account name, and
| perform 'sudo -u root' on that host afterwards. It is important to
| know that the given method is applied on the host which has been
| reached so far. 'sudo -u root', applied on your local host,
| wouldn't be useful here.
`----
I'll mark it as not-a-bug.
Best regards, Michael.
prev parent reply other threads:[~2013-04-05 9:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 7:36 bug#14142: 24.3.50; documentation bug in TRAMP joakim
2013-04-05 7:44 ` Thierry Volpiatto
2013-04-05 9:02 ` 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r4ip2vvn.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=14142@debbugs.gnu.org \
--cc=joakim@verona.se \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).