From: Peter Korsgaard <peter@korsgaard.com>
To: Sergey Bobrenok via buildroot <buildroot@buildroot.org>
Cc: Joseph Kogut <joseph.kogut@gmail.com>,
Sergey Bobrenok <sibobrenok@sberdevices.ru>,
sdfw_system_team <sdfw_system_team@sberdevices.ru>
Subject: Re: [Buildroot] [PATCH 1/3] package/earlyoom: fix daemon executable path in the init script
Date: Wed, 14 Jun 2023 11:23:13 +0200 [thread overview]
Message-ID: <87352utn26.fsf@48ers.dk> (raw)
In-Reply-To: <20230529134320.1961326-1-SIBobrenok@sberdevices.ru> (Sergey Bobrenok via buildroot's message of "Mon, 29 May 2023 13:43:56 +0000")
>>>>> "Sergey" == Sergey Bobrenok via buildroot <buildroot@buildroot.org> writes:
> earlyoom.mk file explicitly sets 'PREFIX=/usr', and the init script
> fails to start earlyoom because of a nonexistent executable path:
> # /etc/init.d/S02earlyoom start
> start-stop-daemon: unable to stat /bin/earlyoom (No such file or directory)
> FAIL
> Signed-off-by: Sergey Bobrenok <SIBobrenok@sberdevices.ru>
Committed to 2023.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-06-14 9:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 13:43 [Buildroot] [PATCH 1/3] package/earlyoom: fix daemon executable path in the init script Sergey Bobrenok via buildroot
2023-05-29 13:44 ` [Buildroot] [PATCH 2/3] package/earlyoom: restore missing startup message " Sergey Bobrenok via buildroot
2023-06-02 19:25 ` Peter Korsgaard
2023-06-14 9:23 ` Peter Korsgaard
2023-05-29 13:44 ` [Buildroot] [PATCH 3/3] package/earlyoom: unhardcode package version in CFLAGS Sergey Bobrenok via buildroot
2023-06-02 19:25 ` Peter Korsgaard
2023-06-14 9:23 ` Peter Korsgaard
2023-06-02 19:25 ` [Buildroot] [PATCH 1/3] package/earlyoom: fix daemon executable path in the init script Peter Korsgaard
2023-06-14 9:23 ` Peter Korsgaard [this message]
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=87352utn26.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=joseph.kogut@gmail.com \
--cc=sdfw_system_team@sberdevices.ru \
--cc=sibobrenok@sberdevices.ru \
/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.