From: 2QdxY4RzWzUUiLuE@potatochowder.com
To: help-gnu-emacs@gnu.org
Subject: Re: Tramp prompt (?) issue
Date: Fri, 31 Jul 2020 16:46:22 -0500 [thread overview]
Message-ID: <20200731214622.GA1681@scrozzle> (raw)
In-Reply-To: <871rkrxxsd.fsf@ebih.ebihd>
On 2020-07-31 at 21:57:38 +0200,
Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
> Michael Albinus wrote:
> > What do you see, if you call manually
> >
> > # ssh -l embe8573 -o ControlMaster=auto -o
> > ControlPath='tramp.%C' -o ControlPersist=no -e none
> > polhem.it.uu.se
>
> $ sudo ssh -l embe8573 -o ControlMaster=auto -o ControlPath='tramp.%C' -o ControlPersist=no -e none polhem.it.uu.se
> Password: ***
> Last login: Fri Jul 31 21:48:18 2020 from c-fd84225c.021-
> .Z. ls
I've been half following this thread, because I've also had weird issues
with tramp over the years, but it's been a long time, and I have nothing
new to add on that front.
With that disclaimer out of the way, why are you running ssh under root
and/or sudo, and do you get different results if you don't? Are you
running emacs as root, or under sudo, or as a regular user? I ask
because very often root has an entirely separate set of rules for remote
access, on both client and server, and sudo can add its own permission
and environment related issues.
HTH,
Dan
next prev parent reply other threads:[~2020-07-31 21:46 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 0:22 Tramp prompt (?) issue Emanuel Berg via Users list for the GNU Emacs text editor
2020-07-29 9:22 ` Michael Albinus
2020-07-29 16:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-07-29 18:18 ` Michael Albinus
2020-07-29 20:23 ` Tim Visher
2020-07-29 22:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-07-29 22:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-07-30 9:51 ` Michael Albinus
2020-07-30 11:54 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-07-30 18:18 ` Michael Albinus
2020-07-31 19:57 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-07-31 21:46 ` 2QdxY4RzWzUUiLuE [this message]
2020-07-31 22:20 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-01 9:36 ` Michael Albinus
2020-08-01 9:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-01 10:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-01 18:23 ` Michael Albinus
2020-08-02 17:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-03 9:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-03 14:15 ` Michael Albinus
2020-08-03 16:15 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-03 19:09 ` Michael Albinus
2020-08-03 20:37 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-04 6:59 ` Michael Albinus
2020-08-17 1:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-17 11:28 ` Michael Albinus
2020-08-17 21:51 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-18 8:18 ` tomas
2020-08-18 10:37 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-18 14:06 ` tomas
2020-08-18 16:49 ` Michael Albinus
2020-08-18 17:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-18 17:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-18 17:46 ` Michael Albinus
2020-08-18 8:59 ` Michael Albinus
2020-08-18 17:12 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-18 17:49 ` Michael Albinus
2020-09-03 3:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-03 3:08 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-03 3:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-07 19:43 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-09-12 18:01 ` Michael Albinus
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=20200731214622.GA1681@scrozzle \
--to=2qdxy4rzwzuuilue@potatochowder.com \
--cc=help-gnu-emacs@gnu.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).