unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: gebser@speakeasy.net
Subject: Re: Editing a file as root
Date: Wed, 17 Dec 2003 08:19:53 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44.0312170811130.23118-100000@www> (raw)
In-Reply-To: <m2k74vkb9o.fsf@sage.com>


At 11:07 (UTC+0100) on Wed, 17 Dec 2003 Sébastien Kirche said:

= gebser@speakeasy.net writes:
= 
= > Yes, this is what I was asking.  I just wanted to make sure that the 
= > problem wasn't with the server.  For example, servers are often set up 
= > to disallow remote logins to the root account.  (From a security 
= > standpoint, this is a very good idea.)
= 
= Well the "server" is actually the same local machine. So I guess that
= even if remote login is disabled (not sure it is) it should not
= interfere with local login from within emacs. 
= Or do i misunderstood and the /su::/some/path acts as a rlogin even on
= local system ?
= 
= ...

I guess the local/remote paradigm can be confusing in this case, so we
should speak in terms of client/server.  So, yes, if the server is
configured to disallow root logins, then you won't be able to log in as
root, even if the client and server are one the same physical machine.  
So check out the server configuration to see if this is the case.  And
as said before, the definition of the prompt string might be the problem
also.


hth,
ken

  reply	other threads:[~2003-12-17 13:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.97.1071509004.868.help-gnu-emacs@gnu.org>
2003-12-17 10:07 ` Editing a file as root  Sébastien Kirche
2003-12-17 13:19   ` gebser [this message]
2003-12-17 18:08   ` Kai Grossjohann
     [not found] <mailman.83.1071495859.868.help-gnu-emacs@gnu.org>
2003-12-15 13:15 `  Sébastien Kirche
2003-12-15 16:17   ` gebser
2003-12-17 18:06   ` Kai Grossjohann
     [not found] <E1AT5y2-0002EZ-OF@monty-python.gnu.org>
2003-12-14 18:54 ` bhiker
     [not found] ` <mailman.62.1071431778.868.help-gnu-emacs@gnu.org>
2003-12-14 21:09   ` Dan Anderson
2003-12-14 21:25     ` David Kastrup
2003-12-15  0:12       ` Micha Feigin
     [not found]       ` <mailman.65.1071450890.868.help-gnu-emacs@gnu.org>
2003-12-15  0:50         ` David Kastrup
2003-12-15 17:22           ` Micha Feigin
     [not found]           ` <mailman.105.1071513681.868.help-gnu-emacs@gnu.org>
2003-12-15 21:57             ` Benjamin Rutt
2003-12-16 12:41               ` Micha Feigin
     [not found]               ` <mailman.136.1071582719.868.help-gnu-emacs@gnu.org>
2003-12-16 15:36                 ` Benjamin Rutt
2003-12-17 18:01             ` Kai Grossjohann
2003-12-15 10:47       `  Sébastien Kirche
2003-12-15 12:40         ` gebser
2003-12-17 15:51         ` Piet van Oostrum
2003-12-17 18:04         ` Kai Grossjohann
2003-12-18 17:28           ` Kevin Rodgers
2003-12-18 18:28             ` Kai Grossjohann
2003-12-19 11:16               ` Piet van Oostrum
2003-12-21 13:52                 ` Kai Grossjohann
2003-12-15 18:39   ` kgold

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=Pine.LNX.4.44.0312170811130.23118-100000@www \
    --to=gebser@speakeasy.net \
    /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).