Re: [DNG] printing (was Re: Readiness notification)

2015-06-16 Thread Arnt Gulbrandsen
If you do any cloud development or deployment, you will meet that requirement again. It happens all the time in distributed cloudy services. For example: you need the ability to look up backends immediately, you need read access to the database PDQ, and you need write access eventually, but tha

Re: [DNG] [Dng] printing (was Re: Readiness notification)

2015-06-16 Thread Klaus Hartnegg
Am 15.06.2015 um 16:35 schrieb Steve Litt: I know that every service has a "provides", that basically gives the service a uniformly agreed upon name. And it has zero to many "requires", which I believe means that the current service (call it A), requires another service (call it B), so it won't s

Re: [DNG] printing (was Re: Readiness notification)

2015-06-16 Thread Rob van der Putten
Hi there Hendrik Boom wrote: Just make sure the package cops-bsd isn't installed. It provides a file /usr/bin/lpr, which is preumably a front end to cups. And cat should be lower-case, obviously. There are plenty of videos illustrating what happens if it isn't. Regards, Rob ___

Re: [DNG] printing (was Re: Readiness notification)

2015-06-16 Thread Hendrik Boom
On Tue, Jun 16, 2015 at 01:17:54PM +0200, Rob van der Putten wrote: > > Cat Some_File.ps | lpr (bypassing CUPS) should work. If not, it's > not a postscript printer. Just make sure the package cops-bsd isn't installed. It provides a file /usr/bin/lpr, which is preumably a front end to cups. A

Re: [DNG] printing (was Re: Readiness notification)

2015-06-16 Thread Rob van der Putten
Hi there Nate Bargmann wrote: As if on cue, IgnorantGuru posts up a very timely and salient post: https://igurublog.wordpress.com/2015/06/13/openwashing-and-other-deceptions-in-linux/ Sadly, CUPS is long one of these technologies ensnared by Apple and now we're beholden to them. At first CU

Re: [Dng] printing (was Re: Readiness notification)

2015-06-15 Thread Roger Leigh
On 15/06/2015 14:57, Steve Litt wrote: Just so I understand your answer in relation to my question, you're saying that "Start after" means "start sometime after", not "start immediately after". Right? Yes, exactly this. It's just a prerequisite condition: "b must start after a is started" an

Re: [Dng] printing (was Re: Readiness notification)

2015-06-15 Thread Steve Litt
On Mon, 15 Jun 2015 14:43:30 + Roger Leigh wrote: > On 15/06/2015 14:35, Steve Litt wrote: > > On Mon, 15 Jun 2015 08:46:13 +0100 > > Arnt Gulbrandsen wrote: > > > > > >> I really appreciate upstart's way of declaring "start x after y". > >> (I believe systemd does the same, which I would li

Re: [Dng] printing (was Re: Readiness notification)

2015-06-15 Thread Roger Leigh
On 15/06/2015 14:35, Steve Litt wrote: On Mon, 15 Jun 2015 08:46:13 +0100 Arnt Gulbrandsen wrote: I really appreciate upstart's way of declaring "start x after y". (I believe systemd does the same, which I would like if it weren't one of 500 features.) I've been confused about this for a lo

Re: [Dng] printing (was Re: Readiness notification)

2015-06-15 Thread Steve Litt
On Mon, 15 Jun 2015 08:46:13 +0100 Arnt Gulbrandsen wrote: > I really appreciate upstart's way of declaring "start x after y". (I > believe systemd does the same, which I would like if it weren't one > of 500 features.) I've been confused about this for a long time. I know that every service h

Re: [Dng] printing (was Re: Readiness notification)

2015-06-15 Thread Arnt Gulbrandsen
LM writes: I've had a lot of problems with getting hardware working properly with Linux, so when I bought my last printer, I tried to do some research on what printers had support for Linux. As mentioned, Brother advertises support. So, I ended up buying my first (and probably last) Brother pri

Re: [Dng] printing (was Re: Readiness notification)

2015-06-15 Thread Arnt Gulbrandsen
Laurent Bercot writes: Authors *should* document readiness notification capabilities of their daemons. But then again, reality may be different. It's difficult to even know. It's _so_ easy to do things like logging the address of a client that connects and not think about having added a star

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread Isaac Dunham
On Sun, Jun 14, 2015 at 07:39:37AM -0400, LM wrote: > Hendrik Boom wrote: > > I think that Brother is one of the companies that advertises actual > > Unix support, and that my printer an HL-3170CDW, at least, accepts a > > variety of networked protocols, including some that originated in Unix. > >

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread Laurent Bercot
On 14/06/2015 23:45, Jonathan Wilkes wrote: Is there a way to tell which packages use a particular function like sd_notify et al? Authors *should* document readiness notification capabilities of their daemons. But then again, reality may be different. sd_notify will be easy to spot: there w

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread Jonathan Wilkes
On 06/14/2015 02:39 PM, Laurent Bercot wrote: On 14/06/2015 19:17, KatolaZ wrote: I am sorry but you simply don't get rid of race conditions by signalling that the daemon is ready. If the daemon dies or hangs for whatever reason, you will still have a problem, since you thought the service was u

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread Stephanie Daugherty
On Sun, Jun 14, 2015 at 11:46 AM, Steve Litt wrote: > This is an exact analogy of saying "I believe seatbelts are evil, > because car crashes should not happen." > > Shouldn't, but do. Besides that, some drivers are incompetant. Just > like some daemon authors are incompetant. Saying incompetent

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread Steve Litt
On Sun, 14 Jun 2015 18:22:26 +0100 KatolaZ wrote: > On Sun, Jun 14, 2015 at 10:35:48AM -0400, Stephanie Daugherty wrote: > > [cut] > > > > > A professional service of any sort should have monitoring - the > > administrator should be alerted within minutes if a service doesn't > > start when it

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread Steve Litt
On Sun, 14 Jun 2015 18:17:44 +0100 KatolaZ wrote: > On Sun, Jun 14, 2015 at 03:50:06PM +0200, Laurent Bercot wrote: > > On 14/06/2015 15:29, Nikolaus Klepp wrote: > > >And I thought the historic solution would be to give your web > > >printing service an id higher than cups, eg.: > > > > > >/etc/

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread Laurent Bercot
On 14/06/2015 19:17, KatolaZ wrote: I am sorry but you simply don't get rid of race conditions by signalling that the daemon is ready. If the daemon dies or hangs for whatever reason, you will still have a problem, since you thought the service was up and running while it is not any more W

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread KatolaZ
On Sun, Jun 14, 2015 at 10:35:48AM -0400, Stephanie Daugherty wrote: [cut] > > A professional service of any sort should have monitoring - the > administrator should be alerted within minutes if a service doesn't start > when it should or goes down when it shouldn't, > > Getting a little off to

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread KatolaZ
On Sun, Jun 14, 2015 at 03:50:06PM +0200, Laurent Bercot wrote: > On 14/06/2015 15:29, Nikolaus Klepp wrote: > >And I thought the historic solution would be to give your web printing > >service an id higher than cups, eg.: > > > >/etc/rc*/S04cups > >/etc/rc*/S99awsomewebprinter > > > >Together wit

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread Dr. Nikolaus Klepp
Am Sonntag, 14. Juni 2015 schrieb Laurent Bercot: > On 14/06/2015 15:29, Nikolaus Klepp wrote: > > And I thought the historic solution would be to give your web printing > > service an id higher than cups, eg.: > > > > /etc/rc*/S04cups > > /etc/rc*/S99awsomewebprinter > > > > Together with the nig

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread Steve Litt
On Sun, 14 Jun 2015 17:22:11 +0200 Laurent Bercot wrote: > > [ Stephanie ] > > I'm firmly in the camp that process supervision is evil, because > > service failures on a *nix system should not happen > > They should not happen. But they do. > And auto-restart is not the only thing that pro

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread Steve Litt
On Sun, 14 Jun 2015 15:59:17 +0200 Didier Kryn wrote: > > Here comes the remark of Katolaz: "so what?". > > What happens then? Does the webprinting service crash? Or does > it hang until Cups is ready? Is it able to detect that it is hanging? > The last would probably be the most sen

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread Go Linux
On Sun, 6/14/15, Steve Litt wrote: Subject: Re: [Dng] printing (was Re: Readiness notification) To: dng@lists.dyne.org Date: Sunday, June 14, 2015, 10:17 AM [CUT] My life is so much simpler. I have one printer connected to one computer

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread Laurent Bercot
[ Didier ] What happens then? Does the webprinting service crash? Or does it hang until Cups is ready? Is it able to detect that it is hanging? The last would probably be the most sensible way to handle the dependency :-) A professional webprinting service should be able to do that. And this is w

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread Steve Litt
On Sun, 14 Jun 2015 12:27:37 +0200 Laurent Bercot wrote: > On 14/06/2015 11:58, KatolaZ wrote: > > Sorry for asking a silly question, but what's the problem in having > > cups "running" all the time? And better, if you start/stop cups when > > you need it, why should cups notify systemd (or any o

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread Stephanie Daugherty
On Sun, Jun 14, 2015 at 9:59 AM, Didier Kryn wrote: > What happens then? Does the webprinting service crash? Or does it hang > until Cups is ready? Is it able to detect that it is hanging? The last > would probably be the most sensible way to handle the dependency :-) A > professional webprin

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread Didier Kryn
Le 14/06/2015 15:50, Laurent Bercot a écrit : On 14/06/2015 15:29, Nikolaus Klepp wrote: And I thought the historic solution would be to give your web printing service an id higher than cups, eg.: /etc/rc*/S04cups /etc/rc*/S99awsomewebprinter Together with the nightmare from unix museum (aka

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread Laurent Bercot
On 14/06/2015 15:29, Nikolaus Klepp wrote: And I thought the historic solution would be to give your web printing service an id higher than cups, eg.: /etc/rc*/S04cups /etc/rc*/S99awsomewebprinter Together with the nightmare from unix museum (aka fork when ready) it simply works. No, it do

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread Nikolaus Klepp
Am Sonntag, 14. Juni 2015 schrieb Laurent Bercot: > On 14/06/2015 11:58, KatolaZ wrote: > > Sorry for asking a silly question, but what's the problem in having > > cups "running" all the time? And better, if you start/stop cups when > > you need it, why should cups notify systemd (or any other init

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread LM
Hendrik Boom wrote: > I think that Brother is one of the companies that advertises actual > Unix support, and that my printer an HL-3170CDW, at least, accepts a > variety of networked protocols, including some that originated in Unix. > But I don't know how to access them without CUPS. > > There m

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread Laurent Bercot
On 14/06/2015 11:58, KatolaZ wrote: Sorry for asking a silly question, but what's the problem in having cups "running" all the time? And better, if you start/stop cups when you need it, why should cups notify systemd (or any other init) that it is ready to do things? Why should init be informed o

Re: [Dng] printing (was Re: Readiness notification)

2015-06-14 Thread KatolaZ
On Sat, Jun 13, 2015 at 08:04:27PM -0500, Nate Bargmann wrote: > * On 2015 13 Jun 18:23 -0500, Jonathan Wilkes wrote: > > > What part of systemd are these various (non-systemd) programs > > leveraging? Is it the sd-notify thingy? If it is that would imply a > > different course of action than if

Re: [Dng] printing (was Re: Readiness notification)

2015-06-13 Thread Nate Bargmann
* On 2015 13 Jun 18:23 -0500, Jonathan Wilkes wrote: > What part of systemd are these various (non-systemd) programs > leveraging? Is it the sd-notify thingy? If it is that would imply a > different course of action than if they are using many different > features. I know that CUPS can be run u

Re: [Dng] printing (was Re: Readiness notification)

2015-06-13 Thread Jonathan Wilkes
On 06/13/2015 01:31 PM, Clarke Sideroad wrote: On 06/13/2015 11:03 AM, Hendrik Boom wrote: On Sat, Jun 13, 2015 at 10:22:29AM -0500, Nate Bargmann wrote: * On 2015 13 Jun 08:08 -0500, LM wrote: Laurent Bercot wrote: It would be great if Devuan became the Linux distribution that offered its use

Re: [Dng] printing (was Re: Readiness notification)

2015-06-13 Thread Clarke Sideroad
On 06/13/2015 11:03 AM, Hendrik Boom wrote: On Sat, Jun 13, 2015 at 10:22:29AM -0500, Nate Bargmann wrote: * On 2015 13 Jun 08:08 -0500, LM wrote: Laurent Bercot wrote: It would be great if Devuan became the Linux distribution that offered its users alternatives to more commonly used, often blo

Re: [Dng] printing (was Re: Readiness notification)

2015-06-13 Thread Hendrik Boom
On Sat, Jun 13, 2015 at 10:22:29AM -0500, Nate Bargmann wrote: > * On 2015 13 Jun 08:08 -0500, LM wrote: > > Laurent Bercot wrote: > > It would be great if Devuan became the Linux distribution that offered > > its users alternatives to more commonly used, often bloated software. > > It would certa

Re: [Dng] printing (was Re: Readiness notification)

2015-06-13 Thread Nate Bargmann
* On 2015 13 Jun 08:08 -0500, LM wrote: > Laurent Bercot wrote: > >As for printing servers, I don't know, but I'd be surprised > >if cupsd was the only possibility. > > > > And if it actually is the only possibility, then we have a bigger > > problem than just sd_notify: it means that monopolies

[Dng] printing (was Re: Readiness notification)

2015-06-13 Thread LM
Laurent Bercot wrote: >As for printing servers, I don't know, but I'd be surprised >if cupsd was the only possibility. > > And if it actually is the only possibility, then we have a bigger > problem than just sd_notify: it means that monopolies exist in free > software - real, existing monopolies