crm_ticket(8) [debian man page]

PACEMAKER(8)						  System Administration Utilities					      PACEMAKER(8)

NAME

       Pacemaker - Part of the Pacemaker cluster resource manager

SYNOPSIS

       crm_ticket (query|command) [options]

DESCRIPTION

       crm_ticket - Perform tasks related to cluster tickets.  Allows ticket attributes to be queried, modified and deleted.

OPTIONS

       -?, --help
	      This text

       -$, --version
	      Version information

       -V, --verbose
	      Increase debug output

       -Q, --quiet
	      Print only the value on stdout

       -t, --ticket=value
	      Ticket ID

   Queries:
       -l, --info
	      Display the information of ticket(s)

       -L, --details
	      Display the details of ticket(s)

       -w, --raw
	      Display the IDs of ticket(s)

       -q, --query-xml
	      Query the XML of ticket(s)

       -c, --constraints
	      Display the rsc_ticket constraints that apply to ticket(s)

   Commands:
       -g, --grant
	      Grant a ticket to this cluster site

       -r, --revoke
	      Revoke a ticket from this cluster site

       -s, --standby
	      Tell this cluster site this ticket is standby

       -a, --activate
	      Tell this cluster site this ticket is active

   Advanced Commands:
       -G, --get-attr=value
	      Display the named attribute for a ticket

       -S, --set-attr=value
	      Set the named attribtue for a ticket

       -D, --delete-attr=value
	      Delete the named attribute for a ticket

       -C, --cleanup
	      Delete all state of a ticket at this cluster site

   Additional Options:
       -v, --attr-value=value
	      Attribute value to use with -S

       -d, --default=value
	      (Advanced) The default attribute value to display if none is found. For use with -G

       -f, --force
	      (Advanced) Force the action to be performed

       -n, --set-name=value
	      (Advanced) ID of the instance_attributes object to change

       -i, --nvpair=value
	      (Advanced) ID of the nvpair object to change/delete

EXAMPLES

       Display the info of tickets:

	      # crm_ticket --info

       Display the detailed info of tickets:

	      # crm_ticket --details

       Display the XML of 'ticketA':

	      # crm_ticket --ticket ticketA --query-xml

       Display the rsc_ticket constraints that apply to 'ticketA':

	      # crm_ticket --ticket ticketA --constraints

       Grant 'ticketA' to this cluster site:

	      # crm_ticket --ticket ticketA --grant

       Revoke 'ticketA' from this cluster site:

	      # crm_ticket --ticket ticketA --revoke

       Make 'ticketA' standby:

       The  cluster site will treat a granted 'ticketA' as 'standby'.  The dependent resources will be stopped or demoted gracefully without trig-
       gering loss-policies

	      # crm_ticket --ticket ticketA --standby

       Activate 'ticketA' from being standby:

	      # crm_ticket --ticket ticketA --activate

       Get the value of the 'granted' attribute for 'ticketA':

	      # crm_ticket --ticket ticketA --get-attr granted

       Set the value of the 'standby' attribute for 'ticketA':

	      # crm_ticket --ticket ticketA --set-attr standby --attr-value true

       Delete the 'granted' attribute for 'ticketA':

	      # crm_ticket --ticket ticketA --delete-attr granted

       Erase the operation history of 'ticketA' at this cluster site:

       The cluster site will 'forget' the existing ticket state.

	      # crm_ticket --ticket ticketA --cleanup

AUTHOR

       Written by Andrew Beekhof

REPORTING BUGS

       Report bugs to pacemaker@oss.clusterlabs.org

Pacemaker 1.1.7 						    April 2012							      PACEMAKER(8)

Check Out this Related Man Page

shishi_tkt_may_postdate_p(3)					      shishi					      shishi_tkt_may_postdate_p(3)

NAME

       shishi_tkt_may_postdate_p - API function

SYNOPSIS

       #include <shishi.h>

       int shishi_tkt_may_postdate_p(Shishi_tkt * tkt);

ARGUMENTS

       Shishi_tkt * tkt
		   input variable with ticket info.

DESCRIPTION

       Determine if ticket may be used to grant postdated tickets.

       The  MAY-POSTDATE  flag	in a ticket is normally only interpreted by the ticket-granting service. It can be ignored by application servers.
       This flag MUST be set in a ticket-granting ticket in order to issue a postdated ticket based on	the  presented	ticket.  It  is  reset	by
       default;  it  MAY  be  requested  by  a client by setting the ALLOW- POSTDATE option in the KRB_AS_REQ message.	This flag does not allow a
       client to obtain a postdated ticket-granting ticket; postdated ticket-granting tickets can only by obtained by requesting the postdating in
       the  KRB_AS_REQ message. The life (endtime-starttime) of a postdated ticket will be the remaining life of the ticket-granting ticket at the
       time of the request, unless the RENEWABLE option is also  set,  in  which  case	it  can  be  the  full	life  (endtime-starttime)  of  the
       ticket-granting ticket. The KDC MAY limit how far in the future a ticket may be postdated.

RETURN VALUE

       Returns non-0 iff may-postdate flag is set in ticket.

REPORTING BUGS

       Report bugs to <bug-shishi@gnu.org>.

COPYRIGHT

       Copyright (C) 2002-2010 Simon Josefsson.
       Copying	and  distribution  of  this file, with or without modification, are permitted in any medium without royalty provided the copyright
       notice and this notice are preserved.

SEE ALSO

       The full documentation for shishi is maintained as a Texinfo manual.  If the info and shishi programs are properly installed at your  site,
       the command

	      info shishi

       should give you access to the complete manual.

shishi								       1.0.1					      shishi_tkt_may_postdate_p(3)

Linux and UNIX Man Pages

crm_ticket(8) [debian man page]

Check Out this Related Man Page