From: Toomas Soome <tsoome@me.com>
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] Review - 15665 svc:/network/loopback exits successfully even if it fails
Date: Fri, 26 Jul 2024 16:41:01 +0300 [thread overview]
Message-ID: <E37277E7-2D22-49AA-BE7E-2035BA9C51CD@me.com> (raw)
In-Reply-To: <CAEgYsbHoTOmhq5_B2_9XhpY07oKBAB1mze4SKFm__utaqmUUnA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]
> On 26. Jul 2024, at 15:44, Peter Tribble <peter.tribble@gmail.com> wrote:
>
> On Fri, Jul 26, 2024 at 9:21 AM Andy Fiddaman <illumos@fiddaman.net <mailto:illumos@fiddaman.net>> wrote:
>> Please can you review the following change?
>>
>> 15665 svc:/network/loopback exits successfully even if it fails
>> https://www.illumos.org/issues/15665
>> https://code.illumos.org/c/illumos-gate/+/3610
>
> When this first came up I expressed my belief that making this change is the wrong
> thing to do, and I'll express it again.
>
> If this service fails, I think the best thing to do is drive on so that the system can come
> up as far as possible to maximise the chance that the system comes up far enough for
> an administrator to be able to get in and fix it. Not putting the service into maintenance
> is a feature, not a bug.
>
> (If it fails, then there's something deeper wrong with the system, and those fundamental
> causes should be dealt with.)
>
> I think generally it would be wrong for a single voice to veto any change, which means I
> would generally be uncomfortable sticking a -1 on it, but if this does get into the gate
> it will be reverted in Tribblix.
>
hm, ok, you mean that service startup error in case of network/loopback will block too many other services? but then again, if there is an error, those depending services are also not functional, aren't they? Otherwise those depending services should not depend on network/loopback ;)
rgds,
toomas
[-- Attachment #2: Type: text/html, Size: 2492 bytes --]
next prev parent reply other threads:[~2024-07-26 13:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 8:20 Andy Fiddaman
2024-07-26 12:44 ` [developer] " Peter Tribble
2024-07-26 13:41 ` Toomas Soome [this message]
2024-07-26 14:05 ` Peter Tribble
2024-07-26 13:50 ` Andy Fiddaman
2024-07-26 15:14 ` Peter Tribble
2024-07-26 15:55 ` Jorge Schrauwen
2024-07-30 22:46 ` Gordon Ross
2024-07-31 9:44 ` Peter Tribble
2024-08-01 8:48 ` Joshua M. Clulow
2024-07-26 18:08 ` Alan Coopersmith
2024-08-07 20:04 ` Andy Fiddaman
2024-09-09 17:36 ` Andy Fiddaman
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=E37277E7-2D22-49AA-BE7E-2035BA9C51CD@me.com \
--to=tsoome@me.com \
--cc=developer@lists.illumos.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).