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

Bug#399911: marked as done (cupsys: Prefer a debconf question to enable remote administration)

Your message dated Mon, 11 Oct 2010 08:21:17 +0200
with message-id <20101011062117.GB2464@piware.de>
and subject line Re: [Pkg-cups-devel] Bug#399911: Still need to use lynx to enable remote administration
has caused the Debian Bug report #399911,
regarding cupsys: Prefer a debconf question to enable remote administration
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.)


-- 
399911: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=399911
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: cupsys
Version: 1.2.5-1
Severity: normal

I'm installing CUPS on a print server for a LAN.  I want to be able to 
administer the CUPS setup and submit print jobs from anywhere on the 
LAN.  Initially, CUPS is configured to allow access only from localhost.

There are two ways to enable remote administration: you can do it via 
the web interface, or by editting cupsd.conf manually.  In my case the 
server on which CUPS is running is a Linksys NSLU2, which is not able to 
run a conventional web browser.  It is not unusual for print servers to 
be stripped-down machines without X installed. I was eventually able to 
access the web interface by installing lynx, but this was a rather 
painful process.  Not quite as painful as manual editting would have 
been though...

I therefore suggest that debconf would be the better way of selecting 
whether CUPS is accessible from other machines.

I'd also suggest that the options are extended from two to three:
- localhost only
- any address
- LAN IP range, e.g. 192.168.* (new)

An alternative would be to put a suitable cupsd.conf file in the 
documentation examples directory.

I'm submitting this bug because, in most respects, CUPS is a 
user-friendly application.  This is an exception.

Phil.

--- End Message ---
--- Begin Message --- 
Hello Phil,

we won't add debconf for this, so I'm closing this. 

On a desktop you can easily do that on the cups web ui or
system-config-printer, on a server you can connect remotely to it via
web ui or s-c-p, or you can use "cupsctl --remote-admin".

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

--- End Message ---
Reply to: