Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15535
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Unexpected sourcing of ~/.bashrc under ssh |
| Date | 2019-10-24 10:47 -0400 |
| Message-ID | <mailman.1664.1571928511.9715.bug-bash@gnu.org> (permalink) |
| References | <27440.1571900467@kermit.inria.fr> <20191024144752.GF1408@eeg.ccf.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 gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: Unexpected sourcing of ~/.bashrc under ssh Greg Wooledge <wooledg@eeg.ccf.org> - 2019-10-24 10:47 -0400
csiph-web