Thanks for the advice!
However, when I modified the inittab line as shown here:
SV:123456:respawn:/usr/bin/env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin
svscan /service </dev/null >/dev/console 2>/dev/console
nothing changed and I got the exact same continuous error.
Also, as you can see from the original post lines below, when I type in the below from
the console:
env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service </dev/null
>/dev/console 2>/dev/console
which works perfectly, it would seem that the "env" command is readily found by the
shell.
It's possible I may be misunderstanding something here, but I don't think this solves
the problem from my tests.
Thanks,
Jack D. Browning
[EMAIL PROTECTED]
=========================
>> [snip]
>>However, when I enter the single line from section 2.7 of Life with qmail at the
>bottom of "/etc/inittab":
>> SV:123456:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan
>/service </dev/null >/dev/console 2>/dev/console
>>I get the following continuous error at boot or at "kill -HUP 1":
>> /var/qmail/rc: exec: env: not found
>>
>>When I type in the same line from the console, starting with "env - PATH=/usr...."
>it works fine.
>> [snip]
=========================
>> On Sun, Aug 26, 2001 at 07:49:39PM -0400, Jack D . Browning wrote:
>> [snip]
>> > I get the following continuous error at boot or at "kill -HUP 1":
>> > /var/qmail/rc: exec: env: not found
>> [snip]
>> It is in front of you.... ''env'' is a program and the shell command
>> ''exec'' cannot find it. Try the full path to ''env'' which you can find
>> with the shell command ''which''.
>> J�rgen
