Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   10987 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

rpc_gss_set_svc_name(3N)			      rpc_gss_set_svc_name(3N)

NAME
       rpc_gss_set_svc_name() - send a principal name to a server

SYNOPSIS

DESCRIPTION
       sets  the  name of a principal the server is to represent.  If a server
       is going to act as more than  one  principal,  this  procedure  can  be
       invoked for every such principal.

PARAMETERS
       Information  on	data  types  for  parameters  may be found on the rpc‐
       sec_gss(3N) manpage.

       principal   An ASCII string representing the server's  principal	 name,
		   given in the form of service@host.

       mech	   An ASCII string representing the security mechanism in use.
		   Valid strings may be found in the file, or by using

       req_time	   The time, in seconds, for  which  a	credential  should  be
		   valid.   Note that the req_time is a hint to the underlying
		   mechanism.  The actual time that the credential will remain
		   valid  is mechanism dependent.  In the case of kerberos the
		   actual time will be

       program	   The RPC program number for this service.

       version	   The RPC version number for this service.

MULTITHREAD USAGE
       Thread Safe:	     Yes
       Cancel Safe:	     Yes
       Fork Safe:	     No
       Async-cancel Safe:    No
       Async-signal Safe:    No

       These functions can be called safely in	a  multithreaded  environment.
       They  may  be  cancellation points in that they call functions that are
       cancel points.

       In a multithreaded environment, these functions	are  not  safe	to  be
       called  by  a child process after and before These functions should not
       be called by a multithreaded  application  that	supports  asynchronous
       cancellation or asynchronous signals.

RETURN VALUE
       returns if it is successful; otherwise, use to get the error associated
       with the failure.

FILES
       File containing valid security mechanisms

SEE ALSO
       rpc(3N),	 rpc_gss_get_mechanisms(3N),   rpc_gss_get_principal_name(3N),
       rpcsec_gss(3N), mech(4).

						      rpc_gss_set_svc_name(3N)

Vote for polarhome