supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Steve Litt <slitt@troubleshooters.com>
To: supervision@list.skarnet.org
Subject: Re: interesting claims
Date: Wed, 15 May 2019 21:07:17 -0400	[thread overview]
Message-ID: <20190515210717.27b002ba@mydesk.domain.cxm> (raw)
In-Reply-To: <20190516012214.15ffcf2e@dickeberta>

On Thu, 16 May 2019 01:22:14 +0200
Oliver Schad <oliver.schad@automatic-server.com> wrote:

> On Wed, 15 May 2019 13:22:48 -0400
> Steve Litt <slitt@troubleshooters.com> wrote:
> 
> > The preceding's true for you, but not for everyone. Some
> > people, like myself, are perfectly happy with a 95% reliable
> > system. I reboot once every 2 to 4 weeks to get rid of accumulated
> > state, or as a troubleshooting diagnostic test. I don't think I'm
> > alone. Some people need 100% reliable, some don't.  
> 
> That is a strange point of view: 

Not strange at all. In a tradeoff between reliability and simplicity,
some people will sacrifice some off the former to get some of the
latter.

> there might be people who doesn't
> need computers at all. So we shouldn't program anything? 

The preceding analogy makes no sense in the current context.

> So if there
> are people outside who needs a higher quality and Laurant wants to
> target them, then he needs to deliver that and it makes sense

for Laurant to program to their higher standards because that's what he
wants to do. It would also make sense for somebody to make something
simpler, but with lower reliability.

> argument with that requirement.

I don't understand the preceding phrase in the current context.

There's a tradeoff between the product A, which has the utmost in
reliability and a fairly simple architecture, and product B, which is
fairly reliable and has the utmost in simplicity. In contrast to A and
B, there's product C whose reliability is between A and B, but which is
much less simple than A and B. Then there's productD, which is
unreliable and whose architecture is an unholy mess. When viewed over
the entire spectrum, the differences in A and B could reasonably be
termed a "family quarrel". Absent from the entire discussion are people
who don't need A, B, C or D.

SteveT


  reply	other threads:[~2019-05-16  1:07 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-29 19:19 Jeff
2019-04-30  2:49 ` Guillermo
2019-04-30  8:22 ` Laurent Bercot
2019-05-03  0:53   ` what init systems do you use ? Jeff
2019-05-11 18:45     ` Guillermo
2019-05-13 19:13     ` multiplexd
2019-05-13 20:36       ` Laurent Bercot
2019-05-13 21:09       ` Steve Litt
2019-05-14  2:34         ` Guillermo
2019-05-13 21:16       ` Joshua Ismael Haase Hernández
2019-05-14  5:50     ` Colin Booth
2019-05-14  7:15       ` eric vidal
2019-04-30  8:47 ` interesting claims Jonathan de Boyne Pollard
2019-05-01  7:26 ` Steve Litt
2019-05-01  7:33 ` Steve Litt
2019-05-01 18:13   ` Laurent Bercot
2019-05-15 17:22     ` Steve Litt
2019-05-15 23:22       ` Oliver Schad
2019-05-16  1:07         ` Steve Litt [this message]
2019-05-16  5:36           ` fungal-net
2019-05-16  8:32             ` Laurent Bercot
2019-05-16 17:10               ` Jeff
2019-05-17  0:23               ` Dewayne Geraghty
2019-05-17 11:21               ` fungal-net
2019-05-17 22:57                 ` Guillermo
2019-05-18  0:52                   ` Jeff
2019-05-18 16:26                     ` fungal-net
2019-05-18 20:04                       ` Guillermo
2019-05-19 11:24                         ` fungal-net
2019-05-19 12:57                           ` killall test run Jeff
2019-05-19 17:29                             ` Colin Booth
2019-05-19 20:39                             ` Guillermo
2019-05-19 23:06                               ` Laurent Bercot
2019-05-19 20:35                           ` interesting claims Guillermo
2019-05-03  1:37   ` how to handle system shutdown ? Jeff
2019-05-03 19:25     ` Laurent Bercot
2019-05-05  0:52       ` is it required to call kill() from process #1 ? Jeff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190515210717.27b002ba@mydesk.domain.cxm \
    --to=slitt@troubleshooters.com \
    --cc=supervision@list.skarnet.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).