[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#19691: lprng: include a PATH= statement in the init.d script

[You (Sven Rudolph)]
><aj@dungeon.inka.de> writes:
>> Package: lprng
>> Version: 3.4.2-1
>> to make sure /sbin and /usr/sbin is in the PATH
>> (which might not be with some administrate accounts,
>>  that su to root to start the spooler).
>Some /etc/init.d/ scripts (re)set PATH; others don't. I think we need
>a policy decision here.

Hmm.  I kinda agree.  I don't think init scripts should mess with PATH.
Unless they have unique requirements.  I think generally the init scripts 
should assume that path is set correctly.  If there are problems with the 
path being set by init during boot time, that would be a bug on init.  If 
there's problems in a sysadmin not having the right path and running an 
init script, that's an operator error.

As far as the invokation of the actual daemon in question, I think the 
path to the binary or script should be absolute, i.e., /usr/sbin/crond or 

That's my opinion.

.....A. P. Harris...apharris@onShore.com...<URL:http://www.onShore.com/>

To UNSUBSCRIBE, email to debian-policy-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: