[sane-devel] SUSE9.1: sane-port in /etc/services
Wed, 26 May 2004 13:26:30 +0900
Matt <email@example.com> writes:
> 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.
Yes, it matters because nowhere, AFAIK, is this "sane-port" service
documented in the sane-backends sources/documentation. FYI, I just
grepped for sane-port in the sane-backends-1.0.14 sources and got zero
sane-net(5) is even so bold as to say:
For this backend to function properly, it is also necessary to define
the sane service in /etc/services. The sane service should be defined
using a line of the following form:
sane 6566/tcp # SANE network scanner daemon
whereas IANA has assigned a service by a different name to that port.
Olaf Meeuwissen EPSON KOWA Corporation, PF1
FSF Associate Member #1962 sign up at http://member.fsf.org/
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97 976A 16C7 F27D 6BE3 7D90
Penguin's lib! -- I hack, therefore I am -- LPIC-2