I have been using these scripts happily but I discovered a problem with
them. If the system is shut down then
although /etc/network/if-down.d/cupsys-client gets executed, it has no
effect and the currently enabled printers are left enabled.
The reason is that /etc/network/if-down.d/cupsys-client which gets run
by ifdown which gets run by /etc/rc0.d/S35networking, gets run after
cupsys has been shut down at /etc/rc0.d/K20cupsys.
A solution to this would be for /etc/rc0.d/K20cupsys to disable all
printers on shutdown. A more refined solution would be for it to
disable all printers listed in /etc/network/interfaces on
"cups-printers" lines belonging to logical interfaces listed
in /etc/network/run/ifstate. However the latter seems ugly.
(In the longer term, cupsys shouldn't be storing state information
in /etc/cups/printers.conf. /etc is for configuration files and in
principle should not be changed at run time, whereas cupsenable and
cupsdisable are commands that are reasonably executed at run time.
("run time" here means anytime except when the system administrator is
configuring the system.) If the printer state record were kept in a
volatile file such as /dev/shm/cupsys/printers/<name> and if the absence
of the file were interpreted as "disabled" or "unknown" then rebooting
would automatically clear the state record to the appropriate value.
However, this is the topic of another bug report.)
--
Thomas Hood <[EMAIL PROTECTED]>
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
