From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id DE7BAC433F5 for ; Wed, 23 Feb 2022 18:38:41 +0000 (UTC) Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4K3lDH2RYrz3bc6 for ; Thu, 24 Feb 2022 05:38:39 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.a=rsa-sha256 header.s=Intel header.b=lPLcKdbc; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=none (no SPF record) smtp.mailfrom=linux.intel.com (client-ip=134.134.136.20; helo=mga02.intel.com; envelope-from=jason.m.bills@linux.intel.com; receiver=) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.a=rsa-sha256 header.s=Intel header.b=lPLcKdbc; dkim-atps=neutral Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4K3lCY0pVSz3bV6 for ; Thu, 24 Feb 2022 05:37:59 +1100 (AEDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645641481; x=1677177481; h=message-id:date:mime-version:subject:to:references:from: in-reply-to:content-transfer-encoding; bh=AR3lXJW2KcD5AFpAcoh6ZmthqI7ii5jDjja5Z1MyUlY=; b=lPLcKdbcz+r2C4KAmYwVc3OUbf2qHBPwzgcXfZt79OjPmeRW6K7Lj9Ph OaAEKm5zy/EP2Rcr7dfyV3Xozt+oe/3+a2uQMegbISUysOZ2djSiaNSx3 QVVvpSCYGdRxi3me9npGqjpiQRaRadPjuG3VN/h4qpF8An+Q2MWM00Heh JtZgoOQPW9EZtUXcj8rtJyQp0ieywLrdfYBxUwcibjl9vlwYlWhLYU9Rn zdtw4bT6HahsCxivgH0JXR5XRQ/apg0wIXt5QxYEE1ak/W+wfEshaZWmO uGOfMY+DQ5Ej4Q9gTw1ggWo8LdUjUR/ozx8ED+R7/3uXh8/uak7PK2kOc w==; X-IronPort-AV: E=McAfee;i="6200,9189,10267"; a="239445717" X-IronPort-AV: E=Sophos;i="5.88,391,1635231600"; d="scan'208";a="239445717" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Feb 2022 10:36:56 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.88,391,1635231600"; d="scan'208";a="782897440" Received: from linux.intel.com ([10.54.29.200]) by fmsmga005.fm.intel.com with ESMTP; 23 Feb 2022 10:36:54 -0800 Received: from [10.212.187.244] (jmbills-MOBL.amr.corp.intel.com [10.212.187.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by linux.intel.com (Postfix) with ESMTPS id 1C9E1580295 for ; Wed, 23 Feb 2022 10:36:51 -0800 (PST) Message-ID: <3402647e-d195-4537-1279-bf4f7839161e@linux.intel.com> Date: Wed, 23 Feb 2022 11:36:50 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: Checking for network online Content-Language: en-US To: openbmc@lists.ozlabs.org References: <37a29642-788c-b966-3b58-214c3d44c8f4@intel.com> <64727f8e-cca3-b04d-e4cf-709ceb60f37f@linux.intel.com> <112c8819-24bc-2a24-45a3-9c919088f43a@linux.intel.com> From: "Bills, Jason M" In-Reply-To: <112c8819-24bc-2a24-45a3-9c919088f43a@linux.intel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: openbmc-bounces+openbmc=archiver.kernel.org@lists.ozlabs.org Sender: "openbmc" On 2/23/2022 10:44 AM, 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: ... > > My understanding is that in OpenBMC, the propose to use rsyslog is to format the Redfish and IPMI SEL logs from system journal. The "r" of rsyslogd is not used in most cases. > Just a nit-picky side-note: The "r" in rsyslogd is for "rocket-fast". I don't believe rsyslogd is inherently designed for remote logging. https://www.rsyslog.com/