Skip to Content.
Sympa Menu

freetds - RE: configure bombs on DU 4.0

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Varley, David(CBorn at Alcoa)" <David.Varley AT alcoa.com.au>
  • To: 'TDS Development Group' <freetds AT franklin.oit.unc.edu>
  • Subject: RE: configure bombs on DU 4.0
  • Date: Thu, 12 Sep 2002 19:17:34 +0800

Thats why I reopened this thread addressed to Nick, as he was
doing testing on DU4.0 (aka Tru64) and looking at threadsafe
code, I believe.

I've attached the man page, gethostbyaddr_r was not recommended for
new code at that stage!

OS version is 4.0f, was OSF1, then DU, then Tru64, and now HP something,
soon to be assimilated (ie dropped in favour of HPUX :( ).

If noone has this working, I can live without it, I'm afraid that with
the dropping of Tru64 by HP, any corporate support here is evaporating.
At a meeting yesterday I was basically told all the alpha systems will
be replaced by Win2K servers at the next upgrade. Before I get to deploy
FreeTDS in the field. I'm still happy to test on it, though.

David

> -----Original Message-----
> From: ZIGLIO Frediano [mailto:Frediano.Ziglio AT vodafoneomnitel.it]
> Sent: Thursday, 12 September 2002 7:25 PM
> To: TDS Development Group
> Subject: [freetds] RE: configure bombs on DU 4.0
>
>
> > >
> > > Freddy,
> > >
> > > Tests 1-6 core-dump, 7 and 8 both pass.
> > > No freetds.log is generated, but here's a run of t0001 with
> > > resulting core-dump, foloowed by stack traces using first gdb
> > > and then dbx (which seems to grok the libc symbols better).
> > >
> > > Parameters to gethostbyaddr_r look a bit odd, right number,
> > > but strange values. If tds_gethostbyaddr_r is passing a
> > > structure address as the last parameter, how can it be 0 ?
> > >
> >
> > Well... a "man gethostbyaddr_r" should be useful.
> >
> > freddy77
> >
> I found it.
> What version of Tru64 are you using ??
> Version 5 (I don't know earlier) have reentrant gethostbyaddr
> function.
> I think we should change our reentrant implementation for tru64.
> There is a define for tru64 system ?
> Something like
>
> #ifdef __TRU64__
> /* Oh.. tru64 system found */
> #endif
> ??
>
> And to know version ??
>
> freddy77
>
> =================================
> "STRICTLY PERSONAL AND CONFIDENTIAL
>
> This message may contain confidential and proprietary
> material for the sole
> use of the intended recipient. Any review or distribution by others is
> strictly prohibited. If you are not the intended recipient
> please contact
> the sender and delete all copies.
> The contents of this message that do not relate to the
> official business of
> our company shall be understood as neither given nor endorsed by it."
>
> =================================
>
> ---
> You are currently subscribed to freetds as:
> [David.Varley AT alcoa.com.au]
> To unsubscribe, forward this message to
> $subst('Email.Unsub')
>




gethostbyaddr(3) gethostbyaddr(3)



NAME

ggeetthhoossttbbyyaaddddrr,
ggeetthhoossttbbyyaaddddrr__rr - Gets a network host entry by
address

LIBRARY

Standard C Library (lliibbcc..ssoo,, lliibbcc..aa)

SYNOPSIS

##iinncclluuddee <<nneettddbb..hh>>

ssttrruucctt hhoosstteenntt
**ggeetthhoossttbbyyaaddddrr((
ccoonnsstt vvooiidd *_a_d_d_r,,
ssiizzee__tt _l_e_n,,
iinntt _t_y_p_e)) ;;

[DIGITAL] The following obsolete function is supported in order to main-
tain backward compatibility with previous versions of the operating system.
You should not use it in new designs.

iinntt **ggeetthhoossttbbyyaaddddrr__rr((
ccoonnsstt cchhaarr *_a_d_d_r,,
iinntt _l_e_n,,
iinntt _t_y_p_e,,
ssttrruucctt hhoosstteenntt **_h_p_t_r,,
ssttrruucctt hhoosstteenntt__ddaattaa
**_h_d_p_t_r));;

[DIGITAL] The following definition of the
ggeetthhoossttbbyyaaddddrr(()) function does
not conform to current standards and is supported only for backward compa-
tibility (see ssttaannddaarrddss(5)):

ssttrruucctt hhoosstteenntt
**ggeetthhoossttbbyyaaddddrr((
ccoonnsstt cchhaarr *_a_d_d_r,,
iinntt _l_e_n,,
iinntt _t_y_p_e)) ;;

STANDARDS

Interfaces documented on this reference page conform to industry standards
as follows:

ggeetthhoossttbbyyaaddddrr(()): XNS4.0

Refer to the ssttaannddaarrddss(5) reference page for more
information about indus-
try standards and associated tags.

PARAMETERS

_a_d_d_r Specifies an Internet address in network order.

_l_e_n Specifies the number of bytes in an Internet address.

_t_y_p_e Specifies the Internet domain address format. The value
AAFF__IINNEETT
must be used.

_h_d_p_t_r [DIGITAL] Is data for the host database. The
nneettddbb..hh header
file defines the hhoosstteenntt__ddaattaa structure.

_h_p_t_r [DIGITAL] Points to the hhoosstteenntt structure.
The nneettddbb..hh header
file defines the hhoosstteenntt structure.

DESCRIPTION

The ggeetthhoossttbbyynnaammee(()) function returns a
pointer to a structure of type hhooss--
tteenntt. Its members specify data obtained from either the local
//eettcc//hhoossttss
file or one of the files distributed by BIND or NIS. To determine which
file or files to search, and in which order, the system uses the switches
in the //eettcc//ssvvcc..ccoonnff file. The
nneettddbb..hh header file defines the hhoosstteenntt
structure.

The ggeetthhoossttbbyyaaddddrr(()) function searches the
network host database sequen-
tially until a match with the _a_d_d_r and _t_y_p_e parameters
occurs. The _l_e_n
parameter must specify the number of bytes in an Internet address. The
_a_d_d_r_e_s_s parameter must specify the address in network
order. The _t_y_p_e
parameter must be the constant AAFF__IINNEETT, which specifies the
Internet
address format. When EEOOFF (End-of-File) is reached without a match, an
error
value is returned.

If using BIND, the information is obtained from a name server specified in
the //eettcc//rreessoollvv..ccoonnff file. When the name
server is not running, the
ggeetthhoossttbbyyaaddddrr(()) function searches the local
hhoossttss name file.

Use the eennddhhoosstteenntt(()) function to close the
//eettcc//hhoossttss file.

NOTES

The ggeetthhoossttbbyyaaddddrr(()) function returns a
pointer to thread-specific data.
Subsequent calls to this or a related function from the same thread
overwrite this data.

[DIGITAL] The ggeetthhoossttbbyyaaddddrr__rr(()) function
is an obsolete reentrant version
of the ggeetthhoossttbbyyaaddddrr(()) function. It is
supported in order to maintain
backward compatibility with previous versions of the operating system and
should not be used in new designs. Note that you must zero-fill the
_h_d_p_t_r
structure before its first access by the
ggeetthhoossttbbyyaaddddrr__rr(()) function.

RETURN VALUES

Upon successful completion, the
ggeetthhoossttbbyyaaddddrr(()) function returns a pointer
to a hhoosstteenntt structure. If it reaches the end of the
network hostname
database, it returns a null pointer.

[DIGITAL] Upon successful completion, the
ggeetthhoossttbbyyaaddddrr__rr(()) function
stores the hhoosstteenntt structure in _h_p_t_r, and returns a
value of 0 (zero).
Upon failure, it returns a value of -1.

ERRORS

If the ggeetthhoossttbbyyaaddddrr(()) or
ggeetthhoossttbbyyaaddddrr__rr(()) function call fails,
hh__eerrrrnnoo is
set to one of the following values:

[[HHOOSSTT__NNOOTT__FFOOUUNNDD]]
Host is unknown.

[[NNOO__DDAATTAA]] The server recognized the request and the
name, but no address is
available for the name. Another type of name server request may
be successful.

[[NNOO__RREECCOOVVEERRYY]]
An unexpected server failure occurred. This is a nonrecoverable
error.

[[TTRRYY__AAGGAAIINN]]
A transient error occurred, for example, the server did not
respond. A retry at some later time may be successful.

[DIGITAL] If any of the following conditions occurs, the
ggeetthhoossttbbyyaaddddrr__rr(())
function sets eerrrrnnoo to the corresponding value:

[[EEIINNVVAALL]] The _n_a_m_e, _h_p_t_r, or
_h_d_p_t_r is invalid, or _t_y_p_e is not
AAFF__IINNEETT.

FILES

//eettcc//hhoossttss
This file is the DARPA Internet network hostname database. Each
record in the file occupies a single line and has three fields
consisting of the host address, official hostname, and aliases.

//eettcc//rreessoollvv..ccoonnff
The resolver configuration file.

//eettcc//ssvvcc..ccoonnff
The database service selection configuration file.

RELATED INFORMATION

Functions: eennddhhoosstteenntt(3),
ggeetthhoossttbbyynnaammee(3), sseetthhoosstteenntt(3).

Files: hhoossttss(4), rreessoollvv..ccoonnff(4),
ssvvcc..ccoonnff(4).

Networks: bbiinndd__iinnttrroo(7), nniiss__iinnttrroo(7).

Standards: ssttaannddaarrddss(5)








































Archive powered by MHonArc 2.6.24.

Top of Page