GSSAPI::Status man page on UnixWare

Man page or keyword search:  
man Server   3616 pages
apropos Keyword Search (all sections)
Output format
UnixWare logo
[printable version]

GSSAPI::Status(3)     User Contributed Perl Documentation    GSSAPI::Status(3)

NAME
       GSSAPI::Status - methods for handlings GSSAPI statuses

SYNOPSIS
	 use GSSAPI;

	 $status = GSSAPI::Status->new(GSS_S_COMPLETE, 0);

	 if (GSS_ERROR($status->major)) {
	   die "a horrible death";
	 }
	 if (! $status) {		       # another way of writing the above
	   die "a horrible death";
	 }

	 $status = $some_GSSAPI->someop($args1, etc);
	 if ($status) {
	   foreach ($status->generic_message, $status->specific_message) {
	     print "GSSAPI error: $_\n";
	   }
	   die "help me";
	 }

DESCRIPTION
       "GSSAPI::Status" objects are returned by most other GSSAPI operations.
       Such statuses consist of a GSSAPI generic code and, for most opera‐
       tions, a mechanism specific code.  These numeric codes can be accessed
       via the methods "major" and "minor".  The standard textual messages
       that go with the current status can be obtained via the "generic_mes‐
       sage" and "specific_message" methods.  Each of these returns a list of
       text which should presumably be displayed in order.

       The generic code part of a GSSAPI::Status is composed of three sub‐
       fields that can be accessed with the "GSS_CALLING_ERROR", "GSS_ROU‐
       TINE_ERROR", and "GSS_SUPPLEMENTARY_INFO" functions.  The returned val‐
       ues can be compared against the constants whose names start with
       "GSS_S_" if your code wants to handle particular errors itself.	The
       "GSS_ERROR" function returns true if and only if the given generic code
       contains neither a calling error nor a routine error.

       When evaluated in a boolean context, a "GSSAPI::Status" object will be
       true if and only if the major status code is "GSS_S_COMPLETE".

       When evaluated in a string contect, a "GSSAPI::Status" object will
       return the generic and specific messages all joined together with new‐
       lines.  This may or may not make "die $status" work usefully.

BUGS
       The base objects are currently implmented as a blessed C structure con‐
       taining the major and minor status codes.  It should probably be a
       blessed array or hash instead, thereby cutting down on the amount of C
       code involved and making it more flexible.

AUTHOR
       Philip Guenther <pguen@cpan.org>

SEE ALSO
       perl(1) RFC2743

perl v5.8.8			  2006-07-31		     GSSAPI::Status(3)
[top]
                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 
More information is available in HTML format for server UnixWare

List of man pages available for UnixWare

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net