Bug#3290 acknowledged by developer (was: sysvinit path doesn't include /usr/local/{,s}bin)
Raul Miller
> > > /etc/init.d/boot sets up a path that doesn't include /usr/local/bin
> > > nor /usr/local/sbin. In my opinion, the PATH= from /etc/profile
> > > (supplied by the bash package) should be used here as well. It's
> > > rather silly to have two different default paths for root.
Dominik Kubla:
> > No it is not. It is the basic law of system administration that during
> > system setup the PATH should be as short as possible and only include
> > _MACHINE_LOCAL_ path names (/usr/local might be shared over NFS!).
Miquel van Smoorenburg:
> OK, so I'm closing this bug report.
I think there's a very big opportunity here that's being missed.
We have a large problem of configuring the default path for shells
and such that don't use /etc/profile. It's fine to have a restricted
path during boot, but this path setting persists long after boot, and
is inherited by everything that init inherits.
Here's another suggestion: include an action 'environment'. This is
a process that would be run when entering a run level, and would be
run before any other actions at that runlevel. It will be exec'd by
process 1, rather like the sysinit entry.
Yes, this introduces more possibilities to shoot yourself in the foot,
but init's already that way.
--
Raul
Reply to: