On Fri, Sep 03, 2004 at 09:31:43AM -0700, Collins, Kevin (KCollins) alleged: > More than likely, the terminal window will be missing things like > aliases that are evaluated in a "login", which happens with telnet. Most > X-terminal apps support a "-ls" (login shell) option that causes them to > source the whole environment as if a login were occurring. If that is happening, then the environment is arguable misconfigured. Only exportable items (environmental variables) should be configured on login. All non-exportable items (function definitions, aliases, shell opts, etc), should be configred in your profile so that all new shells are configured correctly. When non-exportable items are in your login scripts, then subshells can't pick these up. > -----Original Message----- > From: taroon-list-bounces redhat com > [mailto:taroon-list-bounces redhat com] On Behalf Of SATISH RAMANATHAN > Sent: Friday, September 03, 2004 9:24 AM > To: taroon-list redhat com > Subject: differences between telnet and terminal window > > > Hi, > > This might be a silly question, but how are environments of > * a telnet session i.e. a remote login session created by running > "telnet > <machine-name>" and > * a terminal window i.e. obtained by right clicking on the desktop > console > and choosing "New Terminal" > different? Aren't they supposed to be similar? I am looking at > differences > in behavior of my application depending on which mode is used for login. -- Garrick Staples, Linux/HPCC Administrator University of Southern California
Attachment:
pgp00000.pgp
Description: PGP signature