Hello Chris, On Sun, 2015-06-14 at 11:11 +1000, Chris Samuel wrote:
On Sat, 13 Jun 2015 08:00:14 PM Mark Trickett wrote:
Hello Chris
Hiya Mark,
On Sat, 2015-06-13 at 11:49 +1000, Chris Samuel wrote:
Yeah, your version of Debian is too old to have systemd as the default and unfortunately I don't have a Debian box with cups running, but I'm guessing it will be something like:
7.8 is reasonably current, and when I look through the system directories, I see systemd.
Wheezy (7.8) is too old for systemd to be the default, it's the default for Debian 8.0 (Jessie), I forgot to put the version numbers in, sorry.
Certainly bits and pieces, will have to take a closer look.
I will be looking closely at Devuan.
I'm not running a Debian new enough for systemd, but under Ubuntu it's only made things better. Before I would get random (but often) times when my system wouldn't boot because of weird race conditions between software raid, LVM and init trying to fsck volumes before they were ready and so aborting saying it couldn't fsck something that didn't exist. Of course when I tried manually it would work. :-(
That problem has gone away since going to 15.04 and systemd so I, for one, welcome our new systemd overlords. :-)
systemd has some excellent promises, but I do not want the one monolithic item that has too much under its purview. There are problems with the old style init, and it can get quite complicated, but it is documented and stable, or very largely so. I do not leave my PC's running for more than the hours to do things, but I do not find the boot times unreasonable even without systemd.
/etc/init.d/cups stop
Do the editing you need, then:
/etc/init.d/cups start
That is what I was expecting with the traditional init, but seeing the systemd bootprint, I am being careful.
I think some packages provide systemd files by default, but that doesn't mean you're running systemd. To see if you are what does "systemctl" say?
Will be looking.
I have just picked up some Linux magazines, and found one tool I was looking for, "lsof" and will be carefully reading up the man pages.
lsof will list open files and sockets. If you just want to look for open TCP connections then you can do (as root):
netstat -ntp
Just drop the -n option if you want to see symbolic names for hosts and services:
netstat -tp
With the error message about a broken pipe, I suspect I will be looking for a handoff failure within the CUPS chain of processes.
I have also found other reference to needing to add the lpadmin group to whichever user is trying to administer CUPS. That not being default is the wrong way round in my opinion, especially with the way that there is no pointer to the problem or solution when running up against not being able to install a printer.
The Debian docs for printing say to do that if you get a permissions error:
https://wiki.debian.org/SystemPrinting
so perhaps there are situation where that's not neccessary? I'm not sure as Ubuntu does that by default.
Certainly it should be a default to make things less confusing for newbies. As I commented, I was able to put things together and go hunting around and find the requirement for myself, but I did a course in Unix while using CP/M before being introduced to DOS.
When I find my way around, I shall comment. I know of at least one other case where someone has succeeded, with an earlier release of the CAPT driver, on a netbook. There are two elements that changed, along with a different distro. I am still trying to get my head around the chain of workflow in CUPS, and where the bits are configured. There is a lot of good documentation, but I can see a need for slightly above raw novice primerson some of the networking and how CUPS actually works.
In addition to the Debian CUPS page the Arch Linux wiki also has some more detailed documentation on setting up CUPS:
CUPS is installed, apparently successfully, and the drivers also installed, and I can select the appropriate printer that has been detected, just the broken pipe for the network connection, and sits there saying writing data to printer or some such for USB. Since I suspect the broken pipe is all in the CUPS process on the one PC, then lsof would appear to be an appropriate tool.
Best of luck! Chris
Going to need, lost too much of today to broken back window on the VW Transporter I drive, something flung when trying to get into clearing with the brushcutter. Have taken out the majority of the glass, left the glued edge for the moment and taped a large piece of bubble wrap over the open hole to keep out the exhaust fumes and worst of the weather. Regards, Mark Trickett