Index for Section 8

Alphabetical listing for C

Bottom of page

caa_start(8)
NAME
  caa_start - Starts application resources that have been registered with
  Cluster Application Availability (CAA).

SYNOPSIS
  /usr/sbin/caa_start resource_name [...] [-c cluster_member] [-q]

  /usr/sbin/caa_start resource_name  [-c cluster_member] [-q]

  /usr/sbin/caa_start -all [-q]

PARAMETER
  resource_name [...]
      Name(s) (as specified in a resource profile) of one or more resources
      to be started.  The resource must be registered with CAA.

OPTIONS
  -c cluster_member
      Starts each indicated application resource on the specified member,
      regardless of its placement policy. If an application resource's
      required resources are not available on the destination member, the
      caa_start command fails.	If the specified member is not available, the
      command fails.

  -all
      Starts all registered CAA application resources on active cluster
      members, according to their placement policies and required resource
      lists.

  -q  Runs the caa_start command in quiet mode; no messages are displayed on
      the console.

DESCRIPTION
  The caa_start command starts application resources that are registered with
  the CAA daemon. It calls the start entry point in the resource's action
  script.  If the start fails, CAA marks the resource as "Suspended." You
  must stop a suspended resource before restarting it (see caa_stop(8)).

  You must have root privilege to use this command.

  After a registered resource is started, you must use the caa_stop command
  to end its execution.

  The caa_start command displays progress on the command line. If there are
  troubles starting an application, feedback will be displayed.	 If the CAA
  daemon is busy and cannot process the caa_start request immediately, a
  message to this effect is displayed and the request is queued for
  processing once the daemon is free.

EXAMPLE
   1.  The following example starts an application:
	    /usr/sbin/caa_start xclock
	    Trying to start `xclock` on `polishham`
	    Successfully started `xclock` on `polishham`

   2.  The following example starts an application on a specific cluster
       member:
	    /usr/sbin/caa_start -c provolone xclock
	    Trying to start `xclock` on `provolone`
	    Successfully started `xclock` on `provolone`

EXIT VALUES
  The following exit values are returned:

  0   Successful completion.

  non-zero
      A failure has occurred.

      A corresponding text message will be given for the following
      conditions:

      No root privilege.

      The CAA daemon is not running.

      The application is running.

      A profile file is not found.

      A start action script is not found.

      The cluster member was specified and it was not available.

      A timeout was reached before the startup was unsuccessful.

SEE ALSO
  Commands:  caa_stat(1), caa_profile(8), caa_register(8), caa_unregister(8),
  caa_stop(8), caa_relocate(8)

  Daemon:  caad(8)

  File:	 caa(4)

  TruCluster Server Cluster Administration

Index for Section 8

Alphabetical listing for C

Top of page