Bug#3290: acknowledged by developer (was: sysvinit path doesn't include /usr/local/{,s}bin)
You (Bill Mitchell) wrote:
> On Sat, 15 Jun 1996, Miquel van Smoorenburg wrote:
>
> >If you really want to set an environment or ulimits or whatever for
> >everything that is spawned by init use "initscript" - see man
> >initscript(8). It does everything you're talking about.
>
> My system is probably not up to date, so I'm not casting this as
> a bug report against sysvinit. I have sysvinit-2.60-1 installed,
> and I can't currently get on master or ftp.debian.org to check
> if I'm current. tsx-11 doesn't seem to have a sysvinit package
> in pub/linux/distributions/debian/unstable/binary.
>
> I have no initscript(8) man page. I do have an initscript(5)
> man page which says, in part:
Okay, that's what I meant. Sorry.
> DESCRIPTION
> When the shell script /etc/initscript is present, init
> will use it to execute the commands from inittab. This
> script can be used to set things like ulimit and umask
> default values for every process.
>
> If initscript is an executable shell script, shouldn't it go in /sbin?
Hmmm. I don't think so, it is more a configuration file than a
shell script. Like the scripts in /etc/init.d/. However if these
scripts would be "static" and got their configuration from a
file in /etc (what I would prefer) there is something to be said
to move them into /sbin. But it would break a lot of existing
systems and would make upgrades very difficult.
Mike.
--
Miquel van | Cistron Internet Services -- Alphen aan den Rijn.
Smoorenburg, | mailto:info@cistron.nl http://www.cistron.nl/
miquels@het.net | Tel: +31-172-419445 (Voice) 430979 (Fax) 442580 (Data)
Reply to: