More information, this is an Ubuntu 20.04 box, though I don't remember if I installed fresh or updated from 16.04. My /etc/passwd line says /bin/bash. My .bash_profile does *NOT* source .bashrc, but .bash_login does. Including the source .bashrc in .bash_profile fixes it.
Thank you! On Tue, Jun 29, 2021 at 5:40 PM Larry Brigman <larry.brig...@gmail.com> wrote: > > I had something similar on a Centos 7 system and found that my login shell > was /bin/sh. > Even though /bin/sh was linked to bash, it acted more like a Bourne shell > and wasn't acting on my .bashrc or .bash_profile. > > On Tue, Jun 29, 2021 at 3:09 PM Reid <nrw...@protonmail.com> wrote: > > > Does your ~/.bash_profile not source ~/.bashrc? Mine (Fedora) does by > > default but maybe yours is different. > > > > > > https://unix.stackexchange.com/questions/332531/why-does-remote-bash-source-bash-profile-instead-of-bashrc > > > > > > Sent with ProtonMail Secure Email. > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > On Tuesday, June 29, 2021 3:00 PM, Russell Senior < > > russ...@personaltelco.net> wrote: > > > > > I noticed that my attempt to keep my shell history indefinitely was > > > thwarted. My .bashrc has HISTFILESIZE=-1 and HISTSIZE=-1, but when I > > > ssh in to the box and run "echo $HISTFILESIZE " I mysteriously get > > > 500. I don't currently understand why and I have not yet dug into > > > serious research yet. > > > > > > Does anyone happen to know? > > > > > > > > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > > > > > Russell Senior > > > russ...@personaltelco.net > > > > > >
