Re: [bug-bash] Unexpected sourcing of ~/.bashrc under ssh

[Dr. Werner Fink]

On 2019/10/24 10:47:52 -0400, Greg Wooledge wrote:
> On Thu, Oct 24, 2019 at 09:01:07AM +0200, Francis.Montagnac@inria.fr wrote:
> >   When logged on a machine with ssh, executing a simple command CMD1
> >   that spawn a "/bin/bash -c some other command" do not source
> >   ~/.bashrc: normal behaviour.
> > 
> >   When executing "CMD1 | CMD2", the ~/.bashrc is sourced: wrong  .
> 
> Bash can be built with a compile-time option that causes it to try to
> detect when it's the non-interactive child of an ssh session, and source
> the user's ~/.bashrc under those conditions.
> 
> Many Linux distributions enable this option, because they believe that
> their users expect this behavior.

That is what bugzilla had told the last few years here, most users and customers
expect that their bash bahaves (non-)interactive local and remote the same way

-- 
  "Having a smoking section in a restaurant is like having
          a peeing section in a swimming pool." -- Edward Burr

signature.asc
Description: PGP signature