"Gerald Walls" <[EMAIL PROTECTED]> writes:
> Interesting. I'm running RH 6.0 and I have the following in mine (I may
> have added the ssl entries, I seem to remember) and everything *seems* to
> work fine:
>
> https 443/tcp # MCom
> https 443/udp # MCom
> ssl 443/tcp
> ssl 443/udp
AFAIK this is not the standard way to do this but if it works... ;-)
Tip: when I upgraded from 0.16-4 to 0.16-5, a long time ago, I've faced
a problem near from this one. After some investigation I discovered that
the patch 5 had changed the way diald is mapping services names to port
numbers. In 0.16-4 it was using the standard way, i.e getservbyname(),
and in 0.16-5 the code is reading directly /etc/services and performs
a pattern matching which ignores services aliases.
I still don't know why this has been done. I don't know if it is the
way 0.99 does, I still run 0.16-5 on a 2.0 kernel.
BTW, here is the standard syntax of a /etc/services:
Each line describes one service, and is of the form:
service-name port/protocol [aliases ...]
where:
service-name
is the friendly name the service is known by and
looked up under. It is case sensitive. Often,
the client program is named after the service-
name.
port is the port number (in decimal) to use for this
service.
protocol is the type of protocol to be used. This field
should match an entry in the protocols(5) file.
Typical values include tcp and udp.
aliases is an optional space or tab separated list of
other names for this service (but see the BUGS
section below). Again, the names are case sensi-
tive.
--
If the answer is NT, you've asked the wrong question
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
