[SOLVED] Re: Dependency based boot sequencing and printers

[Rob Hurle <rob1940@gmail.com>]

I found what I was ding wrong:

>>> >  The printer has stopped working!  I'm suspicious of the
>>> > dependency-based sequencing since that was the only upgrade which
>>> > mentioned the printer, but another one of the upgrades may well have
>>> > disturbed the printing system.  Before I start the tedious debugging
>
> I have attempted to use insserv to get the printer daemons running
> after cupsd starts, with no success.  I have set up a file
> /etc/insserv.d.conf/printers:
>
> debianrob:/etc/insserv.conf.d# cat printers
> #RJH
> # Define $printers to be the CUPS daemon  (cupsd)
> # Other printer daemons (at least, the Canon one) must start after
> CUPS is running.
> $printers              cups
>
> The headers for my Canon printer daemon in init.d are:
>
> debianrob:/etc/init.d# head -20 ccpd
> #!/bin/sh
> # startup script for Canon Printer Daemon for CUPS (ccpd)
> # Modified for Debian GNU/Linux
> #RJH 13 May 2012
> ### BEGIN INIT INFO
> # Provides:          ccpd
> # Required-Start:    $remote_fs $syslog $printers
> # Required-Stop:     $remote_fs $syslog
> # Default-Start:     2 3 4 5
> # Default-Stop:      0 1 6
> # Short-Description: Start ccpd at boot time
> # Description:       Enable the Canon Printer Daemon for CUPS
> ### END INIT INFO
> DAEMON=/usr/sbin/ccpd
> LOCKFILE=/var/lock/subsys/ccpd
> NAME=ccpd
> DESC="Canon Printer Daemon for CUPS"
> ...

This was all correct, but, at the end of it all, I needed to do:

insserv ccpd

to register the new script.  I found this on the novell web site where
the manual entry for insserv(8) specifically points this out for slow
learners like me :-)

Cheers,
Rob Hurle
-- 
-----------------------------
Rob Hurle
ANU, College of Asia and the Pacific
School of Culture, History and Language
Histories of Asia and the Pacific
e-mail:              rob1940@gmail.com
Mobile (in VN):  +84 948 243 538
Mobile (in OZ):  +61 417 293 603
-----------------------------