At 02:39 PM 4/2/2001 -0700, Peter Prymmer wrote:
>It does not look like a bug to me since it is trying to find the FQDN at
>the point in question:
but as far as I can tell, UCX$INET_HOST_NAME is not and never was something
defined by UCX, so the first line of the section you quote is probably a noop.
>$ IF myhostname.eqs."" THEN myhostname = F$TRNLNM("UCX$INET_HOST_NAME")
>$ IF myhostname.eqs."".and. -
> F$TRNLNM("UCX$INET_HOST") .nes. "" .and. -
> F$TRNLNM("UCX$INET_DOMAIN") .nes. "" THEN -
> myhostname = F$TRNLNM("UCX$INET_HOST") + "." + F$TRNLNM("UCX$INET_DOMAIN")
>
>So it ought to drop through to the values that your system has (does it
>not do so?).
Ah, yes, it apparently does, but since UCX$INET_HOST translates to "unknown"
on my system, I thought there was something missing in configure.com. It
turned out there is something missing in my system configuration, though for
the life of me I can't figure out what. I'm using the DHCP client feature,
so perhaps that keeps it from figuring out who it is.
We could probably delete the line in configure.com with UCX$INET_HOST_NAME,
but it doesn't look like having it there actually harms anything.
>Clearly something like TCPIP$* would be more recent than UCX 4.x. We
>should probably add some checks for them.
Since the UCX$* logicals are still present in TCP/IP 5.1, I think we can
rely on their existence for the forseeable future.
