Service shutdown leaves seafevents.pid file hanging around

[laur89]

My understanding is shutting down both seafile & seahub via seahub.sh & seafile.sh stop commands should shut down all processes and clean up the pidfiles. However seafevents.pid remains. The PID in the file however does not appear to be running anymore.

Also note it's the only PID-file that contains PID without a trailing newline. No idea whether that's important or not:

┌─[srvr]─[/mnt/user/seafile]
└──╼ + ls -ltr pids
total 12K
-rw-r--r-- 1 root root 5 Oct  7 11:58 seaf-server.pid
-rw-r--r-- 1 root root 4 Oct  7 11:58 seafevents.pid
-rw-r--r-- 1 root root 5 Oct  7 11:58 seafdav.pid
┌─[srvr]─[/mnt/user/seafile]
└──╼ + cat pids/seafevents.pid 
5438┌─[srvr]─[/mnt/user/seafile]
└──╼ + cat pids/*
5402
5476
5438┌─[srvr]─[/mnt/user/seafile]  <-- note 5438 doesn't have a newline, causing shell prompt to be appended
└──╼ +

Running v11.0.12 in phusion/baseimage:jammy-1.0.4 container.