diff options
| author | Zoltan Boszormenyi <zboszor@gmail.com> | 2024-07-28 16:29:06 +0200 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2024-08-03 07:56:10 +0100 |
| commit | ee83d0fdae1482583f156d8b8f217c170d9de473 (patch) | |
| tree | 2e4abdb0b0f26e6222b19f515cd5f6a755031f1a /meta/recipes-devtools/gcc | |
| parent | 2dded9958328d9e5a801dd3cb2d0084f538cfef6 (diff) | |
| download | poky-ee83d0fdae1482583f156d8b8f217c170d9de473.tar.gz | |
rpcbind: Fix boot time start failure
With commits 90bc1810 ("bitbake.conf: Add runtimedir") and
561e853e ("rpcbind: Specify state directory under /run") rpcbind
still can fail during startup with:
rpcbind: /var/run/rpcbind.lock: Read-only file system
The lockfile is hardcoded as "/var/run/rpcbind.lock".
While it should use the same internal define "RPCBIND_STATEDIR"
as the paths for rpcbind.xdr and portmap.xdr, it's not necessary
to be patched because of the default value of ${runtimedir} and
the presence of the /var/run -> /run symlink.
Using --with-statedir=/run/rpcbind adds the line
RequiresMountsFor=/run/rpcbind
to the service but it doesn't guarantee that /run is writable yet
when rpcbind.service starts. Add this guarantee by running
rpcbind.service with systemd-tmpfiles-setup.service and add the
tmpfiles.d entry for /run/rpcbind.
(From OE-Core rev: 53fb871f84c99a66485979da2588c1d11d8749e7)
Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/gcc')
0 files changed, 0 insertions, 0 deletions