diff options
| author | Kyle Nieman <kyle.nieman@fii-na.com> | 2023-10-16 21:44:14 +0300 |
|---|---|---|
| committer | Kyle Nieman <kyle.nieman@fii-na.com> | 2024-01-06 01:52:32 +0300 |
| commit | 86347becd852967e550b3f427eebe80ec3ac7618 (patch) | |
| tree | 75b3647a741b0862faa888d6c82c5123fdab4de3 /meta-openembedded/meta-python/recipes-devtools | |
| parent | 15f018161f68a422bf9f8ed6dcc75db675dae626 (diff) | |
| download | openbmc-86347becd852967e550b3f427eebe80ec3ac7618.tar.xz | |
meta-fii: meta-mori: Launch apps by correct path to avoid anti-pattern
As specified by OpenBMC anti-pattern document, calls to a binary/script
should be the fully qualified path to the application being launched.
https://github.com/openbmc/docs/blob/717d273cf8bceac3868a278aeb34d19e8d74c1b3/anti-patterns.md#resolution-4
This follows the systemd recommendation to use the full
path to avoid ambiguity.
https://www.freedesktop.org/software/systemd/man/systemd.service.html#:~:text=Using%20an%20absolute%20path%20is%20recommended%20to%20avoid%20ambiguity
In addition, OpenBMC applications that are intended to be used by users
should be located in /usr/bin.
Changes:
Place user scripts in /usr/bin instead of /usr/sbin. Start scripts by
their absolute path in service files.
Testing:
The services that are modified can find and start their scripts. The
scripts that had their locations modified can be called by the user
without providing their full path.
Change-Id: Ibe7fbb1644aa1b0df0f296ea1f1a8ceaf444fe35
Signed-off-by: Kyle Nieman <kyle.nieman@fii-na.com>
Diffstat (limited to 'meta-openembedded/meta-python/recipes-devtools')
0 files changed, 0 insertions, 0 deletions