Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15535 > unrolled thread
| Started by | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| First post | 2019-10-24 10:47 -0400 |
| Last post | 2019-10-24 10:47 -0400 |
| 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: Unexpected sourcing of ~/.bashrc under ssh Greg Wooledge <wooledg@eeg.ccf.org> - 2019-10-24 10:47 -0400
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Date | 2019-10-24 10:47 -0400 |
| Subject | Re: Unexpected sourcing of ~/.bashrc under ssh |
| Message-ID | <mailman.1664.1571928511.9715.bug-bash@gnu.org> |
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.
Back to top | Article view | gnu.bash.bug
csiph-web