From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: [PATCH 2/2] initscripts: Implement storing PIDs in loadproc Date: Thu, 11 Jan 2024 15:21:08 +0000 Message-ID: <20240111152108.4041802-2-michael.tremer@ipfire.org> In-Reply-To: <20240111152108.4041802-1-michael.tremer@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7596970269348970743==" List-Id: --===============7596970269348970743== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Some programs do not write their own PID files any more, but since our initscripts heavily rely on those, this extension allows to store it easily. Signed-off-by: Daniel Weism=C3=BCller --- src/initscripts/system/functions | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/initscripts/system/functions b/src/initscripts/system/functi= ons index e4cb30456..5a26aef45 100644 --- a/src/initscripts/system/functions +++ b/src/initscripts/system/functions @@ -446,6 +446,7 @@ loadproc() local pidfile=3D"" local forcestart=3D"" local nicelevel=3D"" + local pid =20 # This will ensure compatibility with previous LFS Bootscripts if [ -n "${PIDFILE}" ]; then @@ -521,12 +522,19 @@ loadproc() ( ${cmd} &>/dev/null ) & + pid=3D"$!" evaluate_retval else ${cmd} + pid=3D"$!" evaluate_retval # This is "Probably" not LSB compliant, but required to be= compatible with older bootscripts fi =20 + # Write the pidfile + if [ -n "${pid}" -a -n "${pidfile}" ]; then + echo "${pid}" > "${pidfile}" + fi + return 0 } =20 --=20 2.39.2 --===============7596970269348970743==--