I know that on Linux systems you can find out the process behind a PID by
using the proc file system. The bug submitter has, however, requested that
licq handle that, and that would necessarily have to be done in some
platform-independent fashion. Add to that that licq is a user process and
therefore might not have full access to the proc file system. Therefore, I
think that this issue cannot be reasonably solved.
It is possible but might require a lot of work. Before I wrote my reply I looked up the source of ``start-stop-daemon'' which is in the ``dpkg'' package.
There all this stuff is handled in three functions[1] implemented and conditionally compiled for each platform (listed in [2]).
However I know that this is nothing of the package maintainer's business. I've got similar feature requests for my packages. I would not implement them myself and they are not very high on the TODO list of the upstream author either, but I mostly keep them open in the BTS and tag them appropriately.
Kind regards, Philipp Kern Debian Developer
[1] pid_is_cmd (pid_is_exec), pid_is_user, pid_is_running [2] Linux, Hurd, SunOS, OpenBSD, HPUX, FreeBSD, NetBSD, OpenBSD
PGP.sig
Description: This is a digitally signed message part
