Re: telnet logins
From: Barry Margolin (barmar_at_alum.mit.edu)
Date: 01/12/05
- Next message: Deke: "Disksuite Volme Manager"
- Previous message: Dave Uhring: "Re: The man knows how to get publicity ..."
- In reply to: Randy: "Re: telnet logins"
- Next in thread: Randy: "Re: telnet logins"
- Reply: Randy: "Re: telnet logins"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 12 Jan 2005 01:43:22 -0500
In article <1105464688.326502.161380@c13g2000cwb.googlegroups.com>,
"Randy" <yates@ieee.org> wrote:
> > Randy <y...@ieee.org> wrote:
> > > Is it conventional to exclude the x-client directory (on my system
> its
> > > /usr/openwin/bin) from the path when logging in over a telnet
> session?
> >
> > *exclude*, no. However it's pretty common to not have it in the
> default
> > path, but add it when logging in via a graphical interface, or when
> > starting X windows.
>
> Semantics. Are we "excluding" or "choosing not to add"?
There's usually a separate initialization file for X logins, e.g.
.xinitrc, as well as various system scripts that are run by XDM or
startx. These X-specific scripts typically add the directories
containing GUI applications.
When you do a text login, you never execute these scripts, so none of
the X stuff is added to your path. It's not just telnet logins that are
affected by this. If you use the option to get a plain console login,
you also won't have these scripts executed.
-- Barry Margolin, barmar@alum.mit.edu Arlington, MA *** PLEASE post questions in newsgroups, not directly to me ***
- Next message: Deke: "Disksuite Volme Manager"
- Previous message: Dave Uhring: "Re: The man knows how to get publicity ..."
- In reply to: Randy: "Re: telnet logins"
- Next in thread: Randy: "Re: telnet logins"
- Reply: Randy: "Re: telnet logins"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|