Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #16111
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: First lines of examples/startup-files/bashrc |
| Date | 2020-04-09 08:27 -0400 |
| Message-ID | <mailman.402.1586435266.2644.bug-bash@gnu.org> (permalink) |
| References | <20200408234241.84fa2643163cc7ec3aedc6ef@schrader-schulte.de> <CAOSMAuvsyHZ18kM6RaDfoCVynprvTkEbgtHsi9EX1JXcxs9rPg@mail.gmail.com> <20200409122714.GZ845@eeg.ccf.org> |
On Wed, Apr 08, 2020 at 04:46:19PM -0700, Eduardo Bustamante wrote: > On Wed, Apr 8, 2020 at 2:42 PM Martin Schulte <gnu@schrader-schulte.de> wrote: > (...) > > But, as far as I understand, a non-interactive bash doesn't read > > ~/.bashrc at all - so shouldn't we just omit them? > > There are exceptions. One of them being SSH, see: > https://git.savannah.gnu.org/cgit/bash.git/tree/shell.c?h=ea31c00845c858098d232bd014bf27b5a63a668b#n1095 > > > /* If we were run by sshd or we think we were run by rshd, execute > > ~/.bashrc if we are a top-level shell. */ Another case would be someone setting BASH_ENV to force the file to be dotted in by scripts. Or, possibly, someone who drank the Oracle Kool-Aid and is using su - someuser -c 'some command' to run stuff. Which we all know is utterly and completely terrible, and yet... people do it.
Back to gnu.bash.bug | Previous | Next | Find similar
Re: First lines of examples/startup-files/bashrc Greg Wooledge <wooledg@eeg.ccf.org> - 2020-04-09 08:27 -0400
csiph-web