Sponsored Content
Top Forums UNIX for Advanced & Expert Users End of Life / Life Cycle Information Post 302177669 by fpmurphy on Saturday 22nd of March 2008 10:39:20 AM
Old 03-22-2008
The official end-of-life date for Tru64 UNIX v4.0D was 6/30/2000.
 

3 More Discussions You Might Find Interesting

1. News, Links, Events and Announcements

End of life date for errata support for our final Red Hat Linux distribution

Dear Red Hat Linux user, We are approaching the published end of life date for errata support for our final Red Hat Linux distribution. We'd like to remind you of this date and the options available to you for migrating your Red Hat Linux implementations: Red Hat Enterprise Linux and the... (0 Replies)
Discussion started by: google
0 Replies

2. AIX

AIX 5.2 End of Life

Hello, has anyone heard of plans to end of life AIX 5.2? We are currently a 5.2 shop and are bringing in some new servers and are debating using 5.3 on the new boxes. Also, does anyone know of a site or document that show all the advantages of 5.3 over 5.2? Such as better jfs2 support etc. ... (3 Replies)
Discussion started by: zuessh
3 Replies

3. HP-UX

The life cycle of System logfiles

Hi , The log files of the system are located in /var/admin/syslog , I want to know on which way the files are generated. To be more clear for example old log files are deleted automatically from the sytem ( is that configured ? if yes what is the criteria: is it file volume or file date or ..)... (5 Replies)
Discussion started by: enabbou
5 Replies
getservbyname(3)					     Library Functions Manual						  getservbyname(3)

NAME
getservbyname, getservbyname_r - Get a service entry by name LIBRARY
Standard C Library (libc.so, libc.a) SYNOPSIS
#include <netdb.h> struct servent *getservbyname( const char *name, const char *proto); [Tru64 UNIX] The following obsolete function is supported in order to maintain backward compatibility with previous versions of the oper- ating system. You should not use it in new designs. int getservbyname_r( const char *name, const char *proto, struct ser- vent *serv, struct servent_data *serv_data); STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: getservbyname(): XNS4.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. PARAMETERS
Specifies the official name or alias name of the service. Specifies the name of the protocol to use when contacting the service. [Tru64 UNIX] For getservbyname_r() only, this points to the servent structure. The netdb.h header file defines the servent structure. [Tru64 UNIX] For getservbyname_r() only, this is data for the services database. The netdb.h header file defines the servent_data structure. DESCRIPTION
The getservbyname() function returns a pointer to a structure of type servent. Its members specify data in fields from a record line in either the local /etc/services file or the NIS distributed network services database file. To determine which file or files to search, and in which order, the system uses the switches in the /etc/svc.conf file. The netdb.h header file defines the servent structure. The getservbyname() function searches the network services database file sequentially until a match with the name parameter and with the proto parameter occurs. The name parameter can specify either the official name or its alias. When EOF (End-of-File) is reached without the match, a null pointer is returned by this subroutine. When the protocol name is not specified (proto parameter is NULL), the proto parame- ter need not be matched during the network services database file record search. Use the endservent() function to close the network services database file. NOTES
The getservbyname() function returns a pointer to thread-specific data. Subsequent calls to this or a related function from the same thread overwrite this data. [Tru64 UNIX] The getservbyname_r() function is an obsolete reentrant version of the getservbyname() 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 servent_data structure before its first access by either the setservent_r() or getservbyname_r() function. RETURN VALUES
Upon successful completion, the getservbyname() function returns a pointer to a servent structure. If it fails or reaches the end of the network services database file, it returns a null pointer. [Tru64 UNIX] Upon successful completion, the getservbyname_r() function stores the servent structure in the location pointed to by serv, and returns a value of 0 (zero). Upon failure, it returns a value of -1. ERRORS
[Tru64 UNIX] If any of the following conditions occurs, the getservbyname_r() function sets errno to the corresponding value: The serv or serv_data parameter is invalid. The search failed. In addition, if the function fails to open the file, it sets errno to indicate the cause of the failure. FILES
The DARPA Internet network service-name database. Each record in the file occupies a single line and has four fields: the official service name, the port reference, protocol name, and aliases. The database service selection configuration file. RELATED INFORMATION
Functions: getservbyport(3), getservent(3), setservent(3), endservent(3). Files: services(4), svc.conf(4). Networks: nis_intro(7). Standards: standards(5). delim off getservbyname(3)
All times are GMT -4. The time now is 05:12 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy