[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug-inetutils] On hardcoded pid-files.
From: |
Mats Erik Andersson |
Subject: |
[bug-inetutils] On hardcoded pid-files. |
Date: |
Thu, 4 Nov 2010 11:23:57 +0100 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
Hello all,
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?
On the one hand testing becomes more hazardous, and on the
other hand, Inetd could thus interfer with an identically
named server of other origin. Such is known to exist!
The introduction of a command line option would be the
best path to tread.
Best regards,
Mats
- [bug-inetutils] On hardcoded pid-files.,
Mats Erik Andersson <=