Hello Chris On Sat, 2015-06-13 at 11:49 +1000, Chris Samuel wrote:
On Fri, 12 Jun 2015 07:59:01 PM Mark Trickett wrote:
There were comments about Arch having a blog with useful comments. It specified commands for systemd components that I could not find under Debian. I would appreciate some pointers to stopping services, and restarting. There are files that if I am to edit, I need to stop CUPS for the duration, then restart to test.
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. I will be looking closely at Devuan.
/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 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. 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. 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.
Best of luck! Chris
Regards, Mark Trickett