From: Patrick Williams <patrick@stwcx.xyz>
To: Johnathan Mantey <johnathanx.mantey@intel.com>
Cc: Jiaqing Zhao <jiaqing.zhao@linux.intel.com>,
Jeremy Kerr <jk@codeconstruct.com.au>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Lei Yu <yulei.sh@bytedance.com>
Subject: Re: Checking for network online
Date: Thu, 24 Feb 2022 14:09:11 -0600 [thread overview]
Message-ID: <Yhfl589tw2oeLJ9C@heinlein> (raw)
In-Reply-To: <3f4f0cc0-7967-66f9-a085-a6b2ae978a01@intel.com>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
On Wed, Feb 23, 2022 at 12:04:12PM -0800, Johnathan Mantey wrote:
> On 2/23/22 09:44, Jiaqing Zhao wrote:
> > On 2022-02-23 21:48, Patrick Williams wrote:
> >> On Wed, Feb 23, 2022 at 10:09:19AM +0800, Jiaqing Zhao wrote:
> There may be openbmc powered servers that do use the distributed logging
> provided by rsyslogd. If there are then globally removing network-online
> from the rsyslog service file is undesirable. I consider the same to be
> true of assigning a default RequiredForOnline=false.
>
> Based on the above, it's my opinion this is a vendor based decision for
> how to configure rsyslog/systemd-networkd-wait-online.
I agree we shouldn't enable this globally, but that doesn't mean we can't add
a simple PKGCONFIG that allows it to be enabled/disabled as needed. That way
we only have the single `PKGCONFIG:append` line in vendor layers and vendors
that have a problem with it can leave it same as upstream.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-02-24 20:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 22:54 Checking for network online Johnathan Mantey
2022-02-18 0:11 ` Jeremy Kerr
2022-02-18 2:29 ` Lei Yu
2022-02-18 16:11 ` Johnathan Mantey
2022-02-23 2:09 ` Jiaqing Zhao
2022-02-23 13:48 ` Patrick Williams
2022-02-23 17:44 ` Jiaqing Zhao
2022-02-23 18:36 ` Bills, Jason M
2022-02-23 18:58 ` Patrick Williams
2022-02-23 18:55 ` Patrick Williams
2022-02-23 20:04 ` Johnathan Mantey
2022-02-24 20:09 ` Patrick Williams [this message]
2022-03-02 6:15 ` Jiaqing Zhao
2022-03-01 19:56 ` Milton Miller II
2022-02-18 19:04 ` Doman, Jonathan
2022-02-18 19:39 ` Johnathan Mantey
2022-02-23 13:58 ` Patrick Williams
2022-03-02 6:24 ` Ratan Gupta
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=Yhfl589tw2oeLJ9C@heinlein \
--to=patrick@stwcx.xyz \
--cc=jiaqing.zhao@linux.intel.com \
--cc=jk@codeconstruct.com.au \
--cc=johnathanx.mantey@intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=yulei.sh@bytedance.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.