Bug#36151: REJECTED] /etc/init.d scripts should specify an explicit PATH

2000-06-22 Thread Steve Greenland
On 21-Jun-00, 13:17 (CDT), Julian Gilbey [EMAIL PROTECTED] wrote: Brock Rozen suggested that init.d scripts should have explicit PATH=... settings. No-one commented on the idea. As I recall, there was a lot of discussion...although maybe it occurred in -devel before Brock formally proposed

Bug#36151: REJECTED] /etc/init.d scripts should specify an explicit PATH

2000-06-21 Thread Julian Gilbey
Brock Rozen suggested that init.d scripts should have explicit PATH=... settings. No-one commented on the idea. In general, all programs which make assumptions about PATH containing more that /bin and /usr/bin should probably explicitly set PATH; this problem is not exclusive to /etc/init.d

Bug#36151: REJECTED] /etc/init.d scripts should specify an explicit PATH

2000-06-21 Thread Alexander Koch
On Wed, 21 June 2000 19:17:21 +0100, Julian Gilbey wrote: Brock Rozen suggested that init.d scripts should have explicit PATH=... settings. No-one commented on the idea. I had the problem when once I wrote a script that was calling /etc/init.d/sysklogd which called start-stop-daemon. Now

Bug#36151: REJECTED] /etc/init.d scripts should specify an explicit PATH

2000-06-21 Thread Brock Rozen
I still think that we should put the basics in, according to the original proposal. Nonetheless, if people don't like the proposal then what can I do? ;-) If that's the case, then yeah, it should go into that doco. BR On Wed, 21 Jun 2000 at 19:17, Julian Gilbey wrote about Bug#36151:...:

Bug#36151: REJECTED] /etc/init.d scripts should specify an explicit PATH

2000-06-21 Thread Brock Rozen
On Wed, 21 Jun 2000 at 18:41, Alexander Koch wrote about Re: Bug#36151:...: I do not think this is how it is meant to be, given that /sbin/ is probably not in the typical user PATH setting for a reason. And it is not the default anyway. You're right. But the typical user doesn't run scripts