On Mon, Nov 02, 2009 at 01:16:10PM -0500, Michael Krieger wrote: > Package: proftpd-basic > Version: 1.3.1-17lenny2 > Severity: normal > > When installing proftpd, the user is prompted for standalone or inetd mode. > If inetd mode is chosen, no check is made for inetd being present. > Accordingly, > a failed grep happens and the package appears to install fine, however is not > configured or enabled as a result of the inability to install it into an > inetd mode. > > The correct response should be that the check is made for the > inetd-superserver > virtual package and a note stating that it can't be installed in inetd mode, > forcing it in standalone mode. It can not be depended on as a package, or it > will require an unnecessary dependancy in standalone mode. >
Well, this is not a big result, because admin could always remove inetd/xinetd and leave proftpd configuration broken anyway after installation. > This check is missing and unfortunately the package silently fails and of > course > doesn't start. Installing inetd after the fact will likely result in a > missing entry > and need to reconfigure proftpd. > I could add a warning about the missing inetd-superserver at config time. That would suggest admin to do his/her homework better :) The init script is already descriptive in my opinion. Unfortunately there's nothig to do better, inetd-superserver is definitively not mandatory for proftpd and admin has dozen of different ways to break configuration. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
