Re: does /etc/profile get sourced also when .profile exists ?

[Alex fxmbsw7 Ratchev]

so the summary, if, use at most files in ~/
no /etc

ye ?

On Mon, Jul 26, 2021 at 10:00 PM Alex fxmbsw7 Ratchev <fxmbsw7@gmail.com> wrote:
>
> lol systemd , i never liked it
> not sure i think i have it its standard but i used to replace it by
> sysvinit-core
>
> pid 1 says /sbin/init .. looks like sysvinit
> but on the server, not sure ..
>
> On Mon, Jul 26, 2021 at 9:56 PM Jeffrey Walton <noloader@gmail.com> wrote:
> >
> > On Mon, Jul 26, 2021 at 10:10 AM Tim Visher <tim.visher@gmail.com> wrote:
> > >
> > > On Mon, Jul 26, 2021 at 9:57 AM Alex fxmbsw7 Ratchev <fxmbsw7@gmail.com>
> > > wrote:
> > >
> > > The exact set of init/dot files that are sourced when you start a shell
> > > depends on quite a few factors, but I think there are no circumstances 
> > > that
> > > would source `~/.profile` without _first_ sourcing `/etc/profile`, since
> > > `/etc/profile` is always sourced by bash when bash is invoked as a login
> > > shell.
> > >
> > > This is all covered in extensive detail in
> > > https://mywiki.wooledge.org/DotFiles, if you'd like to read up on it.
> >
> > One case to watch out for is Systemd (maybe it was present in SysV,
> > too)... Systemd does not source /etc/profile, even on systems like
> > CentOS.
> >
> > The significance is, Red Hat and CentOS say to setup Software
> > Collections (SCL) in /etc/profile. So you install Apache, Python and
> > PHP from SCL and you enable the updated packages from /etc/profile per
> > the vendor. But Systemd does not follow the vendor's practices. It
> > uses random paths, and uses the wrong version of the software when it
> > executes your scripts.
> >
> > Then, you get to troubleshoot why Duplicity is failing for no apparent 
> > reason...
> >
> > Jeff
> >