All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yu, Mingli" <mingli.yu@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] systemd: use the absolute path in service file
Date: Tue, 12 Jan 2021 15:42:10 +0800	[thread overview]
Message-ID: <1daa7957-d969-1db0-9bd6-83304c74a46c@windriver.com> (raw)
In-Reply-To: <56862538e3b73683149fcba749ea5dfcedd26012.camel@linuxfoundation.org>

Hi RP,

On 1/8/21 4:52 PM, Richard Purdie wrote:
> On Fri, 2021-01-08 at 08:40 +0000, Yu, Mingli wrote:
>> This is just configuration change which defines the absolute path for
>> the command to silence the warning when systemd-analyze verify the
>> unit files and the command may be installed in different place
>> between OE and non-OE, so it should be OE specific, will resend v2 to
>> mark it is configuration specific.
> 
> Why wouldn't systemd-analyze show warnings for upstream too though?

I also checked the service file on other linux distribution such as 
Ubuntu and it also use the absolute path.

Thanks,

> 
> Cheers,
> 
> Richard
> 
> 
> 
> 
> 

  reply	other threads:[~2021-01-12  7:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07  9:56 [PATCH] systemd: use the absolute path in service file Yu, Mingli
2021-01-07 11:29 ` [OE-core] " Richard Purdie
2021-01-08  8:40   ` Yu, Mingli
2021-01-08  8:52     ` Richard Purdie
2021-01-12  7:42       ` Yu, Mingli [this message]
2021-01-12  9:29         ` Richard Purdie
2021-01-21  7:44           ` [PATCH v3] systemd: resolve executable path if it is relative Yu, Mingli
2021-01-08  8:43   ` [PATCH v2] systemd: use the absolute path in service file Yu, Mingli

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=1daa7957-d969-1db0-9bd6-83304c74a46c@windriver.com \
    --to=mingli.yu@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 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.