ERRATA : interactive and login shells: bug or design decision ?
From: Cristian Zoicas (zoicas_at_ictp.trieste.it)
Date: 03/24/05
- Previous message: Greg Wooledge: "Re: interactive and login shells: bug or design decision ?"
- Next in thread: Greg Wooledge: "Re: ERRATA : interactive and login shells: bug or design decision ?"
- Reply: Greg Wooledge: "Re: ERRATA : interactive and login shells: bug or design decision ?"
- Reply: Robert Hajime Lanning: "Re: ERRATA : interactive and login shells: bug or design decision ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 24 Mar 2005 14:44:42 +0100 To: secureshell@securityfocus.com
Hello all
It seems that I have to correct my post on this mailing list.
When I execute: <ssh user@somesite.com>, I get a login shell, but
when I execute: <ssh user@somesite.com command>, command does not run
under a login shell.
Of course I do not expect the shell started in the second command to be an
interactive one, but I am expecting my command to run under a login shell.
The ssh version that I use is OpenSSH_3.6.1p2
The question is the same: Is this behaviour a bug or a design decision ?
If it is a design decision, then what are the reasons to have it like this.
Thx again
Z. Cristian
- Previous message: Greg Wooledge: "Re: interactive and login shells: bug or design decision ?"
- Next in thread: Greg Wooledge: "Re: ERRATA : interactive and login shells: bug or design decision ?"
- Reply: Greg Wooledge: "Re: ERRATA : interactive and login shells: bug or design decision ?"
- Reply: Robert Hajime Lanning: "Re: ERRATA : interactive and login shells: bug or design decision ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|