Re: Need help with CUPS printing
On Sunday 29 March 2015 12:58:11 Brian wrote:
> On Sun 29 Mar 2015 at 10:57:37 -0400, Gene Heskett wrote:
> > I am getting the impression that the overall install on both doesn't
> > have the correct Browsing options set, from this machine which
> > serves all
>
> That could be a possibility, although the OP did say
>
> > After installing the most recent upgrades to Jessie on both
> > computers this morning, I tried to print a few pages from
> > iceweasel and printing worked.
I missed that, it was a long post & my short term memory is poor. :(
>
> His problem appears to be getting Emacs to communicate with the
> printing system rather than the system itself.
>
> > available printers to the rest of the machines on my local network
> > (I am behind a router running dd.wrt so its pretty wide open here,
> > with all addresses set in host files at an not well used class c
> > address in the 192.168 class B block. security by obscurity and NAT
> > rules in the router).
> >
> > The Browsing section of the cupsd.conf of this machine:
> > (comments excised for some reason unk to me)
>
> I'll add some then :).
>
> > LogLevel warn
>
> Ok.
>
> > SystemGroup lpadmin root gene
> > Group sys gene
> > User lp gene
>
> These directives should be in /etc/cups/cups-files.
I was just making sure I could kill a job gone wild without having to
become root on a rootless system to do it. My color laser would have
wasted 40 sheets of paper while I was gaining access rights.
> root doesn't need to be in SystemGroup. There might be a good reason
> for the presence of group gene but I cannot think of one.
Root was inherited from a previous config, and gene is the operative that
lets me do admin stuff. It is my machine. :) Thats also why I appended
the network/security part of my msg. Its terrible practice if the
machine is connected directly to the modem.
> The default for Group and User on Debian is lp. gene and sys seem to
> be superfluous.
Probably.
>
> > Port 631
>
> Needed if you want to allow remote access.
>
> > Listen /var/run/cups/cups.sock
>
> Fine.
>
> > Browsing On
> > BrowseOrder allow,deny
> > BrowseAllow all
> > BrowseRemoteProtocols CUPS
> > BrowseAddress @LOCAL
> > BrowseLocalProtocols CUPS dnssd
>
> This is almost the standard Wheezy,
Correct, the install here is not exactly wheezy, but is based on it.
> It will not suffice on Jessie. The
> BrowseOrder, BrowseAllow, BrowseAddress and BrowseRemoteProtocols
> directives are no longer part of cups. cups also know nothing about
> 'CUPS'.
Gah, Mike's been playing again, or someone at debian. What was wrong
with the way it did work?
As for Mike, I've known him since he was DodgeColt on Delphi.
> [Some lines relevant to the topic snipped]
>
> > One of my printers has an ethernet port and is a bit faster if I use
> > it, hence the dnssd addition in the Protocols.
>
> dnssd and ethernet ports are unrelated.
The dnssd showed up sometime after I'd set the printer up at a local
ethernet address, I didn't make a conscious effort to add it. Bad
assumption on my part?
>
> > The critical section to check would seem to be the "Browsing..."
> > By default, this is not enabled but "Off", and you also need to
> > check
>
> Browsing is 'on' by default on Jessie.
Excellent. If and when I ever get to Jessie. I am somewhat constrained
by at least keeping the sim modes of LinuxCNC working here.
> [Many lines irrelevant to the topic snipped]
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Reply to: