Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!oliveb!felix!info-ultrix
From: kjd@rust.DEC.COM (Kevin J. Dunlap - DECwest Engineering)
Newsgroups: comp.unix.ultrix
Subject: Re: ULTRIX 3.0
Message-ID: <81534@felix.UUCP>
Date: 30 Jan 89 20:21:11 GMT
Sender: info-ultrix@felix.UUCP
Reply-To: kjd@rust.DEC.COM (Kevin J. Dunlap - DECwest Engineering)
Lines: 33
Approved: zemon@felix.UUCP
Reply-Path:

Reply-to: kjd@rust.DEC.COM (Kevin J. Dunlap - DECwest Engineering)



>>?From: hubcap@hubcap.UUCP (Mike Marshall)
>>?	...
>>?
>>?I checked the man page for gethostent, and they're still using the
>>?old-style hostent structure in netdb.h that has the single dimensional
>>?h_addr... I wonder how their sendmail handles MX records? (hmmm... I wish
>>?I was in my office where the manuals are... I wonder IF it handles MX
>>?records...)

The Ultrix V3.0 manual page for gethostent is wrong.  
The Ultrix V3.0 /usr/include/netdb.h has the correct multi dimensional 
list of host addresses.

Looks like the gethostent manual page did not get updated with the new hostent
data structure.  The hostent structure for Ultrix V3.0 is the same as 
4.3BSD & systems running BIND:

struct	hostent {
	char	*h_name;	/* official name of host */
	char	**h_aliases;	/* alias list */
	int	h_addrtype;	/* host address type */
	int	h_length;	/* length of address */
	char	**h_addr_list;	/* list of addresses from name server */
#define	h_addr	h_addr_list[0]	/* address, for backward compatiblity */
};

MX support is in Ultrix V3.0 sendmail!!

-Kevin Dunlap  kjd@decwrl.DEC.COM