On Wed, 26 May 2004 08:48:30 +0900 Olaf Meeuwissen wrote: > > > > The correct way to fix this is to make the xinetd configuration use > > the official name. That is, the saned xinetd config file should > > contain the line 'service sane-port'. > > > > If the xinetd configuration does not match a service name in the > > /etc/services file it is ignored by xinetd, since in this case xinetd > > doesn't know on which port to listen for connections. > > I know that much, but all the sane-backend stuff mentions the "sane" > service only, AFAIK. If Henning went through the trouble of getting > the "sane-port" service registered with IANA (instead of "sane") then > shouldn't the implementation be patched to match? If Henning meant to > register the "sane" service, then something went wrong in getting that > across and IANA registered the wrong service. > > Question stands: what is the prefered way to fix this? > --
As pointed out above, just use "service sane-port" instead of "service sane". And in all honesty, does it really matter? Just alter your config. Matt
