Re: [gentoo-amd64] Re: cupsd wont start on boot.

[Neil Stone]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul de Vrieze wrote:
> On Saturday 05 August 2006 07:50, Duncan wrote:
>> If it's the exact same line both places, one works, the other doesn't,
>> it's almost certainly due to the difference in environment.  The
>> environment passed to the one started from initscript will be rather more
>> limited than a fully interactive bash prompt environment.
>>
>> I'd suggest you put a debug statement in the initscript, right before the
>> command executes, that prints the environment to one file and the exported
>> environment to another.  Diff those against the same output from the
>> command line that works right, and you'll have a good start on tracking
>> down the culprit, since you'll have all the differences nicely listed, in
>> ordered to check.
>
> Additionally many init scripts use start-stop-daemon with the --quiet command
> line option. This suppresses all output from the command used. In this case
> we would like to see this output so remove "--quiet" from the init script.
>
> Paul
>

what happens if you invoke the init script directly, ie not running the
commands contained within the script...

/etc/init.d/cupsd start

for example

- --
Neil Stone

Systems Administrator
FlashTek UK

- -----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d+(++) s: a-(?) C++++(--) UL++++$ P+ L+++ E- W+++ N+
o+ w--- O M PS+ Y+ PGP++ t+ 5+ X+ R+ tv+ b- DI++ D+++ G
e h--- r+++ y++++(**)
- -----END GEEK CODE BLOCK-----
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE1mn1z3Av8JKgzxQRAmxZAKCVMrcPvKCeFdG3UaCrbNZuS97aDACgsZmt
SeSCaw8XjSJX/xfs3N7TQV8=
=lI9m
-----END PGP SIGNATURE-----
-- 
gentoo-amd64@g.o mailing list