Re: Re[2]: ~/.bashrc not sourced for ssh commands on Archlinux

[Pierre Gaston]

On Wed, Apr 24, 2013 at 9:15 AM, Ilya Basin <basinilya@gmail.com> wrote:

> **
>
> >
>
>
>
>
>
>
> On Wed, Apr 24, 2013 at 7:31 AM, Ilya Basin <basinilya@gmail.com> wrote:
>
>
> Hi.
>
>
>     $ cat ~/.bashrc
>
>     #
>
>     # ~/.bashrc
>
>     #
>
>     echo Im in .bashrc >&2
>
>
> RHEL 6.0, bash 4.1.2
>
>     $ ssh localhost 'ps -f $$ && true'
>
>     Im in .bashrc
>
>     UID        PID  PPID  C STIME TTY      STAT   TIME CMD
>
>     git      22295 22294  0 08:29 ?        Ss     0:00 bash -c ps -f $$ &&
> true
>
>
> Archlinux, bash 4.2.42
>
>     $ ssh localhost 'ps -f $$ && true'
>
>     UID        PID  PPID  C STIME TTY      STAT   TIME CMD
>
>     il       26539 26538  0 08:26 ?        Ss     0:00 bash -c ps -f $$ &&
> true
>
>
>
> What can couse this? Manpage says: "Bash attempts to determine when it
>
> is being run with its standard input connected to a network
>
> connection". Is the detection broken?
>
>
>
> With newer sshd stdin is not connected to a socket.
>
> There is a compile time option to cause bash to check for the
> SSH_CLIENT[2] environment variables but it seems arch doesn't enable it for
> its build.
>
>
> Socket? How could it ever be connected to a socket, if the data has to be
> decrypted first?
>
Ask openssh?
A socket is not necessarily a bad choice for 2 processes to communicate.