xref: /titanic_51/usr/src/man/man1m/clinfo.1m (revision a3477ee4728af4a4c3c6869e248aa735d52cbefb)
te
Copyright (c) 2002, Sun Microsystems, Inc. All Rights Reserved
The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
CLINFO 1M "Mar 12, 2002"
NAME
clinfo - display cluster information
SYNOPSIS

clinfo [-nh]
DESCRIPTION

The clinfo command displays cluster configuration information about the node from which the command is executed.

Without arguments, clinfo returns an exit status of 0 if the node is configured and booted as part of a cluster. Otherwise, clinfo returns an exit status of 1.

OPTIONS

The following options are supported: -h

Displays the highest node number allowed to be configured. This is different from the maximum number of nodes supported in a given cluster. The current highest configured node number can change immediately after the command returns since new nodes can be dynamically added to a running cluster. For example, clinfo -h might return 64, meaning that the highest number you can use to identify a node is 64. See the Sun Cluster 3.0 System Administration Guide for a description of utilities you can use to determine the number of nodes in a cluster.

-n

Prints the number of the node from which clinfo is executed.

EXIT STATUS

The following exit values are returned: 0

Successful completion.

1

An error occurred. This is usually because the node is not configured or booted as part of a cluster.

SEE ALSO

attributes(5)