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. > 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. :-) > > /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? > 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 > 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. > 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: https://wiki.archlinux.org/index.php/CUPS Best of luck! Chris -- Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC _______________________________________________ luv-main mailing list [email protected] http://lists.luv.asn.au/listinfo/luv-main
