Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15537 > unrolled thread
| Started by | "Dr. Werner Fink" <werner@suse.de> |
|---|---|
| First post | 2019-10-28 17:33 +0100 |
| Last post | 2019-10-28 17:33 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [bug-bash] Unexpected sourcing of ~/.bashrc under ssh "Dr. Werner Fink" <werner@suse.de> - 2019-10-28 17:33 +0100
| From | "Dr. Werner Fink" <werner@suse.de> |
|---|---|
| Date | 2019-10-28 17:33 +0100 |
| Subject | Re: [bug-bash] Unexpected sourcing of ~/.bashrc under ssh |
| Message-ID | <mailman.10.1572280428.2428.bug-bash@gnu.org> |
[Multipart message — attachments visible in raw view] — view raw
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
Back to top | Article view | gnu.bash.bug
csiph-web