[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#204847: marked as done (cupsys-client: ifupdown hook scripts allow convenient (en|dis)abling of print queues)

Your message dated Fri, 10 Jul 2015 17:00:58 +0100
with message-id <10072015165608.de506826c1c5@desktop.copernicus.demon.co.uk>
and subject line Re: Bug#204847: cupsys-client: ifupdown hook scripts allow convenient (en|dis)abling of print queues
has caused the Debian Bug report #204847,
regarding cupsys-client: ifupdown hook scripts allow convenient (en|dis)abling of print queues
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
204847: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=204847
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cupsys-client
Version: 1.1.19final-1
Severity: wishlist
Tags: patch

Here follow two very simple scripts that are designed to be placed in
/etc/network/if-up.d/ and /etc/network/if-down.d/ .  When present, these
scripts cause the printer queues named on a "cups-printers" line in an
iface stanza in /etc/network/interfaces to be enabled after the relevant
interface is ifupped and disabled before the relevant iface is ifdowned.
(The print queues must of course be created and configured first using
standard cups tools.)  This feature makes life easier for roaming users,
for they can list the print queues available at a location in the iface
stanza appropriate to that location and those print queues will be
automatically enabled and disabled at the right time.  When a print job
is sent to a _class_, CUPS is smart enought to choose a printer from
the class that is currently enabled; so, by creating a "default" class
whose members are all the default printers he wants to use at different
locations and setting it as his default print queue, the roaming user
can always print to his local default print queue without having to
reconfigure anything by hand.

/etc/network/if-up.d/cupsys-client
=---------------------------------
#!/bin/sh
[ -x /usr/bin/cupsenable ] || exit 0
[ -x /usr/bin/cupsdisable ] || exit 0
/usr/bin/cupsenable $IF_CUPS_PRINTERS
=---------------------------------

/etc/network/if-down.d/cupsys-client
=-----------------------------------
#!/bin/sh
[ -x /usr/bin/cupsdisable ] || exit 0
/usr/bin/cupsdisable $IF_CUPS_PRINTERS
=-----------------------------------

(I have chosen the keyword 'cups-printers' with care: it is the name of
the service followed by a hyphen followed by the parameter being set.
This follows the example set by wireless-tools and other packages.)

Please contact me if you have any questions about how this is supposed
to work.

--
Thomas Hood

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux thanatos 2.4.21 #4 Fri Aug 8 21:47:58 CEST 2003 i686
Locale: LANG=en_IE@euro, LC_CTYPE=en_IE@euro

Versions of packages cupsys-client depends on:
ii  libc6                      2.3.1-16      GNU C Library: Shared libraries an
ii  libcupsys2                 1.1.19final-1 Common UNIX Printing System(tm) - 
ii  zlib1g                     1:1.1.4-1     compression library - runtime

-- no debconf information

--- End Message ---
--- Begin Message --- 
I think the cups maintainer has said all there is to say on how these
scripts fit into the framework of today's much-altered CUPS.

Regards,

Brian.

--- End Message ---
Reply to: