Re: [bug-inetutils] On hardcoded pid-files.

[Alfred M. Szmidt]

   I just noticed that `ftpd' and `inetd' use hardcoded paths
   to their PID recording files: 

        $(localstatedir)/run/ftpd.pid
        $(localstatedir)/run/inetd.pid

   There is a command line option for `ftpd' to change this,
   but none such for `inetd'. Is this a design decision hewn
   into stone?

Personally, I'd like to get the whole PID file cruft removed...  ftpd,
inetd, and what not should return the proper PID via other means.  But
yes, inetd lacking a means of specifying the PID file is a bug.