thanks Guillem! that all seems reasonable to me, and I think we can rely on Debian Policy 10.9:
Files should be owned by "root:root", and made writable only by the
owner and universally readable (and executable, if appropriate), that
is mode 644 or 755.
I'll make adequate emit a tag if /run is accessible (it normally is) and pid
files therein are not readable.
now, I'm not sure of what'd be the most reliable way to determine which package
is responsible for the creation of any given pid file, if adequate does not run
as root. (obviously, if it runs as root, we read the pid from the file to find
out which binary it points to). but if we're not running as root, one hacky
option would be to strip ".pid" from the filename and look for such binaries in
/s?bin/ (but that wouldn't always work, e.g. /sbin/cron creates crond.pid)
signature.asc
Description: PGP signature
