From markcarl@sac.sfbay.sun.com Mon Apr 13 13:41:18 2009
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3DKfIlK025516
	for <LSARC-ext@sac.sfbay.sun.com>; Mon, 13 Apr 2009 13:41:18 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3DKfFRK046145;
	Mon, 13 Apr 2009 14:41:18 -0600 (MDT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI200J0144TO000@brm-avmta-1.central.sun.com>; Mon,
 13 Apr 2009 14:41:17 -0600 (MDT)
Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI200BD344SE050@brm-avmta-1.central.sun.com>; Mon,
 13 Apr 2009 14:41:16 -0600 (MDT)
Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132])
	by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2)
 with ESMTP id n3DKfF8b006943; Mon, 13 Apr 2009 13:41:15 -0700 (PDT)
Received: from sac.sfbay.sun.com (localhost [127.0.0.1])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3DKfDiY025511; Mon,
 13 Apr 2009 13:41:13 -0700 (PDT)
Received: (from markcarl@localhost)
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n3DKfDgk025507; Mon,
 13 Apr 2009 13:41:13 -0700 (PDT)
Date: Mon, 13 Apr 2009 13:41:13 -0700 (PDT)
From: Mark Carlson <markcarl@sac.sfbay.sun.com>
Subject: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
To: LSARC-ext@sun.com
Cc: Vivek.Titarmare@sun.com
Message-id: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
Status: RO
Content-Length: 2640

I am sponsoring this familiarity case for Vivek Titarmare, requesting minor binding and timing out 04/20/2009.

-- mark

Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
This information is Copyright 2009 Sun Microsystems
1. Introduction
    1.1. Project/Component Working Name:
	 pdsh Ver 2.18
    1.2. Name of Document Author/Supplier:
	 Author:  Vivek Titarmare
    1.3  Date of This Document:
	13 April, 2009

2. Project Summary
   2.1 Project Description

	Parallel command execution for clusters

4. Technical Description:

	Pdsh is a high-performance, parallel remote shell utility. It has built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and can call SSH externally (though with reduced performance). Pdsh uses a "sliding window" parallel algorithm to conserve socket resources on the initiating node and to allow progress to continue while timeouts occur on some connections.
	
	Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which runs commands on a single remote host, pdsh can run multiple remote commands in parallel. pdsh uses a "sliding window" (or fanout) of threads to conserve resources on the the initiating host while allowing some connections to time out. 	

5. Interfaces 

	The binary file "pdsh" contains following interface.

   Exported interface                   Classification 		Interface type
   =============================        ============== 		==============
	pdsh-rcmd-rsh			Committed     		requires rshd server running on remote nodes
	pdsh-rmcd-ssh			Committed 		requires ssh installed, sshd on remote nodes
	pdsh-rcmd-mrsh			Committed 		requires munge 
	pdsh-rcmd-qshell		Committed 		requires qsnet, pdsh-qshd (qshell server)
	pdsh-rcmd-mqshell		Committed 		requires qsnet, munge, pdsh-mqshd (mqshell server)
	pdsh-rcmd-xcpu			Committed 		requires XCPU service mounted on /mnt/xcpu/<hostname>/xcpu
	pdsh-mod-genders		Uncommitted		requires libgenders
	pdsh-mod-nodeattr		Uncommitted		requires nodeattr program
	pdsh-mod-nodeupdown		Uncommitted		requires libnodeupdown
	pdsh-mod-machines		Uncommitted		None
	pdsh-mod-rms			Uncommitted		requires RMS: rmsquery, qsrmslibs
	pdsh-mod-slurm			Uncommitted		requires slurm
	pdsh-mod-dshgroup		Uncommitted		None
	pdsh-mod-netgroup		Uncommitted		None	
	

   Imported interface        Classification   Comments
   =======================   ==============   =================================== 
	None

   The binary file would go in "usr/local/bin"


6. Resources and Schedule
    6.4. Steering Committee requested information
   	6.4.1. Consolidation C-team Name:
		SFW
    6.5. ARC review type: FastTrack
    6.6. ARC Exposure: open


From John.Fischer@sun.com Mon Apr 13 13:48:05 2009
Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3DKm3xu026252
	for <LSARC-ext@sac.sfbay.sun.com>; Mon, 13 Apr 2009 13:48:04 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n3DKluWL023665
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 14 Apr 2009 04:48:02 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI2001034FZMZ00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@Sun.COM); Mon, 13 Apr 2009 13:47:59 -0700 (PDT)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI200LT14FZT740@nwk-avmta-1.sfbay.Sun.COM> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Mon,
 13 Apr 2009 13:47:59 -0700 (PDT)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3DKlwiD013844	for
 <LSARC-ext@Sun.COM>; Mon, 13 Apr 2009 20:47:59 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KI2001004B5W200@mail-amer.sun.com> for LSARC-ext@Sun.COM
 (ORCPT LSARC-ext@Sun.COM); Mon, 13 Apr 2009 14:47:58 -0600 (MDT)
Received: from [192.168.10.7] ([unknown] [76.20.56.47])
 by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit
 (built Feb 19 2009)) with ESMTPSA id <0KI200GZ64FX5090@mail-amer.sun.com>; Mon,
 13 Apr 2009 14:47:58 -0600 (MDT)
Date: Mon, 13 Apr 2009 13:47:01 -0700
From: John Fischer <John.Fischer@sun.com>
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
Sender: John.Fischer@sun.com
To: Mark Carlson <markcarl@sac.sfbay.sun.com>
Cc: LSARC-ext@sun.com, Vivek.Titarmare@sun.com
Reply-to: John.Fischer@sun.com
Message-id: <49E3A4C5.2050701@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
User-Agent: Thunderbird 2.0.0.21 (X11/20090323)
Status: RO
Content-Length: 3051

Vivek,

usr/local/bin is not the correct location for binaries on
Open Solaris or Solaris.  Please specify a more appropriate
directory.

Thanks,

John


Mark Carlson wrote:
> I am sponsoring this familiarity case for Vivek Titarmare, requesting minor binding and timing out 04/20/2009.
> 
> -- mark
> 
> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
> This information is Copyright 2009 Sun Microsystems
> 1. Introduction
>     1.1. Project/Component Working Name:
> 	 pdsh Ver 2.18
>     1.2. Name of Document Author/Supplier:
> 	 Author:  Vivek Titarmare
>     1.3  Date of This Document:
> 	13 April, 2009
> 
> 2. Project Summary
>    2.1 Project Description
> 
> 	Parallel command execution for clusters
> 
> 4. Technical Description:
> 
> 	Pdsh is a high-performance, parallel remote shell utility. It has built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and can call SSH externally (though with reduced performance). Pdsh uses a "sliding window" parallel algorithm to conserve socket resources on the initiating node and to allow progress to continue while timeouts occur on some connections.
> 	
> 	Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which runs commands on a single remote host, pdsh can run multiple remote commands in parallel. pdsh uses a "sliding window" (or fanout) of threads to conserve resources on the the initiating host while allowing some connections to time out. 	
> 
> 5. Interfaces 
> 
> 	The binary file "pdsh" contains following interface.
> 
>    Exported interface                   Classification 		Interface type
>    =============================        ============== 		==============
> 	pdsh-rcmd-rsh			Committed     		requires rshd server running on remote nodes
> 	pdsh-rmcd-ssh			Committed 		requires ssh installed, sshd on remote nodes
> 	pdsh-rcmd-mrsh			Committed 		requires munge 
> 	pdsh-rcmd-qshell		Committed 		requires qsnet, pdsh-qshd (qshell server)
> 	pdsh-rcmd-mqshell		Committed 		requires qsnet, munge, pdsh-mqshd (mqshell server)
> 	pdsh-rcmd-xcpu			Committed 		requires XCPU service mounted on /mnt/xcpu/<hostname>/xcpu
> 	pdsh-mod-genders		Uncommitted		requires libgenders
> 	pdsh-mod-nodeattr		Uncommitted		requires nodeattr program
> 	pdsh-mod-nodeupdown		Uncommitted		requires libnodeupdown
> 	pdsh-mod-machines		Uncommitted		None
> 	pdsh-mod-rms			Uncommitted		requires RMS: rmsquery, qsrmslibs
> 	pdsh-mod-slurm			Uncommitted		requires slurm
> 	pdsh-mod-dshgroup		Uncommitted		None
> 	pdsh-mod-netgroup		Uncommitted		None	
> 	
> 
>    Imported interface        Classification   Comments
>    =======================   ==============   =================================== 
> 	None
> 
>    The binary file would go in "usr/local/bin"
> 
> 
> 6. Resources and Schedule
>     6.4. Steering Committee requested information
>    	6.4.1. Consolidation C-team Name:
> 		SFW
>     6.5. ARC review type: FastTrack
>     6.6. ARC Exposure: open
> 
> _______________________________________________
> opensolaris-arc mailing list
> opensolaris-arc@opensolaris.org

From danek.duvall@sun.com Mon Apr 13 13:52:21 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3DKqJME026694
	for <LSARC-ext@sac.SFBay.Sun.COM>; Mon, 13 Apr 2009 13:52:19 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3DKqI39012392
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Mon, 13 Apr 2009 21:52:18 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI200F014N6QZ00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Mon, 13 Apr 2009 13:52:18 -0700 (PDT)
Received: from dm-sfbay-01.sfbay.sun.com ([129.145.155.118])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI2003WB4N5VQA0@nwk-avmta-2.sfbay.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon,
 13 Apr 2009 13:52:17 -0700 (PDT)
Received: from mumak.SFBay.Sun.COM (mumak.SFBay.Sun.COM [129.146.229.4])
	by dm-sfbay-01.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2)
 with ESMTP id n3DKqGVn029686; Mon, 13 Apr 2009 13:52:16 -0700 (PDT)
Received: from mumak.SFBay.Sun.COM (loghost [127.0.0.1])
	by mumak.SFBay.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id n3DKscEX009965; Mon,
 13 Apr 2009 13:54:38 -0700 (PDT)
Received: (from dduvall@localhost)
	by mumak.SFBay.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n3DKsaW1009964; Mon,
 13 Apr 2009 13:54:36 -0700 (PDT)
Date: Mon, 13 Apr 2009 13:54:36 -0700
From: Danek Duvall <danek.duvall@sun.com>
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
To: Mark Carlson <markcarl@sac.sfbay.sun.com>
Cc: LSARC-ext@sun.com, Vivek.Titarmare@sun.com
Message-id: <20090413205436.GX7978@mumak.SFBay.Sun.COM>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
User-Agent: Mutt/1.5.16 (2007-06-27)
Status: RO
Content-Length: 2487

On Mon, Apr 13, 2009 at 01:41:13PM -0700, Mark Carlson wrote:

> 4. Technical Description:
> 
> 	Pdsh is a high-performance, parallel remote shell utility. It has
> 	built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and
> 	can call SSH externally (though with reduced performance). Pdsh
> 	uses a "sliding window" parallel algorithm to conserve socket
> 	resources on the initiating node and to allow progress to continue
> 	while timeouts occur on some connections.
> 	
> 	Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which runs
> 	commands on a single remote host, pdsh can run multiple remote
> 	commands in parallel. pdsh uses a "sliding window" (or fanout) of
> 	threads to conserve resources on the the initiating host while
> 	allowing some connections to time out. 	

Does "pdsh" default to either rsh or ssh?

> 5. Interfaces 
> 
> 	The binary file "pdsh" contains following interface.
> 
>    Exported interface                   Classification 		Interface type
>    =============================        ============== 		==============
> 	pdsh-rcmd-rsh			Committed     		requires rshd server running on remote nodes
> 	pdsh-rmcd-ssh			Committed 		requires ssh installed, sshd on remote nodes
> 	pdsh-rcmd-mrsh			Committed 		requires munge 
> 	pdsh-rcmd-qshell		Committed 		requires qsnet, pdsh-qshd (qshell server)
> 	pdsh-rcmd-mqshell		Committed 		requires qsnet, munge, pdsh-mqshd (mqshell server)
> 	pdsh-rcmd-xcpu			Committed 		requires XCPU service mounted on /mnt/xcpu/<hostname>/xcpu

Are munge, qsnet, and the XCPU service exported by another case not
mentiond here?

> 	pdsh-mod-genders		Uncommitted		requires libgenders
> 	pdsh-mod-nodeattr		Uncommitted		requires nodeattr program
> 	pdsh-mod-nodeupdown		Uncommitted		requires libnodeupdown
> 	pdsh-mod-machines		Uncommitted		None
> 	pdsh-mod-rms			Uncommitted		requires RMS: rmsquery, qsrmslibs
> 	pdsh-mod-slurm			Uncommitted		requires slurm
> 	pdsh-mod-dshgroup		Uncommitted		None
> 	pdsh-mod-netgroup		Uncommitted		None	

How about libgenders, nodeattr, libnodeupdown, rmsquery, qsrmslibs, or
slurm?

Are there any command line arguments?  Environment variables?  Are these
executables (I assume that's what they are) delivered in a package that has
a name?

>    Imported interface        Classification   Comments
>    =======================   ==============   =================================== 
> 	None
> 
>    The binary file would go in "usr/local/bin"

Um, no it wouldn't.

Danek

From carlsonj@phorcys.east.sun.com Mon Apr 13 13:58:19 2009
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3DKwJw7027425
	for <LSARC-ext@sac.sfbay.sun.com>; Mon, 13 Apr 2009 13:58:19 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3DKwHRv055224
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@Sun.Com>; Mon, 13 Apr 2009 14:58:19 -0600 (MDT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI20020N4X7YO00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@Sun.Com
 (ORCPT LSARC-ext@Sun.Com); Mon, 13 Apr 2009 13:58:19 -0700 (PDT)
Received: from dm-east-02.east.sun.com ([129.148.13.5])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI200LY24X5TC50@nwk-avmta-1.sfbay.Sun.COM> for
 LSARC-ext@Sun.Com (ORCPT LSARC-ext@Sun.Com); Mon,
 13 Apr 2009 13:58:18 -0700 (PDT)
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by dm-east-02.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2)
 with ESMTP id n3DKwGql060537; Mon, 13 Apr 2009 16:58:16 -0400 (EDT)
Received: from phorcys.east.sun.com (phorcys.local [127.0.0.1])
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n3DKvmjD011791; Mon,
 13 Apr 2009 16:57:48 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n3DKvlgQ011788; Mon,
 13 Apr 2009 16:57:47 -0400 (EDT)
Date: Mon, 13 Apr 2009 16:57:47 -0400
From: James Carlson <james.d.carlson@sun.com>
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
To: Mark Carlson <markcarl@sac.sfbay.sun.com>
Cc: LSARC-ext@sun.com, Vivek.Titarmare@sun.com
Message-id: <18915.42827.953599.223359@gargle.gargle.HOWL>
MIME-version: 1.0
X-Mailer: VM 7.01 under Emacs 21.3.1
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
Status: RO
Content-Length: 631

Mark Carlson writes:
> 	pdsh-rcmd-xcpu			Committed 		requires XCPU service mounted on /mnt/xcpu/<hostname>/xcpu

What is /mnt/xcpu?

> 	pdsh-mod-genders		Uncommitted		requires libgenders
> 	pdsh-mod-nodeupdown		Uncommitted		requires libnodeupdown

Do these things exist on Solaris or OpenSolaris?  (Missing case
dependencies?)

>    The binary file would go in "usr/local/bin"

As John Fischer noted, "no."

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

From Nicolas.Williams@sun.com Mon Apr 13 13:59:29 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3DKxSMv027618
	for <LSARC-ext@sac.sfbay.sun.com>; Mon, 13 Apr 2009 13:59:29 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3DKxO2w016723;
	Mon, 13 Apr 2009 21:59:26 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI200G0D4Z06300@nwk-avmta-2.sfbay.sun.com>; Mon,
 13 Apr 2009 13:59:24 -0700 (PDT)
Received: from binky.Central.Sun.COM ([129.153.128.104])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI2003QQ4YZVVB0@nwk-avmta-2.sfbay.sun.com>; Mon,
 13 Apr 2009 13:59:24 -0700 (PDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1])
	by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id n3DKvRGT010095;
 Mon, 13 Apr 2009 15:57:27 -0500 (CDT)
Received: (from nw141292@localhost)
	by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n3DKvRgo010094; Mon,
 13 Apr 2009 15:57:27 -0500 (CDT)
Date: Mon, 13 Apr 2009 15:57:27 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
To: Mark Carlson <markcarl@sac.sfbay.sun.com>
Cc: LSARC-ext@sun.com, Vivek.Titarmare@sun.com
Message-id: <20090413205727.GX1500@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
X-Authentication-warning: binky.Central.Sun.COM: nw141292 set sender to
 Nicolas.Williams@sun.com using -f
User-Agent: Mutt/1.5.7i
Status: RO
Content-Length: 2224

On Mon, Apr 13, 2009 at 01:41:13PM -0700, Mark Carlson wrote:
> 	Pdsh is a high-performance, parallel remote shell utility. It
> 	has built-in, thread-safe clients for Berkeley and Kerberos V4
> 	rsh and can call SSH externally (though with reduced
> 	performance). Pdsh uses a "sliding window" parallel algorithm to
> 	conserve socket resources on the initiating node and to allow
> 	progress to continue while timeouts occur on some connections.

Kerberos V4??  Solaris does not support that, and also no one should be
using Kerberos V4.

I am not going to suggest using kcmd() (probably a private API) as that
too has its security problems.  Besides, you'd probably need an async
version of it.

I think use of ssh with the ConnectTimeout option is the best usage
option.  For those who don't care about security they can use the rsh
option.

> 	Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which
> 	runs commands on a single remote host, pdsh can run multiple
> 	remote commands in parallel. pdsh uses a "sliding window" (or
> 	fanout) of threads to conserve resources on the the initiating
> 	host while allowing some connections to time out. 	

Excellent.  (Compare to the recent shmux case...)

What are these:

> 	pdsh-rcmd-mrsh			Committed 		requires munge 
> 	pdsh-rcmd-qshell		Committed 		requires qsnet, pdsh-qshd (qshell server)
> 	pdsh-rcmd-mqshell		Committed 		requires qsnet, munge, pdsh-mqshd (mqshell server)
> 	pdsh-rcmd-xcpu			Committed 		requires XCPU service mounted on /mnt/xcpu/<hostname>/xcpu
> 	pdsh-mod-genders		Uncommitted		requires libgenders
> 	pdsh-mod-nodeattr		Uncommitted		requires nodeattr program
> 	pdsh-mod-nodeupdown		Uncommitted		requires libnodeupdown
> 	pdsh-mod-machines		Uncommitted		None
> 	pdsh-mod-rms			Uncommitted		requires RMS: rmsquery, qsrmslibs
> 	pdsh-mod-slurm			Uncommitted		requires slurm
> 	pdsh-mod-dshgroup		Uncommitted		None
> 	pdsh-mod-netgroup		Uncommitted		None	

Also, the manpage for pdsh talks about needing to be setuid-0 in order
to run pdsh-rcmd-qshell.  Are you planning on making pdsh setuid=0?  (I
hope not.)

>    The binary file would go in "usr/local/bin"

We don't put anything in /usr/local.  This needs to go into /usr/bin.

Nico
-- 

From Vivek.Titarmare@sun.com Mon Apr 13 22:20:49 2009
Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3E5Km8B003643
	for <LSARC-ext@sac.sfbay.sun.com>; Mon, 13 Apr 2009 22:20:49 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n3E5KkZL005963
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 14 Apr 2009 13:20:47 +0800 (SGT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI20050PS6LXN00@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Mon, 13 Apr 2009 23:20:46 -0600 (MDT)
Received: from sineb-mail-1.sun.com ([192.18.19.6])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI20004BS6KCMA0@brm-avmta-1.central.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Mon,
 13 Apr 2009 23:20:45 -0600 (MDT)
Received: from fe-apac-06.sun.com
 (fe-apac-06.sun.com [192.18.19.177] (may be forged))
	by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3E5Kipg011187	for
 <LSARC-ext@sun.com>; Tue, 14 Apr 2009 05:20:44 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KI200N00S514100@mail-apac.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 14 Apr 2009 13:20:44 +0800 (SGT)
Received: from VivekTPC ([unknown] [129.150.146.167])
 by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit
 (built Feb 19 2009)) with ESMTPSA id <0KI2009TIS6HJ6L0@mail-apac.sun.com>; Tue,
 14 Apr 2009 13:20:44 +0800 (SGT)
Date: Tue, 14 Apr 2009 10:50:40 +0530
From: Vivek Titarmare <Vivek.Titarmare@sun.com>
Subject: RE: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <49E3A4C5.2050701@sun.com>
Sender: Vivek.Titarmare@sun.com
To: John.Fischer@sun.com, "'Mark Carlson'" <markcarl@sac.sfbay.sun.com>
Cc: LSARC-ext@sun.com
Message-id: <009101c9bcc0$c26c4cf0$4744e6d0$%Titarmare@Sun.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: Acm8eSEma3LuFBlPTeKuCGoEuZgm1QAR3H6g
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
 <49E3A4C5.2050701@sun.com>
Status: RO
Content-Length: 3418

Hi John,

Would /usr/bin be the correct location for the binaries.

Pl. suggest.

Thanks,
~Vivek R. Titarmare

-----Original Message-----
From: John.Fischer@Sun.COM [mailto:John.Fischer@Sun.COM] 
Sent: Tuesday, April 14, 2009 2:17 AM
To: Mark Carlson
Cc: LSARC-ext@sun.com; Vivek.Titarmare@Sun.COM
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]

Vivek,

usr/local/bin is not the correct location for binaries on
Open Solaris or Solaris.  Please specify a more appropriate
directory.

Thanks,

John


Mark Carlson wrote:
> I am sponsoring this familiarity case for Vivek Titarmare, requesting
minor binding and timing out 04/20/2009.
> 
> -- mark
> 
> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
> This information is Copyright 2009 Sun Microsystems
> 1. Introduction
>     1.1. Project/Component Working Name:
> 	 pdsh Ver 2.18
>     1.2. Name of Document Author/Supplier:
> 	 Author:  Vivek Titarmare
>     1.3  Date of This Document:
> 	13 April, 2009
> 
> 2. Project Summary
>    2.1 Project Description
> 
> 	Parallel command execution for clusters
> 
> 4. Technical Description:
> 
> 	Pdsh is a high-performance, parallel remote shell utility. It has
built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and can call
SSH externally (though with reduced performance). Pdsh uses a "sliding
window" parallel algorithm to conserve socket resources on the initiating
node and to allow progress to continue while timeouts occur on some
connections.
> 	
> 	Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which runs
commands on a single remote host, pdsh can run multiple remote commands in
parallel. pdsh uses a "sliding window" (or fanout) of threads to conserve
resources on the the initiating host while allowing some connections to time
out. 	
> 
> 5. Interfaces 
> 
> 	The binary file "pdsh" contains following interface.
> 
>    Exported interface                   Classification
Interface type
>    =============================        ==============
==============
> 	pdsh-rcmd-rsh			Committed     		requires
rshd server running on remote nodes
> 	pdsh-rmcd-ssh			Committed 		requires ssh
installed, sshd on remote nodes
> 	pdsh-rcmd-mrsh			Committed 		requires
munge 
> 	pdsh-rcmd-qshell		Committed 		requires
qsnet, pdsh-qshd (qshell server)
> 	pdsh-rcmd-mqshell		Committed 		requires
qsnet, munge, pdsh-mqshd (mqshell server)
> 	pdsh-rcmd-xcpu			Committed 		requires
XCPU service mounted on /mnt/xcpu/<hostname>/xcpu
> 	pdsh-mod-genders		Uncommitted		requires
libgenders
> 	pdsh-mod-nodeattr		Uncommitted		requires
nodeattr program
> 	pdsh-mod-nodeupdown		Uncommitted		requires
libnodeupdown
> 	pdsh-mod-machines		Uncommitted		None
> 	pdsh-mod-rms			Uncommitted		requires
RMS: rmsquery, qsrmslibs
> 	pdsh-mod-slurm			Uncommitted		requires
slurm
> 	pdsh-mod-dshgroup		Uncommitted		None
> 	pdsh-mod-netgroup		Uncommitted		None	
> 	
> 
>    Imported interface        Classification   Comments
>    =======================   ==============
=================================== 
> 	None
> 
>    The binary file would go in "usr/local/bin"
> 
> 
> 6. Resources and Schedule
>     6.4. Steering Committee requested information
>    	6.4.1. Consolidation C-team Name:
> 		SFW
>     6.5. ARC review type: FastTrack
>     6.6. ARC Exposure: open
> 
> _______________________________________________
> opensolaris-arc mailing list
> opensolaris-arc@opensolaris.org


From John.Fischer@sun.com Tue Apr 14 06:29:20 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3EDTJLZ004561
	for <LSARC-ext@sac.sfbay.sun.com>; Tue, 14 Apr 2009 06:29:20 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3EDTGlO010177
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 14 Apr 2009 14:29:18 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI300909ESTDT00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 14 Apr 2009 06:29:17 -0700 (PDT)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI3000JAESTN970@nwk-avmta-2.sfbay.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue,
 14 Apr 2009 06:29:17 -0700 (PDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3EDTGae007626	for
 <LSARC-ext@sun.com>; Tue, 14 Apr 2009 13:29:16 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KI300B00EMZWX00@mail-amer.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 14 Apr 2009 07:29:16 -0600 (MDT)
Received: from [192.168.10.7] ([unknown] [76.20.56.47])
 by mail-amer.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit
 (built Feb 19 2009)) with ESMTPSA id <0KI300023ESOBJC0@mail-amer.sun.com>; Tue,
 14 Apr 2009 07:29:12 -0600 (MDT)
Date: Tue, 14 Apr 2009 06:28:15 -0700
From: John Fischer <John.Fischer@sun.com>
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <009101c9bcc0$c26c4cf0$4744e6d0$%Titarmare@Sun.com>
Sender: John.Fischer@sun.com
To: Vivek Titarmare <Vivek.Titarmare@sun.com>
Cc: "'Mark Carlson'" <markcarl@sac.sfbay.sun.com>, LSARC-ext@sun.com
Reply-to: John.Fischer@sun.com
Message-id: <49E48F6F.4070809@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
 <49E3A4C5.2050701@sun.com> <009101c9bcc0$c26c4cf0$4744e6d0$%Titarmare@Sun.com>
User-Agent: Thunderbird 2.0.0.21 (X11/20090323)
Status: RO
Content-Length: 3676

Vivek,

Yes.  /usr/bin is the correct location for the
installation.

Thanks,

John

Vivek Titarmare wrote:
> Hi John,
> 
> Would /usr/bin be the correct location for the binaries.
> 
> Pl. suggest.
> 
> Thanks,
> ~Vivek R. Titarmare
> 
> -----Original Message-----
> From: John.Fischer@Sun.COM [mailto:John.Fischer@Sun.COM] 
> Sent: Tuesday, April 14, 2009 2:17 AM
> To: Mark Carlson
> Cc: LSARC-ext@sun.com; Vivek.Titarmare@Sun.COM
> Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
> 
> Vivek,
> 
> usr/local/bin is not the correct location for binaries on
> Open Solaris or Solaris.  Please specify a more appropriate
> directory.
> 
> Thanks,
> 
> John
> 
> 
> Mark Carlson wrote:
>> I am sponsoring this familiarity case for Vivek Titarmare, requesting
> minor binding and timing out 04/20/2009.
>> -- mark
>>
>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
>> This information is Copyright 2009 Sun Microsystems
>> 1. Introduction
>>     1.1. Project/Component Working Name:
>> 	 pdsh Ver 2.18
>>     1.2. Name of Document Author/Supplier:
>> 	 Author:  Vivek Titarmare
>>     1.3  Date of This Document:
>> 	13 April, 2009
>>
>> 2. Project Summary
>>    2.1 Project Description
>>
>> 	Parallel command execution for clusters
>>
>> 4. Technical Description:
>>
>> 	Pdsh is a high-performance, parallel remote shell utility. It has
> built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and can call
> SSH externally (though with reduced performance). Pdsh uses a "sliding
> window" parallel algorithm to conserve socket resources on the initiating
> node and to allow progress to continue while timeouts occur on some
> connections.
>> 	
>> 	Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which runs
> commands on a single remote host, pdsh can run multiple remote commands in
> parallel. pdsh uses a "sliding window" (or fanout) of threads to conserve
> resources on the the initiating host while allowing some connections to time
> out. 	
>> 5. Interfaces 
>>
>> 	The binary file "pdsh" contains following interface.
>>
>>    Exported interface                   Classification
> Interface type
>>    =============================        ==============
> ==============
>> 	pdsh-rcmd-rsh			Committed     		requires
> rshd server running on remote nodes
>> 	pdsh-rmcd-ssh			Committed 		requires ssh
> installed, sshd on remote nodes
>> 	pdsh-rcmd-mrsh			Committed 		requires
> munge 
>> 	pdsh-rcmd-qshell		Committed 		requires
> qsnet, pdsh-qshd (qshell server)
>> 	pdsh-rcmd-mqshell		Committed 		requires
> qsnet, munge, pdsh-mqshd (mqshell server)
>> 	pdsh-rcmd-xcpu			Committed 		requires
> XCPU service mounted on /mnt/xcpu/<hostname>/xcpu
>> 	pdsh-mod-genders		Uncommitted		requires
> libgenders
>> 	pdsh-mod-nodeattr		Uncommitted		requires
> nodeattr program
>> 	pdsh-mod-nodeupdown		Uncommitted		requires
> libnodeupdown
>> 	pdsh-mod-machines		Uncommitted		None
>> 	pdsh-mod-rms			Uncommitted		requires
> RMS: rmsquery, qsrmslibs
>> 	pdsh-mod-slurm			Uncommitted		requires
> slurm
>> 	pdsh-mod-dshgroup		Uncommitted		None
>> 	pdsh-mod-netgroup		Uncommitted		None	
>> 	
>>
>>    Imported interface        Classification   Comments
>>    =======================   ==============
> =================================== 
>> 	None
>>
>>    The binary file would go in "usr/local/bin"
>>
>>
>> 6. Resources and Schedule
>>     6.4. Steering Committee requested information
>>    	6.4.1. Consolidation C-team Name:
>> 		SFW
>>     6.5. ARC review type: FastTrack
>>     6.6. ARC Exposure: open
>>
>> _______________________________________________
>> opensolaris-arc mailing list
>> opensolaris-arc@opensolaris.org
> 

From sacadmin Tue Apr 14 09:54:39 2009
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3EGsdq4006410
	for <lsarc@sac.eng.sun.com>; Tue, 14 Apr 2009 09:54:39 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3EGsSXW043501;
	Tue, 14 Apr 2009 10:54:37 -0600 (MDT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI300K0POB0NP00@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 14 Apr 2009 09:54:36 -0700 (PDT)
Received: from binky.Central.Sun.COM ([129.153.128.104])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI300CR5OAZ6G80@nwk-avmta-1.sfbay.Sun.COM>; Tue,
 14 Apr 2009 09:54:36 -0700 (PDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1])
	by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id n3EGqcm8010613;
 Tue, 14 Apr 2009 11:52:38 -0500 (CDT)
Received: (from nw141292@localhost)
	by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n3EGqclG010612; Tue,
 14 Apr 2009 11:52:38 -0500 (CDT)
Date: Tue, 14 Apr 2009 11:52:38 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
To: Mark Carlson <markcarl@sac.sfbay.sun.com>
Cc: LSARC@sun.com, Vivek.Titarmare@sun.com
Message-id: <20090414165238.GW1500@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
X-Authentication-warning: binky.Central.Sun.COM: nw141292 set sender to
 Nicolas.Williams@sun.com using -f
User-Agent: Mutt/1.5.7i
Status: RO
Content-Length: 596

[-ext removed.]

BTW, pdsh is in /pending.  Now, OpenSolaris is not yet a product in the
ARC sense, so the fact that pdsh is in /pending and could be promoted to
/contrib is irrelevant to the ARC for the time being.  Promotions from
/contrib to /pending without doing SVR4 packaging will surely not be on
the table until Nevada is retired and replaced by OpenSolaris and IPS.

However, the i-team might wish to reconsider whether to integrate until
Nevada is retired, particularly for things which are in /pending or,
better, in /contrib.  I'm not sure that I'd encourage you to do so.

Nico
-- 

From sacadmin Wed Apr 15 09:02:27 2009
Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3FG2PoP018880
	for <lsarc@sac.eng.sun.com>; Wed, 15 Apr 2009 09:02:25 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n3FG2NgV013027
	for <@sunmail2sca.sfbay.sun.com:LSARC@sun.com>; Thu, 16 Apr 2009 00:02:24 +0800 (SGT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI500917GJYM500@brm-avmta-1.central.sun.com> for LSARC@sun.com
 (ORCPT LSARC@sun.com); Wed, 15 Apr 2009 10:02:22 -0600 (MDT)
Received: from sineb-mail-2.sun.com ([192.18.19.7])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI5008ESGJXLK10@brm-avmta-1.central.sun.com> for LSARC@sun.com
 (ORCPT LSARC@sun.com); Wed, 15 Apr 2009 10:02:22 -0600 (MDT)
Received: from fe-apac-05.sun.com
 (fe-apac-05.sun.com [192.18.19.176] (may be forged))
	by sineb-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3FG2LpF016849	for
 <LSARC@sun.com>; Wed, 15 Apr 2009 16:02:21 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KI500400GDV8C00@mail-apac.sun.com> for LSARC@sun.com
 (ORCPT LSARC@sun.com); Thu, 16 Apr 2009 00:02:21 +0800 (SGT)
Received: from VivekTPC ([unknown] [121.246.32.25])
 by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit
 (built Feb 19 2009)) with ESMTPSA id <0KI50082RGJT0IG0@mail-apac.sun.com>; Thu,
 16 Apr 2009 00:02:21 +0800 (SGT)
Date: Wed, 15 Apr 2009 21:32:18 +0530
From: Vivek Titarmare <Vivek.Titarmare@Sun.COM>
Subject: RE: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <20090414165238.GW1500@Sun.COM>
Sender: Vivek.Titarmare@Sun.COM
To: "'Nicolas Williams'" <Nicolas.Williams@Sun.COM>,
        "'Mark Carlson'" <markcarl@sac.sfbay.sun.com>
Cc: LSARC@Sun.COM
Message-id: <002c01c9bde3$9011a0b0$b034e210$%Titarmare@Sun.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: Acm9IbOCTVyNYFqVTAq/CjOJn3zkEQAwYsCA
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
 <20090414165238.GW1500@Sun.COM>
Status: RO
Content-Length: 1183

Hi Nicolas,

As far as  our understanding is this case is promoting pdsh to /dev (via SFW
consolidation) with the intention that it be put in /release at some point
in the future. Therefore superseding the /pending version - which would be
removed.

Let me know if we can do something else in this case.

Regards,
~Vivek R. T.

-----Original Message-----
From: Nicolas Williams [mailto:Nicolas.Williams@Sun.COM] 
Sent: Tuesday, April 14, 2009 10:23 PM
To: Mark Carlson
Cc: LSARC@sun.com; Vivek.Titarmare@Sun.COM
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]

[-ext removed.]

BTW, pdsh is in /pending.  Now, OpenSolaris is not yet a product in the
ARC sense, so the fact that pdsh is in /pending and could be promoted to
/contrib is irrelevant to the ARC for the time being.  Promotions from
/contrib to /pending without doing SVR4 packaging will surely not be on
the table until Nevada is retired and replaced by OpenSolaris and IPS.

However, the i-team might wish to reconsider whether to integrate until
Nevada is retired, particularly for things which are in /pending or,
better, in /contrib.  I'm not sure that I'd encourage you to do so.

Nico
-- 


From sacadmin Wed Apr 15 11:45:08 2009
Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3FIj8m6028424
	for <lsarc@sac.eng.sun.com>; Wed, 15 Apr 2009 11:45:08 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3FIj3mK000775
	for <@sunmail2sca.sfbay.sun.com:LSARC@sun.com>; Wed, 15 Apr 2009 11:45:07 -0700 (PDT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI50020TO36FJ00@brm-avmta-1.central.sun.com> for LSARC@sun.com
 (ORCPT LSARC@Sun.COM); Wed, 15 Apr 2009 12:45:06 -0600 (MDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI500LV6O35T960@brm-avmta-1.central.sun.com> for LSARC@sun.com
 (ORCPT LSARC@Sun.COM); Wed, 15 Apr 2009 12:45:05 -0600 (MDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3FIj5iV019310	for
 <LSARC@Sun.COM>; Wed, 15 Apr 2009 18:45:05 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KI500900N1UJY00@mail-amer.sun.com> for LSARC@Sun.COM
 (ORCPT LSARC@Sun.COM); Wed, 15 Apr 2009 12:45:05 -0600 (MDT)
Received: from c-67-177-232-31.hsd1.co.comcast.net ([unknown] [129.150.35.255])
 by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 with ESMTPSA id <0KI500M3XO2D9B00@mail-amer.sun.com> for LSARC@Sun.COM
 (ORCPT LSARC@Sun.COM); Wed, 15 Apr 2009 12:44:38 -0600 (MDT)
Date: Wed, 15 Apr 2009 12:44:37 -0600
From: Jim Walker <James.Walker@sun.com>
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <002c01c9bde3$9011a0b0$b034e210$%Titarmare@Sun.com>
Sender: James.Walker@sun.com
To: Vivek Titarmare <Vivek.Titarmare@sun.com>
Cc: LSARC@sun.com, Nicolas Williams <Nicolas.Williams@sun.com>
Reply-to: James.Walker@sun.com
Message-id: <49E62B15.2010707@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
 <20090414165238.GW1500@Sun.COM>
 <002c01c9bde3$9011a0b0$b034e210$%Titarmare@Sun.com>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
Status: RO
Content-Length: 588

Vivek Titarmare wrote:
> Hi Nicolas,
> 
> As far as  our understanding is this case is promoting pdsh to /dev (via SFW
> consolidation) with the intention that it be put in /release at some point
> in the future. Therefore superseding the /pending version - which would be
> removed.

Right. once pdsh is in /dev via the SFW consolidation, we can look at
removing it from the pkg.opensolaris.org/pending repo. But, the pending
repo and any repo for that matter isn't an arc concern.

If a BU wants to port an open source pkg into Solaris/OpenSolaris that's
what's important.

Cheers,
Jim

From sacadmin Wed Apr 15 11:51:08 2009
Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3FIp7mp028572
	for <lsarc@sac.eng.sun.com>; Wed, 15 Apr 2009 11:51:08 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n3FIojBf023172;
	Thu, 16 Apr 2009 02:51:04 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI50090ROD2IO00@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 15 Apr 2009 11:51:02 -0700 (PDT)
Received: from binky.Central.Sun.COM ([129.153.128.104])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI500FC6OD1DVC0@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 15 Apr 2009 11:51:02 -0700 (PDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1])
	by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id n3FIn7N6011820;
 Wed, 15 Apr 2009 13:49:07 -0500 (CDT)
Received: (from nw141292@localhost)
	by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n3FIn7fA011819; Wed,
 15 Apr 2009 13:49:07 -0500 (CDT)
Date: Wed, 15 Apr 2009 13:49:07 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <49E62B15.2010707@sun.com>
To: Jim Walker <James.Walker@sun.com>
Cc: Vivek Titarmare <Vivek.Titarmare@sun.com>, LSARC@sun.com
Message-id: <20090415184906.GX1500@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
 <20090414165238.GW1500@Sun.COM>
 <002c01c9bde3$9011a0b0$b034e210$%Titarmare@Sun.com> <49E62B15.2010707@sun.com>
X-Authentication-warning: binky.Central.Sun.COM: nw141292 set sender to
 Nicolas.Williams@sun.com using -f
User-Agent: Mutt/1.5.7i
Status: RO
Content-Length: 1203

On Wed, Apr 15, 2009 at 12:44:37PM -0600, Jim Walker wrote:
> Vivek Titarmare wrote:
> >Hi Nicolas,
> >
> >As far as  our understanding is this case is promoting pdsh to /dev (via 
> >SFW
> >consolidation) with the intention that it be put in /release at some point
> >in the future. Therefore superseding the /pending version - which would be
> >removed.
> 
> Right. once pdsh is in /dev via the SFW consolidation, we can look at
> removing it from the pkg.opensolaris.org/pending repo. But, the pending
> repo and any repo for that matter isn't an arc concern.
> 
> If a BU wants to port an open source pkg into Solaris/OpenSolaris that's
> what's important.

My point was this: if something's in /pending or /contrib then the move
to /dev and /release *TODAY* requires integrating into a consolidation
that produces SVR4 packaging.

At some point in the future that will no longer be the case, which
should make the /contrib -> /dev move much easier on the developer -- a
toggle flip vs. re-doing build and packaging work.  THEREFORE it might
be a better use of the developer's time to work on software that's NOT
already in any of /pending, /contrib, /dev or /release.  That was my
point.

Nico
-- 

From sacadmin Wed Apr 15 12:19:06 2009
Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3FJJ6PQ025176
	for <lsarc@sac.eng.sun.com>; Wed, 15 Apr 2009 12:19:06 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3FJJ3J8020150
	for <@sunmail2sca.sfbay.sun.com:LSARC@sun.com>; Wed, 15 Apr 2009 12:19:05 -0700 (PDT)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI50050XPNTSX00@brm-avmta-1.central.sun.com> for LSARC@sun.com
 (ORCPT LSARC@Sun.COM); Wed, 15 Apr 2009 13:19:05 -0600 (MDT)
Received: from brmea-mail-1.sun.com ([192.18.98.31])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI500LG8PNLT7B0@brm-avmta-1.central.sun.com> for LSARC@sun.com
 (ORCPT LSARC@Sun.COM); Wed, 15 Apr 2009 13:18:57 -0600 (MDT)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3FJIvio029720	for
 <LSARC@Sun.COM>; Wed, 15 Apr 2009 19:18:57 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KI500200P29IT00@mail-amer.sun.com> for LSARC@Sun.COM
 (ORCPT LSARC@Sun.COM); Wed, 15 Apr 2009 13:18:57 -0600 (MDT)
Received: from boulder-dhcp-216.Central.Sun.COM ([unknown] [172.20.24.216])
 by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 with ESMTPSA id <0KI50000ZPNFZY60@mail-amer.sun.com> for LSARC@Sun.COM
 (ORCPT LSARC@Sun.COM); Wed, 15 Apr 2009 13:18:51 -0600 (MDT)
Date: Wed, 15 Apr 2009 13:18:48 -0600
From: "Mark A. Carlson" <Mark.Carlson@sun.com>
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <20090415184906.GX1500@Sun.COM>
Sender: Mark.Carlson@sun.com
To: Nicolas Williams <Nicolas.Williams@sun.com>
Cc: Jim Walker <James.Walker@sun.com>,
        Vivek Titarmare <Vivek.Titarmare@sun.com>, LSARC@sun.com
Message-id: <49E63318.1010809@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
 <20090414165238.GW1500@Sun.COM>
 <002c01c9bde3$9011a0b0$b034e210$%Titarmare@Sun.com> <49E62B15.2010707@sun.com>
 <20090415184906.GX1500@Sun.COM>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
Status: RO
Content-Length: 532

Nicolas Williams wrote:
>
> At some point in the future that will no longer be the case, which
> should make the /contrib -> /dev move much easier on the developer -- a
> toggle flip vs. re-doing build and packaging work.  THEREFORE it might
> be a better use of the developer's time to work on software that's NOT
> already in any of /pending, /contrib, /dev or /release.  That was my
> point.
>   
I would hope this still involves ARC review to flip the toggle...
If my assumption is true, this case is not wasted work.

-- mark


From sacadmin Wed Apr 15 13:43:08 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3FKh7d2027008
	for <lsarc@sac.eng.sun.com>; Wed, 15 Apr 2009 13:43:07 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3FKh16j005481;
	Wed, 15 Apr 2009 21:43:03 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI50010HTJRRV00@nwk-avmta-2.sfbay.sun.com>; Wed,
 15 Apr 2009 13:43:03 -0700 (PDT)
Received: from binky.Central.Sun.COM ([129.153.128.104])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI5000PFTJQUN10@nwk-avmta-2.sfbay.sun.com>; Wed,
 15 Apr 2009 13:43:02 -0700 (PDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1])
	by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id n3FKf7kb011865;
 Wed, 15 Apr 2009 15:41:07 -0500 (CDT)
Received: (from nw141292@localhost)
	by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n3FKf7tp011864; Wed,
 15 Apr 2009 15:41:07 -0500 (CDT)
Date: Wed, 15 Apr 2009 15:41:07 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <49E63318.1010809@sun.com>
To: "Mark A. Carlson" <Mark.Carlson@sun.com>
Cc: Jim Walker <James.Walker@sun.com>,
        Vivek Titarmare <Vivek.Titarmare@sun.com>, LSARC@sun.com
Message-id: <20090415204107.GB1500@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
 <20090414165238.GW1500@Sun.COM>
 <002c01c9bde3$9011a0b0$b034e210$%Titarmare@Sun.com> <49E62B15.2010707@sun.com>
 <20090415184906.GX1500@Sun.COM> <49E63318.1010809@sun.com>
X-Authentication-warning: binky.Central.Sun.COM: nw141292 set sender to
 Nicolas.Williams@sun.com using -f
User-Agent: Mutt/1.5.7i
Status: RO
Content-Length: 789

On Wed, Apr 15, 2009 at 01:18:48PM -0600, Mark A. Carlson wrote:
> Nicolas Williams wrote:
> >
> >At some point in the future that will no longer be the case, which
> >should make the /contrib -> /dev move much easier on the developer -- a
> >toggle flip vs. re-doing build and packaging work.  THEREFORE it might
> >be a better use of the developer's time to work on software that's NOT
> >already in any of /pending, /contrib, /dev or /release.  That was my
> >point.
> >  
> I would hope this still involves ARC review to flip the toggle...
> If my assumption is true, this case is not wasted work.

Indeed.  This case is not, but for the i-team integrating into, say,
SFW, before the switch from SVR4 packaging completes would be wasted
effort unless pdsh were needed _now_.

Nico
-- 

From sacadmin Wed Apr 15 13:48:22 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3FKmLqY027210
	for <lsarc@sac.eng.sun.com>; Wed, 15 Apr 2009 13:48:21 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3FKmEPc008252
	for <@sunmail2sca.sfbay.sun.com:LSARC@sun.com>; Wed, 15 Apr 2009 21:48:20 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI500201TSI2700@nwk-avmta-2.sfbay.sun.com> for LSARC@sun.com
 (ORCPT LSARC@sun.com); Wed, 15 Apr 2009 13:48:18 -0700 (PDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI5000A3TSHUH20@nwk-avmta-2.sfbay.sun.com> for LSARC@sun.com
 (ORCPT LSARC@sun.com); Wed, 15 Apr 2009 13:48:18 -0700 (PDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3FKmHTO020211	for
 <LSARC@sun.com>; Wed, 15 Apr 2009 20:48:17 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KI500G00SZGYL00@mail-amer.sun.com> for LSARC@sun.com
 (ORCPT LSARC@sun.com); Wed, 15 Apr 2009 14:48:17 -0600 (MDT)
Received: from boulder-dhcp-216.Central.Sun.COM ([unknown] [172.20.24.216])
 by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 with ESMTPSA id <0KI5006MZTS6OPA0@mail-amer.sun.com> for LSARC@sun.com
 (ORCPT LSARC@sun.com); Wed, 15 Apr 2009 14:48:06 -0600 (MDT)
Date: Wed, 15 Apr 2009 14:48:03 -0600
From: "Mark A. Carlson" <Mark.Carlson@sun.com>
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <20090415204107.GB1500@Sun.COM>
Sender: Mark.Carlson@sun.com
To: Nicolas Williams <Nicolas.Williams@sun.com>
Cc: Jim Walker <James.Walker@sun.com>,
        Vivek Titarmare <Vivek.Titarmare@sun.com>, LSARC@sun.com
Message-id: <49E64803.7030802@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_zcu6TT+/VSYSefwbURD5NQ)"
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
 <20090414165238.GW1500@Sun.COM>
 <002c01c9bde3$9011a0b0$b034e210$%Titarmare@Sun.com> <49E62B15.2010707@sun.com>
 <20090415184906.GX1500@Sun.COM> <49E63318.1010809@sun.com>
 <20090415204107.GB1500@Sun.COM>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
Status: RO
Content-Length: 2876

This is a multi-part message in MIME format.

--Boundary_(ID_zcu6TT+/VSYSefwbURD5NQ)
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

Nicolas Williams wrote:
> On Wed, Apr 15, 2009 at 01:18:48PM -0600, Mark A. Carlson wrote:
>   
>> Nicolas Williams wrote:
>>     
>>> At some point in the future that will no longer be the case, which
>>> should make the /contrib -> /dev move much easier on the developer -- a
>>> toggle flip vs. re-doing build and packaging work.  THEREFORE it might
>>> be a better use of the developer's time to work on software that's NOT
>>> already in any of /pending, /contrib, /dev or /release.  That was my
>>> point.
>>>  
>>>       
>> I would hope this still involves ARC review to flip the toggle...
>> If my assumption is true, this case is not wasted work.
>>     
>
> Indeed.  This case is not, but for the i-team integrating into, say,
> SFW, before the switch from SVR4 packaging completes would be wasted
> effort unless pdsh were needed _now_.
>   
This is not an architectural issue at this point. Until our management 
tells us
to stop and wait for this, we are proceeding as before.

-- mark


--Boundary_(ID_zcu6TT+/VSYSefwbURD5NQ)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Nicolas Williams wrote:
<blockquote cite="mid:20090415204107.GB1500@Sun.COM" type="cite">
  <pre wrap="">On Wed, Apr 15, 2009 at 01:18:48PM -0600, Mark A. Carlson wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">Nicolas Williams wrote:
    </pre>
    <blockquote type="cite">
      <pre wrap="">At some point in the future that will no longer be the case, which
should make the /contrib -&gt; /dev move much easier on the developer -- a
toggle flip vs. re-doing build and packaging work.  THEREFORE it might
be a better use of the developer's time to work on software that's NOT
already in any of /pending, /contrib, /dev or /release.  That was my
point.
 
      </pre>
    </blockquote>
    <pre wrap="">I would hope this still involves ARC review to flip the toggle...
If my assumption is true, this case is not wasted work.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Indeed.  This case is not, but for the i-team integrating into, say,
SFW, before the switch from SVR4 packaging completes would be wasted
effort unless pdsh were needed _now_.
  </pre>
</blockquote>
This is not an architectural issue at this point. Until our management
tells us<br>
to stop and wait for this, we are proceeding as before.<br>
<br>
-- mark<br>
<div class="moz-signature">
<div class="moz-signature"><br>
</div>
</div>
</body>
</html>

--Boundary_(ID_zcu6TT+/VSYSefwbURD5NQ)--

From sacadmin Wed Apr 15 13:57:43 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3FKvgRR027841
	for <lsarc@sac.eng.sun.com>; Wed, 15 Apr 2009 13:57:43 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3FKvIHZ013442;
	Wed, 15 Apr 2009 21:57:39 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI500201U823Z00@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 15 Apr 2009 13:57:38 -0700 (PDT)
Received: from binky.Central.Sun.COM ([129.153.128.104])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI500EH2U81PRB0@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 15 Apr 2009 13:57:38 -0700 (PDT)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1])
	by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id n3FKthW8011881;
 Wed, 15 Apr 2009 15:55:43 -0500 (CDT)
Received: (from nw141292@localhost)
	by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n3FKths1011880; Wed,
 15 Apr 2009 15:55:43 -0500 (CDT)
Date: Wed, 15 Apr 2009 15:55:43 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <49E64803.7030802@sun.com>
To: "Mark A. Carlson" <Mark.Carlson@sun.com>
Cc: Jim Walker <James.Walker@sun.com>,
        Vivek Titarmare <Vivek.Titarmare@sun.com>, LSARC@sun.com
Message-id: <20090415205543.GD1500@Sun.COM>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Content-disposition: inline
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
 <20090414165238.GW1500@Sun.COM>
 <002c01c9bde3$9011a0b0$b034e210$%Titarmare@Sun.com> <49E62B15.2010707@sun.com>
 <20090415184906.GX1500@Sun.COM> <49E63318.1010809@sun.com>
 <20090415204107.GB1500@Sun.COM> <49E64803.7030802@sun.com>
X-Authentication-warning: binky.Central.Sun.COM: nw141292 set sender to
 Nicolas.Williams@sun.com using -f
User-Agent: Mutt/1.5.7i
Status: RO
Content-Length: 480

On Wed, Apr 15, 2009 at 02:48:03PM -0600, Mark A. Carlson wrote:
> >Indeed.  This case is not, but for the i-team integrating into, say,
> >SFW, before the switch from SVR4 packaging completes would be wasted
> >effort unless pdsh were needed _now_.
> 
> This is not an architectural issue at this point. Until our management 
> tells us
> to stop and wait for this, we are proceeding as before.

Indeed, and I pointed that out in my first message on this.  It was
merely advice.

From margot.miller@sun.com Wed Apr 15 16:25:14 2009
Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3FNPDBd027908
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 15 Apr 2009 16:25:13 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3FNPBd8007829;
	Wed, 15 Apr 2009 17:25:11 -0600 (MDT)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KI600K0511ZY200@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 15 Apr 2009 16:25:11 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.63])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KI60066G11Y0CF0@nwk-avmta-1.sfbay.Sun.COM>; Wed,
 15 Apr 2009 16:25:10 -0700 (PDT)
Received: from [10.7.250.251]
 (punchin-client-10-7-250-251.SFBay.Sun.COM [10.7.250.251])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n3FNP9Uf366694; Wed, 15 Apr 2009 16:25:09 -0700 (PDT)
Date: Wed, 15 Apr 2009 16:20:19 -0700
From: Margot Miller <margot.miller@sun.com>
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
To: Mark Carlson <markcarl@sac.sfbay.sun.com>
Cc: LSARC-ext@sun.com, Vivek.Titarmare@sun.com
Message-id: <49E66BB3.6060008@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
User-Agent: Thunderbird 2.0b1 (X11/20070115)
Status: RO
Content-Length: 3710

According to the interface table, it looks like there is one
binary- pdsh, which will be /usr/local/pdsh.

The materials directory shows man pages for the following:

   dshbak
   pdcp
   rpdcp
   pdsh

Are the three top ones also being delivered by this project?

In the pdsh man page, there are a bunch of environment variables
that should be in the i/f table:

     PDSH_RCMD_TYPE
	 
     PDSH_SSH_ARGS
	  
     PDSH_SSH_ARGS_APPEND
	  
     WCOLL
	 
     DSHPATH
	
     FANOUT
	  
Also in the FOSS checklist there is the statement:

 "Since pdsh needs to run setuid root for qshell support."

Is this true?  And what is qshell?

There is mention of more environment variables listed in the
20 questions that are not in the i/f table:

  "QSHELL_REMOTE_LD_LIBRARY_PATH and QSHELL_REMOTE_LD_PREOPEN"


Thanks
Margot



Mark Carlson wrote:
> I am sponsoring this familiarity case for Vivek Titarmare, requesting minor binding and timing out 04/20/2009.
>
> -- mark
>
> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
> This information is Copyright 2009 Sun Microsystems
> 1. Introduction
>     1.1. Project/Component Working Name:
> 	 pdsh Ver 2.18
>     1.2. Name of Document Author/Supplier:
> 	 Author:  Vivek Titarmare
>     1.3  Date of This Document:
> 	13 April, 2009
>
> 2. Project Summary
>    2.1 Project Description
>
> 	Parallel command execution for clusters
>
> 4. Technical Description:
>
> 	Pdsh is a high-performance, parallel remote shell utility. It has built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and can call SSH externally (though with reduced performance). Pdsh uses a "sliding window" parallel algorithm to conserve socket resources on the initiating node and to allow progress to continue while timeouts occur on some connections.
> 	
> 	Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which runs commands on a single remote host, pdsh can run multiple remote commands in parallel. pdsh uses a "sliding window" (or fanout) of threads to conserve resources on the the initiating host while allowing some connections to time out. 	
>
> 5. Interfaces 
>
> 	The binary file "pdsh" contains following interface.
>
>    Exported interface                   Classification 		Interface type
>    =============================        ============== 		==============
> 	pdsh-rcmd-rsh			Committed     		requires rshd server running on remote nodes
> 	pdsh-rmcd-ssh			Committed 		requires ssh installed, sshd on remote nodes
> 	pdsh-rcmd-mrsh			Committed 		requires munge 
> 	pdsh-rcmd-qshell		Committed 		requires qsnet, pdsh-qshd (qshell server)
> 	pdsh-rcmd-mqshell		Committed 		requires qsnet, munge, pdsh-mqshd (mqshell server)
> 	pdsh-rcmd-xcpu			Committed 		requires XCPU service mounted on /mnt/xcpu/<hostname>/xcpu
> 	pdsh-mod-genders		Uncommitted		requires libgenders
> 	pdsh-mod-nodeattr		Uncommitted		requires nodeattr program
> 	pdsh-mod-nodeupdown		Uncommitted		requires libnodeupdown
> 	pdsh-mod-machines		Uncommitted		None
> 	pdsh-mod-rms			Uncommitted		requires RMS: rmsquery, qsrmslibs
> 	pdsh-mod-slurm			Uncommitted		requires slurm
> 	pdsh-mod-dshgroup		Uncommitted		None
> 	pdsh-mod-netgroup		Uncommitted		None	
> 	
>
>    Imported interface        Classification   Comments
>    =======================   ==============   =================================== 
> 	None
>
>    The binary file would go in "usr/local/bin"
>
>
> 6. Resources and Schedule
>     6.4. Steering Committee requested information
>    	6.4.1. Consolidation C-team Name:
> 		SFW
>     6.5. ARC review type: FastTrack
>     6.6. ARC Exposure: open
>
> _______________________________________________
> opensolaris-arc mailing list
> opensolaris-arc@opensolaris.org
>   


From Vivek.Titarmare@sun.com Tue Apr 21 04:14:05 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3LBE5Nn024590
	for <LSARC-ext@sac.sfbay.sun.com>; Tue, 21 Apr 2009 04:14:05 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3LBE3kE016211
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 21 Apr 2009 12:14:04 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KIG0000377EJD00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 21 Apr 2009 04:14:02 -0700 (PDT)
Received: from sineb-mail-1.sun.com ([192.18.19.6])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KIG00HQ677CL850@nwk-avmta-2.sfbay.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue,
 21 Apr 2009 04:14:01 -0700 (PDT)
Received: from fe-apac-05.sun.com
 (fe-apac-05.sun.com [192.18.19.176] (may be forged))
	by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3LBE0x6029467	for
 <LSARC-ext@sun.com>; Tue, 21 Apr 2009 11:14:00 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KIG00E006QMXM00@mail-apac.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 21 Apr 2009 19:14:00 +0800 (SGT)
Received: from VivekTPC ([unknown] [129.150.146.12])
 by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit
 (built Feb 19 2009)) with ESMTPSA id <0KIG006LW778QV30@mail-apac.sun.com>; Tue,
 21 Apr 2009 19:13:59 +0800 (SGT)
Date: Tue, 21 Apr 2009 16:39:10 +0530
From: Vivek Titarmare <Vivek.Titarmare@sun.com>
Subject: RE: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <49E66BB3.6060008@sun.com>
Sender: Vivek.Titarmare@sun.com
To: "'Margot Miller'" <Margot.Miller@sun.com>,
        "'Mark Carlson'" <markcarl@sac.sfbay.sun.com>
Cc: LSARC-ext@sun.com
Message-id: <00d101c9c271$9a854cd0$cf8fe670$%Titarmare@Sun.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: Acm+IW5FklyNHfT2S8ud6yEpMifXMgEOMFcw
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
 <49E66BB3.6060008@sun.com>
Status: RO
Content-Length: 4422

Hi Margot,

Pl. see my comments INLINE.

Let me know if you require more information on the same.

Thanks,
~Vivek R. Titarmare



-----Original Message-----
From: Margot Miller [mailto:Margot.Miller@Sun.COM] 
Sent: Thursday, April 16, 2009 4:50 AM
To: Mark Carlson
Cc: LSARC-ext@sun.com; Vivek.Titarmare@Sun.COM
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]

According to the interface table, it looks like there is one
binary- pdsh, which will be /usr/local/pdsh.

The materials directory shows man pages for the following:

   dshbak
   pdcp
   rpdcp
   pdsh

Are the three top ones also being delivered by this project?

[VIVEK] Yes, all the three are delivered by the same project.


In the pdsh man page, there are a bunch of environment variables
that should be in the i/f table:

     PDSH_RCMD_TYPE
	 
     PDSH_SSH_ARGS
	  
     PDSH_SSH_ARGS_APPEND
	  
     WCOLL
	 
     DSHPATH
	
     FANOUT
	  

[VIVEK] All the variables are used to override the standard arguments.


Also in the FOSS checklist there is the statement:

 "Since pdsh needs to run setuid root for qshell support."

Is this true?  And what is qshell?

[VIVEK] No not really. Setuid is only require for ssh which is not the
default argument. Not a compulsory command in this case.

There is mention of more environment variables listed in the
20 questions that are not in the i/f table:

  "QSHELL_REMOTE_LD_LIBRARY_PATH and QSHELL_REMOTE_LD_PREOPEN"

[VIVEK] Same is the case with all other variables (override).



Thanks
Margot



Mark Carlson wrote:
> I am sponsoring this familiarity case for Vivek Titarmare, requesting
minor binding and timing out 04/20/2009.
>
> -- mark
>
> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
> This information is Copyright 2009 Sun Microsystems
> 1. Introduction
>     1.1. Project/Component Working Name:
> 	 pdsh Ver 2.18
>     1.2. Name of Document Author/Supplier:
> 	 Author:  Vivek Titarmare
>     1.3  Date of This Document:
> 	13 April, 2009
>
> 2. Project Summary
>    2.1 Project Description
>
> 	Parallel command execution for clusters
>
> 4. Technical Description:
>
> 	Pdsh is a high-performance, parallel remote shell utility. It has
built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and can call
SSH externally (though with reduced performance). Pdsh uses a "sliding
window" parallel algorithm to conserve socket resources on the initiating
node and to allow progress to continue while timeouts occur on some
connections.
> 	
> 	Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which runs
commands on a single remote host, pdsh can run multiple remote commands in
parallel. pdsh uses a "sliding window" (or fanout) of threads to conserve
resources on the the initiating host while allowing some connections to time
out. 	
>
> 5. Interfaces 
>
> 	The binary file "pdsh" contains following interface.
>
>    Exported interface                   Classification
Interface type
>    =============================        ==============
==============
> 	pdsh-rcmd-rsh			Committed     		requires
rshd server running on remote nodes
> 	pdsh-rmcd-ssh			Committed 		requires ssh
installed, sshd on remote nodes
> 	pdsh-rcmd-mrsh			Committed 		requires
munge 
> 	pdsh-rcmd-qshell		Committed 		requires
qsnet, pdsh-qshd (qshell server)
> 	pdsh-rcmd-mqshell		Committed 		requires
qsnet, munge, pdsh-mqshd (mqshell server)
> 	pdsh-rcmd-xcpu			Committed 		requires
XCPU service mounted on /mnt/xcpu/<hostname>/xcpu
> 	pdsh-mod-genders		Uncommitted		requires
libgenders
> 	pdsh-mod-nodeattr		Uncommitted		requires
nodeattr program
> 	pdsh-mod-nodeupdown		Uncommitted		requires
libnodeupdown
> 	pdsh-mod-machines		Uncommitted		None
> 	pdsh-mod-rms			Uncommitted		requires
RMS: rmsquery, qsrmslibs
> 	pdsh-mod-slurm			Uncommitted		requires
slurm
> 	pdsh-mod-dshgroup		Uncommitted		None
> 	pdsh-mod-netgroup		Uncommitted		None	
> 	
>
>    Imported interface        Classification   Comments
>    =======================   ==============
=================================== 
> 	None
>
>    The binary file would go in "usr/local/bin"
>
>
> 6. Resources and Schedule
>     6.4. Steering Committee requested information
>    	6.4.1. Consolidation C-team Name:
> 		SFW
>     6.5. ARC review type: FastTrack
>     6.6. ARC Exposure: open
>
> _______________________________________________
> opensolaris-arc mailing list
> opensolaris-arc@opensolaris.org
>   



From margot.miller@sun.com Tue Apr 21 09:41:03 2009
Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3LGf2bq003547
	for <LSARC-ext@sac.sfbay.sun.com>; Tue, 21 Apr 2009 09:41:03 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n3LGeu7U024531;
	Wed, 22 Apr 2009 00:40:59 +0800 (SGT)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KIG00I0FMC7TI00@nwk-avmta-2.sfbay.sun.com>; Tue,
 21 Apr 2009 09:40:55 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KIG00I0GMC7TA00@nwk-avmta-2.sfbay.sun.com>; Tue,
 21 Apr 2009 09:40:55 -0700 (PDT)
Received: from [10.7.250.251]
 (punchin-client-10-7-250-251.SFBay.Sun.COM [10.7.250.251])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n3LGesV1172778; Tue, 21 Apr 2009 09:40:54 -0700 (PDT)
Date: Tue, 21 Apr 2009 09:35:56 -0700
From: Margot Miller <margot.miller@sun.com>
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <00d101c9c271$9a854cd0$cf8fe670$%Titarmare@Sun.com>
To: Vivek Titarmare <Vivek.Titarmare@sun.com>
Cc: "'Mark Carlson'" <markcarl@sac.sfbay.sun.com>, LSARC-ext@sun.com
Message-id: <49EDF5EC.9010509@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
 <49E66BB3.6060008@sun.com> <00d101c9c271$9a854cd0$cf8fe670$%Titarmare@Sun.com>
User-Agent: Thunderbird 2.0b1 (X11/20070115)
Status: RO
Content-Length: 5620

Hey Vivek,

For the below:

  Is this true?  And what is qshell?

  [VIVEK] No not really. Setuid is only require for ssh which is not the
  default argument. Not a compulsory command in this case.

Is qshell being delivered as part of this case.  If not, then there is no
setuid issue?

Please update the interface table in the materials directory with all
the below info (add environment variables, etc. to i/f table) and in
previous emails (ex. the binary is going
into /usr/bin, not /usr/local/bin).   After updating the i/f table,
please resend it out again to this alias.

Also, looking at the email log, I don't think all the issues were
addressed (please check Danek's email).

Thanks
Margot



Vivek Titarmare wrote:
> Hi Margot,
>
> Pl. see my comments INLINE.
>
> Let me know if you require more information on the same.
>
> Thanks,
> ~Vivek R. Titarmare
>
>
>
> -----Original Message-----
> From: Margot Miller [mailto:Margot.Miller@Sun.COM] 
> Sent: Thursday, April 16, 2009 4:50 AM
> To: Mark Carlson
> Cc: LSARC-ext@sun.com; Vivek.Titarmare@Sun.COM
> Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
>
> According to the interface table, it looks like there is one
> binary- pdsh, which will be /usr/local/pdsh.
>
> The materials directory shows man pages for the following:
>
>    dshbak
>    pdcp
>    rpdcp
>    pdsh
>
> Are the three top ones also being delivered by this project?
>
> [VIVEK] Yes, all the three are delivered by the same project.
>
>
> In the pdsh man page, there are a bunch of environment variables
> that should be in the i/f table:
>
>      PDSH_RCMD_TYPE
> 	 
>      PDSH_SSH_ARGS
> 	  
>      PDSH_SSH_ARGS_APPEND
> 	  
>      WCOLL
> 	 
>      DSHPATH
> 	
>      FANOUT
> 	  
>
> [VIVEK] All the variables are used to override the standard arguments.
>
>
> Also in the FOSS checklist there is the statement:
>
>  "Since pdsh needs to run setuid root for qshell support."
>
> Is this true?  And what is qshell?
>
> [VIVEK] No not really. Setuid is only require for ssh which is not the
> default argument. Not a compulsory command in this case.
>
> There is mention of more environment variables listed in the
> 20 questions that are not in the i/f table:
>
>   "QSHELL_REMOTE_LD_LIBRARY_PATH and QSHELL_REMOTE_LD_PREOPEN"
>
> [VIVEK] Same is the case with all other variables (override).
>
>
>
> Thanks
> Margot
>
>
>
> Mark Carlson wrote:
>   
>> I am sponsoring this familiarity case for Vivek Titarmare, requesting
>>     
> minor binding and timing out 04/20/2009.
>   
>> -- mark
>>
>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
>> This information is Copyright 2009 Sun Microsystems
>> 1. Introduction
>>     1.1. Project/Component Working Name:
>> 	 pdsh Ver 2.18
>>     1.2. Name of Document Author/Supplier:
>> 	 Author:  Vivek Titarmare
>>     1.3  Date of This Document:
>> 	13 April, 2009
>>
>> 2. Project Summary
>>    2.1 Project Description
>>
>> 	Parallel command execution for clusters
>>
>> 4. Technical Description:
>>
>> 	Pdsh is a high-performance, parallel remote shell utility. It has
>>     
> built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and can call
> SSH externally (though with reduced performance). Pdsh uses a "sliding
> window" parallel algorithm to conserve socket resources on the initiating
> node and to allow progress to continue while timeouts occur on some
> connections.
>   
>> 	
>> 	Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which runs
>>     
> commands on a single remote host, pdsh can run multiple remote commands in
> parallel. pdsh uses a "sliding window" (or fanout) of threads to conserve
> resources on the the initiating host while allowing some connections to time
> out. 	
>   
>> 5. Interfaces 
>>
>> 	The binary file "pdsh" contains following interface.
>>
>>    Exported interface                   Classification
>>     
> Interface type
>   
>>    =============================        ==============
>>     
> ==============
>   
>> 	pdsh-rcmd-rsh			Committed     		requires
>>     
> rshd server running on remote nodes
>   
>> 	pdsh-rmcd-ssh			Committed 		requires ssh
>>     
> installed, sshd on remote nodes
>   
>> 	pdsh-rcmd-mrsh			Committed 		requires
>>     
> munge 
>   
>> 	pdsh-rcmd-qshell		Committed 		requires
>>     
> qsnet, pdsh-qshd (qshell server)
>   
>> 	pdsh-rcmd-mqshell		Committed 		requires
>>     
> qsnet, munge, pdsh-mqshd (mqshell server)
>   
>> 	pdsh-rcmd-xcpu			Committed 		requires
>>     
> XCPU service mounted on /mnt/xcpu/<hostname>/xcpu
>   
>> 	pdsh-mod-genders		Uncommitted		requires
>>     
> libgenders
>   
>> 	pdsh-mod-nodeattr		Uncommitted		requires
>>     
> nodeattr program
>   
>> 	pdsh-mod-nodeupdown		Uncommitted		requires
>>     
> libnodeupdown
>   
>> 	pdsh-mod-machines		Uncommitted		None
>> 	pdsh-mod-rms			Uncommitted		requires
>>     
> RMS: rmsquery, qsrmslibs
>   
>> 	pdsh-mod-slurm			Uncommitted		requires
>>     
> slurm
>   
>> 	pdsh-mod-dshgroup		Uncommitted		None
>> 	pdsh-mod-netgroup		Uncommitted		None	
>> 	
>>
>>    Imported interface        Classification   Comments
>>    =======================   ==============
>>     
> =================================== 
>   
>> 	None
>>
>>    The binary file would go in "usr/local/bin"
>>
>>
>> 6. Resources and Schedule
>>     6.4. Steering Committee requested information
>>    	6.4.1. Consolidation C-team Name:
>> 		SFW
>>     6.5. ARC review type: FastTrack
>>     6.6. ARC Exposure: open
>>
>> _______________________________________________
>> opensolaris-arc mailing list
>> opensolaris-arc@opensolaris.org
>>   
>>     
>
>
>   


From Vivek.Titarmare@sun.com Tue Apr 21 10:17:37 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3LHHb9n006335
	for <LSARC-ext@sac.sfbay.sun.com>; Tue, 21 Apr 2009 10:17:37 -0700 (PDT)
Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3LHHXJ3005467
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 21 Apr 2009 18:17:36 +0100 (BST)
Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by
 brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KIG0070LO1ABD00@brm-avmta-1.central.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 21 Apr 2009 11:17:34 -0600 (MDT)
Received: from sineb-mail-1.sun.com ([192.18.19.6])
 by brm-avmta-1.central.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KIG0000SO19NQ60@brm-avmta-1.central.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue,
 21 Apr 2009 11:17:34 -0600 (MDT)
Received: from fe-apac-05.sun.com
 (fe-apac-05.sun.com [192.18.19.176] (may be forged))
	by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3LHHWkd009536	for
 <LSARC-ext@sun.com>; Tue, 21 Apr 2009 17:17:32 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KIG00600NQ5NS00@mail-apac.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Wed, 22 Apr 2009 01:17:32 +0800 (SGT)
Received: from VivekTPC ([unknown] [121.246.32.150])
 by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit
 (built Feb 19 2009)) with ESMTPSA id <0KIG00608O14QVB0@mail-apac.sun.com>; Wed,
 22 Apr 2009 01:17:32 +0800 (SGT)
Date: Tue, 21 Apr 2009 22:47:27 +0530
From: Vivek Titarmare <Vivek.Titarmare@sun.com>
Subject: RE: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <49EDF5EC.9010509@sun.com>
Sender: Vivek.Titarmare@sun.com
To: "'Margot Miller'" <Margot.Miller@sun.com>
Cc: "'Mark Carlson'" <markcarl@sac.sfbay.sun.com>, LSARC-ext@sun.com
Message-id: <013901c9c2a5$0dc5d0b0$29517210$%Titarmare@Sun.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/mixed; boundary="Boundary_(ID_UxYOWro2oxKkAI2KEz5jgQ)"
Content-language: en-us
Thread-index: AcnCn/VuZOoYaNF4SNKFLx7I8QQhbgAAhFMA
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
 <49E66BB3.6060008@sun.com> <00d101c9c271$9a854cd0$cf8fe670$%Titarmare@Sun.com>
 <49EDF5EC.9010509@sun.com>
Status: RO
Content-Length: 9525

This is a multipart message in MIME format.

--Boundary_(ID_UxYOWro2oxKkAI2KEz5jgQ)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi Margot,

-- cut --
Is qshell being delivered as part of this case.  If not, then there is no
setuid issue?

[VIVEK] No it is not the part of this delivery.

Pl. find attached updated Fasttrack for pdsh.

Let me know if I am missing any point in the same.

Thanks,
~Vivek R. Titarmare


-----Original Message-----
From: Margot Miller [mailto:Margot.Miller@Sun.COM] 
Sent: Tuesday, April 21, 2009 10:06 PM
To: Vivek Titarmare
Cc: 'Mark Carlson'; LSARC-ext@sun.com
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]

Hey Vivek,

For the below:

  Is this true?  And what is qshell?

  [VIVEK] No not really. Setuid is only require for ssh which is not the
  default argument. Not a compulsory command in this case.

Is qshell being delivered as part of this case.  If not, then there is no
setuid issue?

Please update the interface table in the materials directory with all
the below info (add environment variables, etc. to i/f table) and in
previous emails (ex. the binary is going
into /usr/bin, not /usr/local/bin).   After updating the i/f table,
please resend it out again to this alias.

Also, looking at the email log, I don't think all the issues were
addressed (please check Danek's email).

Thanks
Margot



Vivek Titarmare wrote:
> Hi Margot,
>
> Pl. see my comments INLINE.
>
> Let me know if you require more information on the same.
>
> Thanks,
> ~Vivek R. Titarmare
>
>
>
> -----Original Message-----
> From: Margot Miller [mailto:Margot.Miller@Sun.COM] 
> Sent: Thursday, April 16, 2009 4:50 AM
> To: Mark Carlson
> Cc: LSARC-ext@sun.com; Vivek.Titarmare@Sun.COM
> Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
>
> According to the interface table, it looks like there is one
> binary- pdsh, which will be /usr/local/pdsh.
>
> The materials directory shows man pages for the following:
>
>    dshbak
>    pdcp
>    rpdcp
>    pdsh
>
> Are the three top ones also being delivered by this project?
>
> [VIVEK] Yes, all the three are delivered by the same project.
>
>
> In the pdsh man page, there are a bunch of environment variables
> that should be in the i/f table:
>
>      PDSH_RCMD_TYPE
> 	 
>      PDSH_SSH_ARGS
> 	  
>      PDSH_SSH_ARGS_APPEND
> 	  
>      WCOLL
> 	 
>      DSHPATH
> 	
>      FANOUT
> 	  
>
> [VIVEK] All the variables are used to override the standard arguments.
>
>
> Also in the FOSS checklist there is the statement:
>
>  "Since pdsh needs to run setuid root for qshell support."
>
> Is this true?  And what is qshell?
>
> [VIVEK] No not really. Setuid is only require for ssh which is not the
> default argument. Not a compulsory command in this case.
>
> There is mention of more environment variables listed in the
> 20 questions that are not in the i/f table:
>
>   "QSHELL_REMOTE_LD_LIBRARY_PATH and QSHELL_REMOTE_LD_PREOPEN"
>
> [VIVEK] Same is the case with all other variables (override).
>
>
>
> Thanks
> Margot
>
>
>
> Mark Carlson wrote:
>   
>> I am sponsoring this familiarity case for Vivek Titarmare, requesting
>>     
> minor binding and timing out 04/20/2009.
>   
>> -- mark
>>
>> Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI
>> This information is Copyright 2009 Sun Microsystems
>> 1. Introduction
>>     1.1. Project/Component Working Name:
>> 	 pdsh Ver 2.18
>>     1.2. Name of Document Author/Supplier:
>> 	 Author:  Vivek Titarmare
>>     1.3  Date of This Document:
>> 	13 April, 2009
>>
>> 2. Project Summary
>>    2.1 Project Description
>>
>> 	Parallel command execution for clusters
>>
>> 4. Technical Description:
>>
>> 	Pdsh is a high-performance, parallel remote shell utility. It has
>>     
> built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and can
call
> SSH externally (though with reduced performance). Pdsh uses a "sliding
> window" parallel algorithm to conserve socket resources on the initiating
> node and to allow progress to continue while timeouts occur on some
> connections.
>   
>> 	
>> 	Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which runs
>>     
> commands on a single remote host, pdsh can run multiple remote commands in
> parallel. pdsh uses a "sliding window" (or fanout) of threads to conserve
> resources on the the initiating host while allowing some connections to
time
> out. 	
>   
>> 5. Interfaces 
>>
>> 	The binary file "pdsh" contains following interface.
>>
>>    Exported interface                   Classification
>>     
> Interface type
>   
>>    =============================        ==============
>>     
> ==============
>   
>> 	pdsh-rcmd-rsh			Committed     		requires
>>     
> rshd server running on remote nodes
>   
>> 	pdsh-rmcd-ssh			Committed 		requires ssh
>>     
> installed, sshd on remote nodes
>   
>> 	pdsh-rcmd-mrsh			Committed 		requires
>>     
> munge 
>   
>> 	pdsh-rcmd-qshell		Committed 		requires
>>     
> qsnet, pdsh-qshd (qshell server)
>   
>> 	pdsh-rcmd-mqshell		Committed 		requires
>>     
> qsnet, munge, pdsh-mqshd (mqshell server)
>   
>> 	pdsh-rcmd-xcpu			Committed 		requires
>>     
> XCPU service mounted on /mnt/xcpu/<hostname>/xcpu
>   
>> 	pdsh-mod-genders		Uncommitted		requires
>>     
> libgenders
>   
>> 	pdsh-mod-nodeattr		Uncommitted		requires
>>     
> nodeattr program
>   
>> 	pdsh-mod-nodeupdown		Uncommitted		requires
>>     
> libnodeupdown
>   
>> 	pdsh-mod-machines		Uncommitted		None
>> 	pdsh-mod-rms			Uncommitted		requires
>>     
> RMS: rmsquery, qsrmslibs
>   
>> 	pdsh-mod-slurm			Uncommitted		requires
>>     
> slurm
>   
>> 	pdsh-mod-dshgroup		Uncommitted		None
>> 	pdsh-mod-netgroup		Uncommitted		None	
>> 	
>>
>>    Imported interface        Classification   Comments
>>    =======================   ==============
>>     
> =================================== 
>   
>> 	None
>>
>>    The binary file would go in "usr/local/bin"
>>
>>
>> 6. Resources and Schedule
>>     6.4. Steering Committee requested information
>>    	6.4.1. Consolidation C-team Name:
>> 		SFW
>>     6.5. ARC review type: FastTrack
>>     6.6. ARC Exposure: open
>>
>> _______________________________________________
>> opensolaris-arc mailing list
>> opensolaris-arc@opensolaris.org
>>   
>>     
>
>
>   


--Boundary_(ID_UxYOWro2oxKkAI2KEz5jgQ)
Content-type: text/plain; name=FastTrack_pdsh.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=FastTrack_pdsh.txt

Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction
    1.1. Project/Component Working Name:
	 pdsh Ver 2.18
    1.2. Name of Document Author/Supplier:
	 Author:  Vivek R. Titarmare
    1.3  Date of This Document:
	 3rd April, 2009

2. Project Summary
   2.1 Project Description

	Parallel command execution for clusters

4. Technical Description:

	Pdsh is a high-performance, parallel remote shell utility. It has built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and can call SSH externally (though with reduced performance). Pdsh uses a "sliding window" parallel algorithm to conserve socket resources on the initiating node and to allow progress to continue while timeouts occur on some connections.
	
	Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which runs commands on a single remote host, pdsh can run multiple remote commands in parallel. pdsh uses a "sliding window" (or fanout) of threads to conserve resources on the the initiating host while allowing some connections to time out. 	

5. Interfaces 

	The binary file "pdsh" contains following interface.

   Exported interface                   Classification 		Interface type
   =============================        ============== 		==============
	pdsh-rcmd-rsh			Committed     		requires rshd server running on remote nodes
	pdsh-rmcd-ssh			Committed 		requires ssh installed, sshd on remote nodes
	pdsh-rcmd-mrsh			Committed 		requires munge 
	pdsh-rcmd-qshell		Committed 		requires qsnet, pdsh-qshd (qshell server)
	pdsh-rcmd-mqshell		Committed 		requires qsnet, munge, pdsh-mqshd (mqshell server)
	pdsh-rcmd-xcpu			Committed 		requires XCPU service mounted on /mnt/xcpu/<hostname>/xcpu
	pdsh-mod-genders		Uncommitted		requires libgenders
	pdsh-mod-nodeattr		Uncommitted		requires nodeattr program
	pdsh-mod-nodeupdown		Uncommitted		requires libnodeupdown
	pdsh-mod-machines		Uncommitted		None
	pdsh-mod-rms			Uncommitted		requires RMS: rmsquery, qsrmslibs
	pdsh-mod-slurm			Uncommitted		requires slurm
	pdsh-mod-dshgroup		Uncommitted		None
	pdsh-mod-netgroup		Uncommitted		None	
	PDSH_RCMD_TYPE			Uncommitted		override standard argument
	PDSH_SSH_ARGS			Uncommitted		override standard argument
	PDSH_SSH_ARGS_APPEND		Uncommitted		override standard argument
	WCOLL				Uncommitted		override standard argument
	DSHPATH				Uncommitted		override standard argument
	FANOUT				Uncommitted		override standard argument
	QSHELL_REMOTE_LD_LIBRARY_PATH	Uncommitted		override standard argument
	QSHELL_REMOTE_LD_PREOPEN	Uncommitted		override standard argument

	

   Imported interface        Classification   Comments
   =======================   ==============   =================================== 
	None

   The binary file would go in "usr/bin"


6. Resources and Schedule
    6.4. Steering Committee requested information
   	6.4.1. Consolidation C-team Name:
		SFW
    6.5. ARC review type: FastTrack
    6.6. ARC Exposure: open

--Boundary_(ID_UxYOWro2oxKkAI2KEz5jgQ)--

From Mark.Carlson@sun.com Tue Apr 21 10:47:22 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3LHlLfH007365
	for <LSARC-ext@sac.sfbay.sun.com>; Tue, 21 Apr 2009 10:47:21 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3LHku9V026282
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 21 Apr 2009 18:47:20 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KIG00M0HPES7700@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@Sun.COM); Tue, 21 Apr 2009 10:47:16 -0700 (PDT)
Received: from brmea-mail-4.sun.com ([192.18.98.36])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KIG00I4FPERTC60@nwk-avmta-2.sfbay.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Tue,
 21 Apr 2009 10:47:16 -0700 (PDT)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3LHlFuE027625	for
 <LSARC-ext@Sun.COM>; Tue, 21 Apr 2009 17:47:15 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KIG00M00OMEFM00@mail-amer.sun.com> for LSARC-ext@Sun.COM
 (ORCPT LSARC-ext@Sun.COM); Tue, 21 Apr 2009 11:47:15 -0600 (MDT)
Received: from Macintosh-335.local ([unknown] [129.150.35.120])
 by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 with ESMTPSA id <0KIG005C6PER5K40@mail-amer.sun.com> for LSARC-ext@Sun.COM
 (ORCPT LSARC-ext@Sun.COM); Tue, 21 Apr 2009 11:47:15 -0600 (MDT)
Date: Tue, 21 Apr 2009 11:47:15 -0600
From: "Mark A. Carlson" <Mark.Carlson@sun.com>
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/23/2009]
In-reply-to: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
Sender: Mark.Carlson@sun.com
To: LSARC-ext@sun.com
Cc: Vivek.Titarmare@sun.com
Message-id: <49EE06A3.3030505@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
Status: RO
Content-Length: 111

I have extended the timer on this case until Thursday 4/23/2009 to further
resolve in-process issues.

-- mark

From Vivek.Titarmare@sun.com Wed Apr 22 06:09:05 2009
Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3MD94il015417
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 22 Apr 2009 06:09:04 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n3MD94Fc021324
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Wed, 22 Apr 2009 06:09:04 -0700 (PDT)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KII0001H774VQ00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@Sun.COM); Wed, 22 Apr 2009 06:09:04 -0700 (PDT)
Received: from sineb-mail-1.sun.com ([192.18.19.6])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KII00JHT76Z6Y70@nwk-avmta-2.sfbay.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Wed,
 22 Apr 2009 06:09:01 -0700 (PDT)
Received: from fe-apac-06.sun.com
 (fe-apac-06.sun.com [192.18.19.177] (may be forged))
	by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3MD8xmk005215	for
 <LSARC-ext@Sun.COM>; Wed, 22 Apr 2009 13:08:59 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KII0030072DWT00@mail-apac.sun.com> for LSARC-ext@Sun.COM
 (ORCPT LSARC-ext@Sun.COM); Wed, 22 Apr 2009 21:08:59 +0800 (SGT)
Received: from VivekTPC ([unknown] [129.150.146.93])
 by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit
 (built Feb 19 2009)) with ESMTPSA id <0KII00G3076Q29M0@mail-apac.sun.com>; Wed,
 22 Apr 2009 21:08:57 +0800 (SGT)
Date: Wed, 22 Apr 2009 18:38:47 +0530
From: Vivek Titarmare <Vivek.Titarmare@sun.com>
Subject: RE: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <20090421180905.GF4425@mumak.SFBay.Sun.COM>
Sender: Vivek.Titarmare@sun.com
To: "'Danek Duvall'" <Danek.Duvall@sun.com>
Cc: "'Mark Carlson'" <markcarl@sac.sfbay.sun.com>, James.D.Carlson@sun.com,
        Nicolas.Williams@sun.com, LSARC-ext@sun.com
Message-id: <024601c9c34b$7b459110$71d0b330$%Titarmare@Sun.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/mixed; boundary="Boundary_(ID_b1FlBRXwNB6pB84SpHAFHw)"
Content-language: en-us
Thread-index: AcnCq+tSROcC6BJGR7uDtWYtXE78wwAnuYSg
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
 <20090413205436.GX7978@mumak.SFBay.Sun.COM>
 <003001c9bd02$8997a1d0$9cc6e570$%Titarmare@Sun.com>
 <20090414150713.GA7978@mumak.SFBay.Sun.COM>
 <013801c9c2a4$e270fb10$a752f130$%Titarmare@Sun.com>
 <20090421180905.GF4425@mumak.SFBay.Sun.COM>
Status: RO
Content-Length: 86483

This is a multipart message in MIME format.

--Boundary_(ID_b1FlBRXwNB6pB84SpHAFHw)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT

Hi Danek and the team,

I have updated the Fasttrack and FOSS check list for pdsh. Major changes in
the interface tables would be seen. Actually a rework was done on this
package and found that the interface table needed a change. 

Pl. ignore the previous Interface related conflicts.

Let me know if this looks good to go.

Pl. find attached all the files required for this ARC review.

Thanks,
~Vivek R. Titarmare



-----Original Message-----
From: Danek Duvall [mailto:Danek.Duvall@Sun.COM] 
Sent: Tuesday, April 21, 2009 11:39 PM
To: Vivek Titarmare
Cc: 'Mark Carlson'; James.D.Carlson@Sun.COM; Nicolas.Williams@Sun.COM;
Manisha.Jha@Sun.COM
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]

[ Please use standard email quoting techniques -- a "> " prefix to every
line that you're responding to, and not to your own; what you're doing
makes your email responses incredibly difficult to read.  Perhaps not using
Outlook would help.  This is Sun, after all; you should be running Solaris.
]

On Tue, Apr 21, 2009 at 10:46:14PM +0530, Vivek Titarmare wrote:

> > No, I want you to not deliver those interfaces.  You can't ship
components
> > that don't work.  This is a commercial OS, not a grad student project,
and
> > it costs Sun tons of money to field calls from customers complaining
about
> > things that don't work.  It's best not to ship them at all if we know
> > they're busted.  Given how much of the man page is filled with text
> > describing options and arguments that won't be useful on Solaris, you'll
> > need to remove this extraneous documentation before delivery, too.
>
> [VIVEK] I am sorry, I think I confused you. All the components work, for
> those components to work we need to override the environment variables
which
> I am adding those in the Interface table. I this case, do we still need to
> remove the contents from the man pages. Pl. let me know.

The components that are unavailable (libgenders, nodeattr, etc) will cause
portions of pdsh (pdsh-mod-genders, pdsh-mod-nodeattr, etc) not to work,
environment variables or not.  There is no way that "pdsh-mod-slurm" is
going to work unless slurm is installed, and since there is no slurm
available for Solaris, then "pdsh-mod-slurm" is not going to work on
Solaris.  So don't ship it, and don't document it.

Danek

--Boundary_(ID_b1FlBRXwNB6pB84SpHAFHw)
Content-type: text/plain; name=dshbak.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=dshbak.txt




DSHBAK							DSHBAK(1)



NAME
     dshbak - format output from pdsh command

SYNOPSIS
     dshbak [-c]

DESCRIPTION
     dshbak formats pdsh output	for  humans.   Output  from  each
     node  is consolidated, the	leading	node: prefix is	stripped,
     and a header block	with the node name is added.  If  the  -c
     option  is	 specified,  nodes  with identical output are not
     displayed twice; instead, the header will contain a list  of
     nodes.   The  list	 of nodes is further compressed	into node
     ranges if the node	names have a numeric suffix.


ORIGIN
     A rewrite of IBM dshbak(1)	by Jim Garlick
     <garlick@llnl.gov>	on LLNL's ASCI Blue-Pacific IBM	 SP  sys-
     tem.


ATTRIBUTES
     See attributes(5) for descriptions	of the	following  attri-
     butes:



     ____________________________________________________________
    |	    ATTRIBUTE TYPE	  |	  ATTRIBUTE VALUE	|
    |_____________________________|_____________________________|
    | Availability		  | SUNWpdsh			|
    |_____________________________|_____________________________|
    | Interface	Stability	  | uncommitted			|
    |_____________________________|_____________________________|


SEE ALSO
     pdsh(1)
















LLNL		    Last change: Release 1.3			1




--Boundary_(ID_b1FlBRXwNB6pB84SpHAFHw)
Content-type: application/octet-stream; name=pdcp.1
Content-transfer-encoding: QUOTED-PRINTABLE
Content-disposition: attachment; filename=pdcp.1

'\" te=0A.\"^M=0A.\" CDDL HEADER START^M=0A.\"^M=0A.\" The contents o=
f this file are subject to the terms of the^M=0A.\" Common Developmen=
t and Distribution License (the "License").^M=0A.\" You may not use t=
his file except in compliance with the License.^M=0A.\"^M=0A.\" You c=
an obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE^M=0A.\=
" or http://www.opensolaris.org/os/licensing.^M=0A.\" See the License=
 for the specific language governing permissions^M=0A.\" and limitati=
ons under the License.^M=0A.\"^M=0A.\" When distributing Covered Code=
, include this CDDL HEADER in each^M=0A.\" file and include the Licen=
se file at usr/src/OPENSOLARIS.LICENSE.^M=0A.\" If applicable, add th=
e following below this CDDL HEADER, with the^M=0A.\" fields enclosed =
by brackets "[]" replaced with your own identifying^M=0A.\" informati=
on: Portions Copyright [yyyy] [name of copyright owner]^M=0A.\"^M=
=0A.\" CDDL HEADER END^M=0A.\"^M=0A.\" Copyright 2009 Sun Microsystem=
s, Inc. All rights reserved.^M=0A.\" Use is subject to license terms.=
^M=0A.\"^M=0A\." $Id: pdcp.1.in 1174 2008-11-25 21:17:05Z grondo $=
=0A.TH "pdsh" "1" "solaris2.11" "pdsh-2.18"=0A=0A.SH NAME=0Apdcp \- c=
opy files to groups of hosts in parallel=0A.br=0Arpdcp \- (reverse pd=
cp) copy files from a group of hosts in parallel=0A=0A.SH SYNOPSIS=
=0A\fBpdcp\fR [\fIoptions\fR]... src [src2...] dest=0A.br=0A\fBrpdcp\=
fR [\fIoptions\fR]... src [src2...] dir=0A=0A.SH DESCRIPTION=0A\fBpdc=
p\fR is a variant of the rcp(1) command.  Unlike rcp(1), which=0Acopi=
es files to a single remote host, \fBpdcp\fR can copy files to=0Amult=
iple remote hosts in parallel.  However, \fBpdcp\fR does=0Anot recogn=
ize files in the format ``rname@rhost:path,'' therefore all=0Asource =
files must be on the local host machine.  Destination nodes must=0Abe=
 listed on the \fBpdcp\fR command line using a suitable target=0Anode=
list option (See the \fIOPTIONS\fR section below).  Each destination=
=0Anode listed must have \fBpdcp\fR installed for the copy to succeed=
.=0A.LP=0AWhen \fBpdcp\fR receives SIGINT (ctrl-C), it lists the stat=
us of current=0Athreads.  A second SIGINT within one second terminate=
s the program. Pending=0Athreads may be canceled by issuing ctrl-Z wi=
thin one second of ctrl-C.=0APending threads are those that have not =
yet been initiated, or are still=0Ain the process of connecting to th=
e remote host.=0A.LP=0ALike pdsh(1), the functionality of \fBpdcp\fR =
may be supplemented by=0Adynamically loadable modules. In \fBpdcp\fR,=
 the modules may provide=0Aa new connect protocol (replacing the stan=
dard rsh(1) protocol), filtering=0Aoptions (e.g. excluding hosts that=
 are down), and/or host selection=0Aoptions (e.g. \fI-a\fR selects al=
l nodes from a local config file).=0ABy default, \fBpdcp\fR requires =
at least one "rcmd" module to be=0Aloaded (to provide the channel for=
 remote copy).=0A=0A.SH "REVERSE PDCP"=0A\fBrpdcp\fR performs a rever=
se parallel copy.  Rather than copying files=0Ato remote hosts, files=
 are retrieved from remote hosts and stored locally.=0AAll directorie=
s or files retrieved will be stored with their remote=0Ahostname appe=
nded to the filename.  The destination file must be a=0Adirectory whe=
n this option is used.=0A.LP=0AIn other respects, \fBrpdcp\fR is exac=
tly like \fBpdcp\fR, and further=0Astatements regarding \fBpdcp\fR in=
 this manual also apply to \fBrpdcp\fR.=0A=0A.SH "RCMD MODULES"=0AThe=
 method by which \fBpdcp\fR connects to remote hosts may be=0Aselecte=
d at runtime using the \fI-R\fR option (See \fIOPTIONS\fR below).=
=0AThis functionality is ultimately implemented via dynamically loada=
ble=0Amodules, and so the list of available options may be different=
=0Afrom installation to installation. A list of currently available r=
cmd=0Amodules is printed when using any of the \fI-h\fR, \fI-V\fR, or=
 \fI-L\fR=0Aoptions. The default rcmd module will also be displayed w=
ith the=0A\fI-h\fR and \fI-V\fR options.=0A.LP=0AA list of \fIrcmd\fR=
 modules currently distributed with \fBpdcp\fR=0Afollows.=0A.TP 8=
=0Arsh=0AUses an internal, thread-safe implementation of BSD rcmd(3)=
=0Ato run commands using the standard rsh(1) protocol.=0A.TP=0Assh=
=0AUses a variant of popen(3) to run multiple copies of the ssh(1)=
=0Acommand.=0A.TP=0Amrsh=0AThis module uses the mrsh(1) protocol to e=
xecute jobs on remote hosts.=0AThe mrsh protocol uses a credential ba=
sed authentication, forgoing=0Athe need to allocate reserved ports. I=
n other aspects, it acts just=0Alike rsh.=0A.TP=0Akrb4=0AThe krb4 mod=
ule allows users to execute remote commands after=0Aauthenticating wi=
th kerberos. Of course, the remote rshd daemons=0Amust be kerberized.=
=0A.TP=0Axcpu=0AThe xcpu module uses the xcpu service to execute remo=
te commands.=0A=0A.SH OPTIONS=0AThe list of available \fBpdcp\fR opti=
ons is determined at runtime=0Aby supplementing the list of standard =
\fBpdcp\fR options with=0Aany options provided by loaded \fIrcmd\fR a=
nd \fImisc\fR modules.=0AIn some cases, options provided by modules m=
ay conflict with=0Aeach other. In these cases, the modules are incomp=
atible and=0Athe first module loaded wins.=0A=0A.SH "Standard target =
nodelist options"=0A.TP=0A.I "-w host,host,..."=0ATarget the specifie=
d list of hosts. Do not use with any other=0Anode selection options (=
e.g. \fI\-a\fR, \fI\-g\fR if they are=0Aavailable). No spaces are all=
owed in the comma-separated list.=0AA list consisting of a single `-'=
 character causes the target=0Ahosts to be read from stdin, one per l=
ine. The host list may=0Acontain hostlist expressions of the form ``h=
ost[1-5,7]''. For=0Amore information about the hostlist format, see t=
he=0A\fBHOSTLIST EXPRESSIONS\fR section below.=0A.TP=0A.I "-x host,ho=
st,..."=0AExclude the specified hosts. May be specified in conjunctio=
n with=0Aother target node list options such as \fI\-a\fR and \fI\-g\=
fR (when=0Aavailable). Hostlists may also be specified to the \fI\-x\=
fR option=0A(see \fBHOSTLIST EXPRESSIONS\fI secion below).=0A=0A.SH "=
Standard pdcp options"=0A.TP=0A.I "-h"=0AOutput usage menu and quit. =
A list of available rcmd modules=0Awill be printed at the end of the =
usage message.=0A.TP=0A.I "-q"=0AList option values and the target no=
delist and exit without action.=0A.TP=0A.I "-b"=0ADisable ctrl-C stat=
us feature so that a single ctrl-C kills parallel=0Acopy. (Batch Mode=
)=0A.TP=0A.I "-r"=0ACopy directories recursively.=0A.TP=0A.I "-p"=
=0APreserve modification time and modes.=0A.TP=0A.I "-e PATH"=0AExpli=
citly specify path to remote \fBpdcp\fR binary=0Ainstead of using the=
 locally executed path.=0A.TP=0A.I "-l user"=0AThis option may be use=
d to copy files as another user, subject to=0Aauthorization. For BSD =
rcmd, this means the invoking user and system must=0Abe listed in the=
 user\'s .rhosts file (even for root).=0A.TP=0A.I "-t seconds"=0ASet =
the connect timeout. Default is 10 seconds.=0A.TP=0A.I "-f number"=
=0ASet the maximum number of simultaneous remote copies to \fInumber\=
fR.=0AThe default is 32.=0A.TP=0A.I "-R name"=0ASet rcmd module to \f=
Iname\fR. This option may also be set via the=0APDSH_RCMD_TYPE enviro=
nment variable. A list of available rcmd=0Amodules may be obtained vi=
a either the \fI-h\fR or \fI-L\fR options.=0A.TP=0A.I "-R name"=0ASet=
 rcmd module to \fIname\fR. This option may also be set via the=0APDS=
H_RCMD_TYPE environment variable. A list of available rcmd=0Amodules =
may be obtained via either the \fI-h\fR or \fI-L\fR options.=0A.TP=
=0A.I "-L"=0AList info on all loaded \fBpdcp\fR modules and quit.=
=0A.TP=0A.I "-d"=0AInclude more complete thread status when SIGINT is=
 received, and display=0Aconnect and command time statistics on stder=
r when done.=0A.TP=0A.I "-V"=0AOutput \fBpdcp\fR version information,=
 along with list of currently=0Aloaded modules, and exit.=0A=0A=0A.SH=
 "HOSTLIST EXPRESSIONS"=0AAs noted in sections above,=0A.B pdcp=0Aacc=
epts ranges of hostnames in=0Athe general form: prefix[n-m,l-k,...], =
where n < m and l < k, etc.,=0Aas an alternative to explicit lists of=
 hosts.  This form should not=0Abe confused with regular expression c=
haracter classes (also denoted=0Aby ``[]''). For example, foo[19] doe=
s not represent foo1 or foo9, but=0Arather represents a degenerate ra=
nge: foo19.=0A=0AThis range syntax is meant=0Aonly as a convenience o=
n clusters with a prefixNN naming convention and=0Aspecification of r=
anges should not be considered necessary -- the list=0Afoo1,foo9 coul=
d be specified as such, or by the range foo[1,9].=0A=0ASome examples =
of range usage follow:=0A=0A.nf=0A=0ACopy /etc/hosts to foo01,foo02,.=
..,foo05=0A    pdcp -w foo[01-05] /etc/hosts /etc=0A=0ACopy /etc/host=
s to foo7,foo9,foo10=0A    pdcp -w foo[7,9-10] /etc/hosts /etc=0A=
=0ACopy /etc/hosts to foo0,foo4,foo5=0A pdcp -w foo[0-5] -x foo[1-3] =
/etc/hosts /etc=0A=0A.fi=0A=0AAs a reminder to the reader, some shell=
s will interpret brackets ('['=0Aand ']') for pattern matching.  Depe=
nding on your shell, it may be=0Anecessary to enclose ranged lists wi=
thin quotes.  For example, in=0Atcsh, the first example above should =
be executed as:=0A=0A    pdcp -w "foo[01-05]" /etc/hosts /etc=0A=0A.S=
H "ORIGIN"=0APdsh/pdcp was originally a rewrite of IBM dsh(1) by Jim =
Garlick=0A<garlick@llnl.gov> on LLNL's ASCI Blue-Pacific IBM SP syste=
m.=0AIt is now also used on Linux clusters at LLNL.=0A=0A.SH "LIMITAT=
IONS"=0AWhen using=0A.B ssh=0Afor remote execution, stderr of ssh to =
be folded in with that of the=0Aremote command.  When invoked by pdcp=
, it is not possible for ssh to=0Aprompt for confirmation if a host k=
ey changes, prompt for passwords if=0ARSA keys are not configured pro=
perly, etc..  Finally, the connect=0Atimeout is only adjustable with =
ssh when the underlying ssh implementation=0Asupports it, and pdsh ha=
s been built to use the correct option.=0A                           =
                                        =0A.SH ATTRIBUTES=0A.sp=0A.LP=
=0ASee \fBattributes\fR(5) for descriptions of the following attribut=
es:=0A.sp=0A=0A.sp=0A.TS=0Atab(=07) box;=0Acw(2.75i) |cw(2.75i) =0Alw=
(2.75i) |lw(2.75i) =0A.=0AATTRIBUTE TYPE=07ATTRIBUTE VALUE=0A_=0AAvai=
lability=07SUNWpdsh=0A_=0AInterface Stability=07uncommitted=0A.TE=
=0A=0A.SH "SEE ALSO"=0Apdsh(1)=0A=

--Boundary_(ID_b1FlBRXwNB6pB84SpHAFHw)
Content-type: text/plain; name=pdcp.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=pdcp.txt




User Commands						  pdsh(1)



NAME
     pdcp - copy files to groups of hosts in parallel
     rpdcp - (reverse pdcp) copy files from a group of	hosts  in
     parallel


SYNOPSIS
     pdcp [options]... src [src2...] dest
     rpdcp [options]...	src [src2...] dir


DESCRIPTION
     pdcp is a variant of the  rcp(1)  command.	  Unlike  rcp(1),
     which  copies  files  to a	single remote host, pdcp can copy
     files to multiple remote hosts in parallel.   However,  pdcp
     does not recognize	files in the format ``rname@rhost:path,''
     therefore all  source  files  must	 be  on	 the  local  host
     machine.	Destination nodes must be listed on the	pdcp com-
     mand line using a suitable	target nodelist	option	(See  the
     OPTIONS  section  below).	Each destination node listed must
     have pdcp installed for the copy to succeed.

     When pdcp receives	SIGINT (ctrl-C), it lists the  status  of
     current  threads.	 A  second  SIGINT within one second ter-
     minates the program. Pending  threads  may	 be  canceled  by
     issuing ctrl-Z within one second of ctrl-C.  Pending threads
     are those that have not yet been initiated, or are	still  in
     the process of connecting to the remote host.

     Like pdsh(1), the functionality of	pdcp may be  supplemented
     by	 dynamically  loadable	modules. In pdcp, the modules may
     provide a	new  connect  protocol	(replacing  the	 standard
     rsh(1)  protocol),	 filtering  options (e.g. excluding hosts
     that are down),  and/or  host  selection  options	(e.g.  -a
     selects  all  nodes  from a local config file).  By default,
     pdcp requires at least one	"rcmd" module to  be  loaded  (to
     provide the channel for remote copy).


REVERSE	PDCP
     rpdcp performs a reverse parallel copy.  Rather than copying
     files to remote hosts, files are retrieved	from remote hosts
     and stored	locally.  All directories or files retrieved will
     be	 stored	 with  their  remote  hostname	appended  to  the
     filename.	The destination	file must  be  a  directory  when
     this option is used.

     In	other respects,	rpdcp is exactly like pdcp,  and  further
     statements	 regarding  pdcp  in  this  manual  also apply to
     rpdcp.





pdsh-2.18	    Last change: solaris2.11			1






User Commands						  pdsh(1)



RCMD MODULES
     The method	by which pdcp connects to  remote  hosts  may  be
     selected at runtime using the -R option (See OPTIONS below).
     This functionality	is ultimately implemented via dynamically
     loadable  modules,	 and so	the list of available options may
     be	different from installation to installation.  A	 list  of
     currently	available  rcmd	modules	is printed when	using any
     of	the -h,	-V, or -L options. The default rcmd  module  will
     also be displayed with the	-h and -V options.

     A list of rcmd modules currently distributed with pdcp  fol-
     lows.

     rsh     Uses an internal, thread-safe implementation of  BSD
	     rcmd(3)  to  run  commands	using the standard rsh(1)
	     protocol.

     ssh     Uses a variant of popen(3)	to run multiple	copies of
	     the ssh(1)	command.

     mrsh    This module uses the  mrsh(1)  protocol  to  execute
	     jobs  on  remote  hosts.	The  mrsh protocol uses	a
	     credential	based authentication, forgoing	the  need
	     to	 allocate  reserved  ports.  In	other aspects, it
	     acts just like rsh.

     krb4    The krb4 module allows users to execute remote  com-
	     mands after authenticating	with kerberos. Of course,
	     the remote	rshd daemons must be kerberized.

     xcpu    The xcpu module uses the  xcpu  service  to  execute
	     remote commands.


OPTIONS
     The list of available pdcp	options	is determined at  runtime
     by	 supplementing the list	of standard pdcp options with any
     options provided by loaded	rcmd and misc modules.	 In  some
     cases,  options  provided	by modules may conflict	with each
     other. In these cases, the	modules	are incompatible and  the
     first module loaded wins.


Standard target	nodelist options
     -w	host,host,...
	  Target the specified list of hosts. Do not use with any
	  other	 node  selection options (e.g. -a, -g if they are
	  available).  No  spaces  are	allowed	 in  the   comma-
	  separated  list.   A	list  consisting  of a single `-'
	  character causes the	target	hosts  to  be  read  from
	  stdin, one per line. The host	list may contain hostlist
	  expressions  of  the	form  ``host[1-5,7]''.	For  more



pdsh-2.18	    Last change: solaris2.11			2






User Commands						  pdsh(1)



	  information about the	hostlist format, see the HOSTLIST
	  EXPRESSIONS section below.

     -x	host,host,...
	  Exclude the specified	hosts. May be specified	 in  con-
	  junction with	other target node list options such as -a
	  and -g (when available). Hostlists may also  be  speci-
	  fied	to the -x option (see HOSTLIST EXPRESSIONS secion
	  below).


Standard pdcp options
     -h	  Output usage menu and	quit. A	list  of  available  rcmd
	  modules  will	 be  printed at	the end	of the usage mes-
	  sage.

     -q	  List option values and the  target  nodelist	and  exit
	  without action.

     -b	  Disable ctrl-C status	feature	so that	a  single  ctrl-C
	  kills	parallel copy. (Batch Mode)

     -r	  Copy directories recursively.

     -p	  Preserve modification	time and modes.

     -e	PATH
	  Explicitly specify path to remote pdcp  binary  instead
	  of using the locally executed	path.

     -l	user
	  This option may be used to copy files	as another  user,
	  subject  to authorization. For BSD rcmd, this	means the
	  invoking user	and system must	be listed in  the  user's
	  .rhosts file (even for root).

     -t	seconds
	  Set the connect timeout. Default is 10 seconds.

     -f	number
	  Set the maximum number of simultaneous remote	copies to
	  number.  The default is 32.

     -R	name
	  Set rcmd module to name. This	option may  also  be  set
	  via  the PDSH_RCMD_TYPE environment variable.	A list of
	  available rcmd modules may be	obtained via  either  the
	  -h or	-L options.

     -R	name
	  Set rcmd module to name. This	option may  also  be  set
	  via  the PDSH_RCMD_TYPE environment variable.	A list of



pdsh-2.18	    Last change: solaris2.11			3






User Commands						  pdsh(1)



	  available rcmd modules may be	obtained via  either  the
	  -h or	-L options.

     -L	  List info on all loaded pdcp modules and quit.

     -d	  Include more complete	 thread	 status	 when  SIGINT  is
	  received,  and display connect and command time statis-
	  tics on stderr when done.

     -V	  Output pdcp version information,  along  with	 list  of
	  currently loaded modules, and	exit.



HOSTLIST EXPRESSIONS
     As	noted in sections above, pdcp accepts ranges of	hostnames
     in	 the general form: prefix[n-m,l-k,...],	where n	< m and	l
     < k, etc.,	as an alternative to  explicit	lists  of  hosts.
     This  form	 should	 not  be confused with regular expression
     character classes (also denoted  by  ``[]'').  For	 example,
     foo[19]   does  not  represent  foo1  or  foo9,  but  rather
     represents	a degenerate range: foo19.

     This range	syntax is meant	only as	a convenience on clusters
     with  a  prefixNN	naming	convention  and	 specification of
     ranges should  not	 be  considered	 necessary  --	the  list
     foo1,foo9	could  be  specified  as  such,	 or  by	the range
     foo[1,9].

     Some examples of range usage follow:


     Copy /etc/hosts to	foo01,foo02,...,foo05
	 pdcp -w foo[01-05] /etc/hosts /etc

     Copy /etc/hosts to	foo7,foo9,foo10
	 pdcp -w foo[7,9-10] /etc/hosts	/etc

     Copy /etc/hosts to	foo0,foo4,foo5
      pdcp -w foo[0-5] -x foo[1-3] /etc/hosts /etc


     As	a reminder to the  reader,  some  shells  will	interpret
     brackets  ('['  and ']') for pattern matching.  Depending on
     your shell, it may	be  necessary  to  enclose  ranged  lists
     within  quotes.   For  example,  in  tcsh,	the first example
     above should be executed as:

	 pdcp -w "foo[01-05]" /etc/hosts /etc






pdsh-2.18	    Last change: solaris2.11			4






User Commands						  pdsh(1)



ORIGIN
     Pdsh/pdcp was originally a	rewrite	of IBM dsh(1) by Jim Gar-
     lick  <garlick@llnl.gov>  on LLNL's ASCI Blue-Pacific IBM SP
     system.  It is now	also used on Linux clusters at LLNL.


LIMITATIONS
     When using	ssh for	remote execution, stderr  of  ssh  to  be
     folded  in	with that of the remote	command.  When invoked by
     pdcp, it is not possible for ssh to prompt	for  confirmation
     if	 a host	key changes, prompt for	passwords if RSA keys are
     not configured properly, etc..  Finally, the connect timeout
     is	 only  adjustable with ssh when	the underlying ssh imple-
     mentation supports	it, and	pdsh has been built  to	 use  the
     correct option.


ATTRIBUTES
     See attributes(5) for descriptions	of the	following  attri-
     butes:



     ____________________________________________________________
    |	    ATTRIBUTE TYPE	  |	  ATTRIBUTE VALUE	|
    |_____________________________|_____________________________|
    | Availability		  | SUNWpdsh			|
    |_____________________________|_____________________________|
    | Interface	Stability	  | uncommitted			|
    |_____________________________|_____________________________|


SEE ALSO
     pdsh(1)





















pdsh-2.18	    Last change: solaris2.11			5




--Boundary_(ID_b1FlBRXwNB6pB84SpHAFHw)
Content-type: application/octet-stream; name=pdsh.1
Content-transfer-encoding: QUOTED-PRINTABLE
Content-disposition: attachment; filename=pdsh.1

'\" te=0A.\"^M=0A.\" CDDL HEADER START^M=0A.\"^M=0A.\" The contents o=
f this file are subject to the terms of the^M=0A.\" Common Developmen=
t and Distribution License (the "License").^M=0A.\" You may not use t=
his file except in compliance with the License.^M=0A.\"^M=0A.\" You c=
an obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE^M=0A.\=
" or http://www.opensolaris.org/os/licensing.^M=0A.\" See the License=
 for the specific language governing permissions^M=0A.\" and limitati=
ons under the License.^M=0A.\"^M=0A.\" When distributing Covered Code=
, include this CDDL HEADER in each^M=0A.\" file and include the Licen=
se file at usr/src/OPENSOLARIS.LICENSE.^M=0A.\" If applicable, add th=
e following below this CDDL HEADER, with the^M=0A.\" fields enclosed =
by brackets "[]" replaced with your own identifying^M=0A.\" informati=
on: Portions Copyright [yyyy] [name of copyright owner]^M=0A.\"^M=
=0A.\" CDDL HEADER END^M=0A.\"^M=0A.\" Copyright 2009 Sun Microsystem=
s, Inc. All rights reserved.^M=0A.\" Use is subject to license terms.=
^M=0A.\"^M=0A\." $Id: pdsh.1.in 1177 2009-03-24 21:46:00Z grondo $=
=0A.TH "pdsh" "1" "solaris2.11" "pdsh-2.18"=0A=0A.SH NAME=0Apdsh \- i=
ssue commands to groups of hosts in parallel=0A=0A.SH SYNOPSIS=0A\fBp=
dsh\fR [\fIoptions\fR]... command=0A=0A.SH DESCRIPTION=0A\fBpdsh\fR i=
s a variant of the rsh(1) command. Unlike rsh(1), which runs=0Acomman=
ds on a single remote host, \fBpdsh\fR can run multiple remote comman=
ds=0Ain parallel. \fBpdsh\fR uses a "sliding window" (or \fIfanout\fR=
) of threads=0Ato conserve resources on the initiating host while all=
owing some=0Aconnections to time out.=0A.LP=0AWhen \fBpdsh\fR receive=
s SIGINT (ctrl-C), it lists the status of current=0Athreads. A second=
 SIGINT within one second terminates the program. Pending=0Athreads m=
ay be canceled by issuing ctrl-Z within one second of ctrl-C.=0APendi=
ng threads are those that have not yet been initiated, or are still=
=0Ain the process of connecting to the remote host.=0A=0A.LP=0AIf a r=
emote command is not specified on the command line, \fBpdsh\fR=0Aruns=
 interactively, prompting for commands and executing them when=0Aterm=
inated with a carriage return. In interactive mode, target nodes=0Ath=
at time out on the first command are not contacted for subsequent=
=0Acommands, and commands prefixed with an exclamation point will be=
=0Aexecuted on the local system.=0A.LP=0AThe core functionality of \f=
Bpdsh\fR may be supplemented by dynamically=0Aloadable modules. The m=
odules may provide a new connection protocol=0A(replacing the standar=
d rcmd(3) protocol used by rsh(1)), filtering=0Aoptions (e.g. removin=
g hosts that are "down" from the target list),=0Aand/or host selectio=
n options (e.g., \fI\-a\fR selects all hosts from=0Aa configuration f=
ile.). By default, \fBpdsh\fR must have at least=0Aone "rcmd" module =
loaded. See the \fBRCMD MODULES\fR section for more=0Ainformation.=
=0A=0A.SH "RCMD MODULES"=0AThe method by which \fBpdsh\fR runs comman=
ds on remote hosts may be=0Aselected at runtime using the \fI-R\fR op=
tion (See \fIOPTIONS\fR below).=0AThis functionality is ultimately im=
plemented via dynamically loadable=0Amodules, and so the list of avai=
lable options may be different=0Afrom installation to installation. A=
 list of currently available rcmd=0Amodules is printed when using any=
 of the \fI-h\fR, \fI-V\fR, or \fI-L\fR=0Aoptions. The default rcmd m=
odule will also be displayed with the=0A\fI-h\fR and \fI-V\fR options=
.=0A.LP=0AA list of \fIrcmd\fR modules currently distributed with \fB=
pdsh\fR=0Afollows.=0A.TP 8=0Arsh=0AUses an internal, thread-safe impl=
ementation of BSD rcmd(3)=0Ato run commands using the standard rsh(1)=
 protocol.=0A.TP=0Aexec=0AExecutes an arbitrary command for each targ=
et host. The first=0Aof the \fBpdsh\fR remote arguments is the local =
command=0Ato execute, followed by any further arguments. Some simple=
=0Aparameters are substitued on the command line, including=0A\fI%h\f=
R for the target hostname, \fI%u\fR for the remote=0Ausername, and \f=
I%n\fR for the remote rank [0-n] (To get=0Aa literal \fI%\fR use \fI%=
%\fR).  For example,=0Athe following would duplicate using the \fBssh=
\fR module to=0Arun \fBhostname\fR(1) across the hosts foo[0-10]:=
=0A=0A.nf=0A   pdsh -R exec -w foo[0-10] ssh -x -l %u %h hostname=
=0A.fi=0A=0Aand this command line would run \fBgrep\fR(1) in parallel=
=0Aacross the files console.foo[0-10]:=0A=0A.nf=0A   pdsh -R exec -w =
foo[0-10] grep BUG console.%h=0A.fi=0A=0A.TP=0Assh=0AUses a variant o=
f popen(3) to run multiple copies of the ssh(1)=0Acommand.=0A.TP=0Amr=
sh=0AThis module uses the mrsh(1) protocol to execute jobs on remote =
hosts.=0AThe mrsh protocol uses a credential based authentication, fo=
rgoing=0Athe need to allocate reserved ports. In other aspects, it ac=
ts just=0Alike rsh. Remote nodes must be running mrshd(8) in order fo=
r the mrsh=0Amodule to work.=0A.TP=0Aqsh=0AAllows \fBpdsh\fR to execu=
te MPI jobs over QsNet. Qshell propagates=0Athe current working direc=
tory, pdsh environment, and Elan capabilities=0Ato the remote process=
. The following environment variable are also=0Aappended to the envir=
onment: RMS_RANK, RMS_NODEID, RMS_PROCID, RMS_NNODES,=0Aand RMS_NPROC=
S. Since \fBpdsh\fR needs to run setuid root for qshell=0Asupport, qs=
hell does not directly support propagation of LD_LIBRARY_PATH=0Aand L=
D_PREOPEN. Instead the QSHELL_REMOTE_LD_LIBRARY_PATH and=0AQSHELL_REM=
OTE_LD_PREOPEN environment variables will may be used and will=0Abe r=
emapped to LD_LIBRARY_PATH and LD_PREOPEN by the qshell daemon if set=
.=0A.TP=0Amqsh=0ASimilar to qshell, but uses the mrsh protocol instea=
d of the rsh protocol.=0A.TP=0Akrb4=0AThe krb4 module allows users to=
 execute remote commands after=0Aauthenticating with kerberos. Of cou=
rse, the remote rshd daemons=0Amust be kerberized.=0A.TP=0Axcpu=0AThe=
 xcpu module uses the xcpu service to execute remote commands.=0A=
=0A.SH OPTIONS=0AThe list of available options is determined at runti=
me=0Aby supplementing the list of standard \fBpdsh\fR options with=
=0Aany options provided by loaded \fIrcmd\fR and \fImisc\fR modules.=
=0AIn some cases, options provided by modules may conflict with=0Aeac=
h other. In these cases, the modules are incompatible and=0Athe first=
 module loaded wins.=0A=0A.SH "Standard target nodelist options"=0A.T=
P=0A.I "-w [rcmd_type:][user@]host,host,..."=0ATarget the specified l=
ist of hosts. Do not use with any other=0Anode selection options (e.g=
. \fI\-a\fR, \fI\-g\fR if they are=0Aavailable). No spaces are allowe=
d in the comma-separated list.=0AA list consisting of a single `-' ch=
aracter causes the target=0Ahosts to be read from stdin, one per line=
. The host list may=0Acontain hostlist expressions of the form ``host=
[1-5,7]''. For=0Amore information about the hostlist format, see the=
=0A\fBHOSTLIST EXPRESSIONS\fR section below. A list of hosts=0Amay al=
so be preceded by "user@" to specify a remote username=0Aother than t=
he default, or "rcmd_type:" to specify an alternate=0Arcmd connection=
 type for these hosts. When used together,=0Athe rcmd type must be sp=
ecified first, e.g. "ssh:user1@host0"=0Awould use ssh to connect to h=
ost0 as user "user1."=0A.TP=0A.I "-x host,host,..."=0AExclude the spe=
cified hosts. May be specified in conjunction with=0Aother target nod=
e list options such as \fI\-a\fR and \fI\-g\fR (when=0Aavailable). Ho=
stlists may also be specified to the \fI\-x\fR option=0A(see the \fBH=
OSTLIST EXPRESSIONS\fR section below).=0A=0A.SH "Standard pdsh option=
s"=0A.TP=0A.I "-S"=0AReturn the largest of the remote command return =
values.=0A.TP=0A.I "-h"=0AOutput usage menu and quit. A list of avail=
able rcmd modules=0Awill also be printed at the end of the usage mess=
age.=0A.TP=0A.I "-s"=0AOnly on AIX, separate remote command stderr an=
d stdout into two sockets.=0A.TP=0A.I "-q"=0AList option values and t=
he target nodelist and exit without action.=0A.TP=0A.I "-b"=0ADisable=
 ctrl-C status feature so that a single ctrl-C kills parallel=0Ajob. =
(Batch Mode)=0A.TP=0A.I "-l user"=0AThis option may be used to run re=
mote commands as another user, subject to=0Aauthorization. For BSD rc=
md, this means the invoking user and system must=0Abe listed in the u=
ser\'s .rhosts file (even for root).=0A.TP=0A.I "-t seconds"=0ASet th=
e connect timeout. Default is 10 seconds.=0A.TP=0A.I "-u seconds"=
=0ASet a limit on the amount of time a remote command is allowed to e=
xecute.=0ADefault is no limit. See note in LIMITATIONS if using \fI-u=
\fR with ssh.=0A.TP=0A.I "-f number"=0ASet the maximum number of simu=
ltaneous remote commands to \fInumber\fR.=0AThe default is 32.=0A.TP=
=0A.I "-R name"=0ASet rcmd module to \fIname\fR. This option may also=
 be set via the=0APDSH_RCMD_TYPE environment variable. A list of avai=
lable rcmd=0Amodules may be obtained via the \fI-h\fR, \fI-V\fR, or \=
fI-L\fR options.=0AThe default will be listed with \fI-h\fR or \fI-V\=
fI.=0A.TP=0A.I "-L"=0AList info on all loaded \fBpdsh\fR modules and =
quit.=0A.TP=0A.I "-N"=0ADisable hostname: prefix on lines of output.=
=0A.TP=0A.I "-d"=0AInclude more complete thread status when SIGINT is=
 received, and display=0Aconnect and command time statistics on stder=
r when done.=0A.TP=0A.I "-V"=0AOutput \fBpdsh\fR version information,=
 along with list of currently=0Aloaded modules, and exit.=0A=0A.SH "q=
sh/mqsh module options"=0A.TP=0A.I "-n tasks_per_node"=0ASet the numb=
er of tasks spawned per node. Default is 1.=0A.TP=0A.I "-m block | cy=
clic"=0ASet block versus cyclic allocation of processes to nodes. Def=
ault is=0Ablock.=0A.TP=0A.I "-r railmask"=0ASet the rail bitmask for =
a job on a multirail system. The default=0Arailmask is 1, which corre=
sponds to rail 0 only. Each bit set in=0Athe argument to \fI-r\fR cor=
responds to a rail on the system, so=0Aa value of 2 would correspond =
to rail 1 only, and 3 would indicate=0Ato use both rail 1 and rail 0.=
=0A=0A.SH "machines module options"=0A.TP=0A.I "-a"=0ATarget all node=
s from machines file.=0A=0A.SH "genders module options"=0A.LP=0AIn ad=
dition to the genders options presented below, the genders=0Aattribut=
e pdsh_rcmd_type may also be used in the genders database=0Ato specif=
y an alternate rcmd connect type than the pdsh default=0Ain the gende=
rs file=0A.nf=0A=0A  host0 pdsh_rcmd_type=3Dssh=0A=0A.fi=0Awould caus=
e \fBpdsh\fR to use ssh to connect to host0, even if rsh were=0Athe d=
efault.  This can be overridden on the commandline with the=0A"rcmd_t=
ype:host0" syntax.=0A=0A.TP=0A.I "-A"=0ATarget all nodes in genders d=
atabase. The \fI-A\fR option will target=0Aevery host listed in gende=
rs -- if you want to omit some hosts by default,=0Asee the \fI-a\fR o=
ption below.=0A.TP=0A.I "-a"=0ATarget all nodes in genders database e=
xcept those with the "pdsh_all_skip"=0Aattribute. This is shorthand f=
or running "pdsh -A -X pdsh_all_skip ..."=0A.TP=0A.I "-g attr[=3Dval]=
[,attr[=3Dval],...]"=0ATarget nodes that match any of the specified g=
enders attributes (with=0Aoptional values). Conflicts with \fI\-a\fR =
and \fI\-w\fR options. This=0Aoption targets the alternate hostnames =
in the genders database by=0Adefault. The \fI\-i\fR option provided b=
y the genders module may be used=0Ato translate these to the canonica=
l genders hostnames. If the installed=0Aversion of genders supports i=
t, attributes supplied to \fI-g\fR may also=0Atake the form of gender=
s \fBqueries\fR. Genders \fBqueries\fR will query=0Athe genders datab=
ase for the union, intersection, difference, or complement=0Aof gende=
rs attributes and values.  The set operation union is represented=
=0Aby two pipe symbols ('||'), intersection by two ampersand symbols =
('&&'),=0Adifference by two minus symbols ('--'), and complement by a=
 tilde ('~').=0AParentheses may be used to change the order of operat=
ions. See the=0Anodeattr(1) manpage for examples of genders \fBquerie=
s\fR.=0A.TP=0A.I "-X attr[=3Dval][,attr[=3Dval],...]"=0AExclude nodes=
 that match any of the specified genders attributes=0A(optionally wit=
h values).  This option may be used in combination with any=0Aother o=
f the node selection options (e.g. \fI-w\fR, \fI-g\fR, \fI-a\fR,=0A..=
.). If the installed version of genders supports it, arguments to=
=0A\fI-X\fR may also take the form of genders \fBqueries\fR. Please s=
ee=0Adocumentation for the genders \fI-g\fR option for more informati=
on about=0Agenders \fBqueries\fR.=0A.TP=0A.I "-i"=0ARequest translati=
on between canonical and alternate hostnames.=0A.TP=0A.I "-F filename=
"=0ARead genders information from \fIfilename\fR instead of the syste=
m=0Adefault genders file.=0A=0A.SH "nodeupdown module options"=0A.TP=
=0A.I "-v"=0AEliminate target nodes that are considered "down" by lib=
nodeupdown.=0A=0A.SH "slurm module options"=0AThe \fBslurm\fI module =
allows \fBpdsh\fR to target nodes based on=0Acurrently running SLURM =
jobs. The \fBslurm\fR module is typically=0Acalled after all other no=
de selection options have been processed,=0Aand if no nodes have been=
 selected, the module will attempt to=0Aread a running jobid from the=
 SLURM_JOBID environment variable=0A(which is set when running under =
a SLURM allocation). If SLURM_JOBID=0Areferences an invalid job, it w=
ill be silently ignored.=0A.TP=0A.I "-j jobid[,jobid,...]"=0ATarget l=
ist of nodes allocated to the SLURM job \fIjobid\fR. This option=0Ama=
y be used multiple times to target multiple SLURM jobs. The special=
=0Aargument "all" can be used to target all nodes running SLURM jobs,=
 e.g.=0A\fI-j all\fR.=0A=0A.SH "rms module options"=0AThe \fBrms\fR m=
odule allows pdsh to target nodes based on an RMS=0Aresource. The \fB=
rms\fR module is typically called after all other=0Anode selection op=
tions, and if no nodes have been selected, the=0Amodule will examine =
the RMS_RESOURCEID environment variable and=0Aattempt to set the targ=
et list of hosts to the nodes in the=0ARMS resource. If an invalid re=
source is denoted, the variable is=0Asilently ignored.=0A=0A.SH "SDR =
module options"=0AThe SDR module supports targeting hosts via the Sys=
tem Data Repository=0Aon IBM SPs.=0A.TP=0A.I "-a"=0ATarget all nodes =
in the SDR. The list is generated from the=0A"reliable hostname" in t=
he SDR by default.=0A.TP=0A.I "-i"=0ATranslate hostnames between reli=
able and initial in the SDR, when applicable.=0AIf the a target hostn=
ame matches either the initial or reliable hostname=0Ain the SDR, the=
 alternate name will be substitued. Thus a list composed=0Aof initial=
 hostnames will instead be replaced with a list of reliable hostnames=
.=0AFor example, when used with \fI-a\fR above, all initial hostnames=
 in=0Athe SDR are targeted.=0A.TP=0A.I "-v"=0ADo not target nodes tha=
t are marked as not responding in the SDR on=0Athe targeted interface=
. (If a hostname does not appear in the SDR, then=0Athat name will re=
main in the target hostlist.)=0A.TP=0A.I "-G"=0AIn combination with \=
fI-a\fR, include all partitions.=0A=0A.SH "nodeattr module options"=
=0AThe \fBnodeattr\fR module supports access to the genders database=
=0Avia the nodeattr(1) command. See the \fBgenders\fR section above=
=0Afor a list of support options with this module. The option usage=
=0Awith the \fBnodeattr\fR module is the same as \fBgenders\fR, above=
,=0Awith the exception that the \fI-i\fR option may only be used=0Awi=
th \fI-a\fR or \fI-g\fR. \fBNOTE\fR: This module will only=0Awork wit=
h very old releases of genders where the \fBnodeattr\fR(1)=0Acommand =
supports the \fI-r\fR option, and before the libgenders=0AAPI was ava=
ilable. Users running newer versions of genders=0Awill need to use th=
e \fBgenders\fR module instead.=0A=0A.SH "dshgroup module options"=
=0AThe dshgroup module allows pdsh to use dsh (or Dancer's shell) sty=
le=0Agroup files from /etc/dsh/group/ or ~/.dsh/group/.=0A.TP=0A.I "-=
g groupname,..."=0ATarget nodes in dsh group file "groupname" found i=
n either=0A~/.dsh/group/groupname or /etc/dsh/group/groupname.=0A.TP=
=0A.I "-X groupname,..."=0AExclude nodes in dsh group file "groupname=
."=0A=0A.SH "netgroup module options"=0AThe netgroup module allows pd=
sh to use standard netgroup entries to=0Abuild lists of target hosts.=
 (/etc/netgroup or NIS)=0A.TP=0A.I "-g groupname,..."=0ATarget nodes =
in netgroup "groupname."=0A.TP=0A.I "-X groupname,..."=0AExclude node=
s in netgroup "groupname."=0A=0A.SH "ENVIRONMENT VARIABLES"=0A.PP=
=0A.TP=0APDSH_RCMD_TYPE=0AEquivalent to the \fI-R\fR option, the valu=
e of this environment=0Avariable will be used to set the default rcmd=
 module for pdsh to=0Ause (e.g. ssh, rsh).=0A.TP=0APDSH_SSH_ARGS=0AOv=
erride the standard arguments that \fBpdsh\fR passes to the=0Assh(1) =
command ("-2 -a -x").=0A.TP=0APDSH_SSH_ARGS_APPEND=0AAppend additiona=
l options to the ssh(1) command invoked by \fBpdsh\fR.=0AFor example,=
 PDSH_SSH_ARGS_APPEND=3D"-q" would run ssh in quiet mode,=0Aor "-v" w=
ould increase the verbosity of ssh.=0A.TP=0AWCOLL=0AIf no other node =
selection option is used, the WCOLL environment=0Avariable may be set=
 to a filename from which a list of target=0Ahosts will be read. The =
file should contain a list of hosts,=0Aone per line (though each line=
 may contain a hostlist expression.=0ASee \fIHOSTLIST EXPRESSIONS\fR =
section below).=0A.TP=0ADSHPATH=0AIf set, the path in DSHPATH will be=
 used as the PATH for the=0Aremote processes.=0A.TP=0AFANOUT=0ASet th=
e \fBpdsh\fR fanout (See description of \fI-f\fR above).=0A=0A.SH "HO=
STLIST EXPRESSIONS"=0AAs noted in sections above \fBpdsh\fR accepts l=
ists of hosts the general=0Aform: prefix[n-m,l-k,...], where n < m an=
d l < k, etc., as an alternative=0Ato explicit lists of hosts. This f=
orm should not be confused with regular=0Aexpression character classe=
s (also denoted by ``[]''). For example, foo[19]=0Adoes not represent=
 an expression matching foo1 or foo9, but rather=0Arepresents the deg=
enerate hostlist: foo19.=0A=0AThe hostlist syntax is meant only as a =
convenience on clusters with a=0A"prefixNNN" naming convention and sp=
ecification of ranges should not be=0Aconsidered necessary -- this fo=
o1,foo9 could be specified as such, or=0Aby the hostlist foo[1,9].=
=0A=0ASome examples of usage follow:=0A=0A.nf=0A=0ARun command on foo=
01,foo02,...,foo05=0A    pdsh -w foo[01-05] command=0A=0ARun command =
on foo7,foo9,foo10=0A    pdsh -w foo[7,9-10] command=0A=0ARun command=
 on foo0,foo4,foo5=0A    pdsh -w foo[0-5] -x foo[1-3] command=0A=0A.f=
i=0A=0AA suffix on the hostname is also supported:=0A=0A.nf=0A=0ARun =
command on foo0-eth0,foo1-eth0,foo2-eth0,foo3-eth0=0A   pdsh -w foo[0=
-3]-eth0 command=0A=0A.fi=0A=0AAs a reminder to the reader, some shel=
ls will interpret brackets ('['=0Aand ']') for pattern matching.  Dep=
ending on your shell, it may be=0Anecessary to enclose ranged lists w=
ithin quotes.  For example, in=0Atcsh, the first example above should=
 be executed as:=0A=0A    pdsh -w "foo[01-05]" command=0A=0A.SH "ORIG=
IN"=0AOriginally a rewrite of IBM dsh(1) by Jim Garlick <garlick@llnl=
.gov>=0Aon LLNL's ASCI Blue-Pacific IBM SP system. It is now used on =
Linux clusters=0Aat LLNL.=0A=0A.SH "LIMITATIONS"=0A.LP=0AWhen using \=
fBssh\fR for remote execution, expect the stderr of ssh to be=0Afolde=
d in with that of the remote command. When invoked by \fBpdsh\fR, it=
=0Ais not possible for \fBssh\fR to prompt for passwords if RSA/DSA k=
eys=0Aare configured properly, etc..  For \fBssh\fR implementations t=
hat suppport=0Aa connect timeout option, \fBpdsh\fR attempts to use t=
hat option to=0Aenforce the timeout (e.g. -oConnectTimeout=3DT for Op=
enSSH), otherwise=0Aconnect timeouts are not supported when using \fB=
ssh\fR.  Finally, there=0Ais no reliable way for \fBpdsh\fR to ensure=
 that remote commands are=0Aactually terminated when using a command =
timeout. Thus if \fI-u\fR is=0Aused with \fBssh\fR commands may be le=
ft running on remote hosts even=0Aafter timeout has killed local \fBs=
sh\fR processes.=0A=0AOutput from multiple processes per node may be =
interspersed when using qshell=0Aor mqshell rcmd modules.=0A=0AThe nu=
mber of nodes that \fBpdsh\fR can simultaneously execute remote=0Ajob=
s on is limited by the maximum number of threads that can be created=
=0Aconcurrently, as well as the availability of reserved ports in the=
 rsh=0Aand qshell rcmd modules. On systems that implement Posix threa=
ds, the limit=0Ais typically defined by the constant PTHREADS_THREADS=
_MAX.=0A=0A.SH "FILES"=0A =0A.SH ATTRIBUTES=0A.sp=0A.LP=0ASee \fBattr=
ibutes\fR(5) for descriptions of the following attributes:=0A.sp=0A=
=0A.sp=0A.TS=0Atab(=07) box;=0Acw(2.75i) |cw(2.75i) =0Alw(2.75i) |lw(=
2.75i) =0A.=0AATTRIBUTE TYPE=07ATTRIBUTE VALUE=0A_=0AAvailability=
=07SUNWpdsh=0A_=0AInterface Stability=07uncommitted=0A.TE=0A=0A.SH "S=
EE ALSO"=0Arsh(1), ssh(1), dshbak(1), pdcp(1)=0Ahttp://sourceforge.ne=
t/projects/pdsh/=0A.SH "NOTES"=0ASource for pdsh is available on http=
://opensolaris.org=0A=0A=0A=

--Boundary_(ID_b1FlBRXwNB6pB84SpHAFHw)
Content-type: text/plain; name=pdsh.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=pdsh.txt




User Commands						  pdsh(1)



NAME
     pdsh - issue commands to groups of	hosts in parallel


SYNOPSIS
     pdsh [options]... command


DESCRIPTION
     pdsh is a variant of  the	rsh(1)	command.  Unlike  rsh(1),
     which  runs  commands  on a single	remote host, pdsh can run
     multiple remote commands in parallel. pdsh	uses  a	 "sliding
     window"  (or fanout) of threads to	conserve resources on the
     initiating	host while allowing some connections to	time out.

     When pdsh receives	SIGINT (ctrl-C), it lists the  status  of
     current  threads.	A  second  SIGINT  within one second ter-
     minates the program. Pending  threads  may	 be  canceled  by
     issuing ctrl-Z within one second of ctrl-C.  Pending threads
     are those that have not yet been initiated, or are	still  in
     the process of connecting to the remote host.


     If	a remote command is not	specified on  the  command  line,
     pdsh  runs	interactively, prompting for commands and execut-
     ing them when terminated with a carriage return. In interac-
     tive  mode,  target nodes that time out on	the first command
     are not contacted for subsequent commands,	and commands pre-
     fixed  with  an  exclamation  point  will be executed on the
     local system.

     The core functionality of pdsh may	be supplemented	by dynam-
     ically  loadable modules. The modules may provide a new con-
     nection protocol (replacing the  standard	rcmd(3)	 protocol
     used by rsh(1)), filtering	options	(e.g. removing hosts that
     are "down"	from the  target  list),  and/or  host	selection
     options  (e.g.,  -a  selects  all hosts from a configuration
     file.). By	default, pdsh  must  have  at  least  one  "rcmd"
     module  loaded. See the RCMD MODULES section for more infor-
     mation.


RCMD MODULES
     The method	by which pdsh runs commands on remote  hosts  may
     be	 selected  at  runtime	using  the -R option (See OPTIONS
     below).  This functionality is  ultimately	 implemented  via
     dynamically  loadable  modules, and so the	list of	available
     options may be different from installation	to  installation.
     A	list  of currently available rcmd modules is printed when
     using any of the -h, -V, or -L  options.  The  default  rcmd
     module will also be displayed with	the -h and -V options.




pdsh-2.18	    Last change: solaris2.11			1






User Commands						  pdsh(1)



     A list of rcmd modules currently distributed with pdsh  fol-
     lows.

     rsh     Uses an internal, thread-safe implementation of  BSD
	     rcmd(3)  to  run  commands	using the standard rsh(1)
	     protocol.

     exec    Executes an arbitrary command for each target  host.
	     The  first	of the pdsh remote arguments is	the local
	     command to	execute, followed by  any  further  argu-
	     ments.  Some simple parameters are	substitued on the
	     command line, including %h	for the	target	hostname,
	     %u	 for  the  remote username, and	%n for the remote
	     rank [0-n]	(To get	a literal % use	%%).   For  exam-
	     ple,  the	following  would  duplicate using the ssh
	     module to run hostname(1) across  the  hosts  foo[0-
	     10]:

		pdsh -R	exec -w	foo[0-10] ssh -x -l %u %h hostname

	     and this command line would run grep(1) in	 parallel
	     across the	files console.foo[0-10]:

		pdsh -R	exec -w	foo[0-10] grep BUG console.%h


     ssh     Uses a variant of popen(3)	to run multiple	copies of
	     the ssh(1)	command.

     mrsh    This module uses the  mrsh(1)  protocol  to  execute
	     jobs  on  remote  hosts.	The  mrsh protocol uses	a
	     credential	based authentication, forgoing	the  need
	     to	 allocate  reserved  ports.  In	other aspects, it
	     acts just like rsh. Remote	 nodes	must  be  running
	     mrshd(8) in order for the mrsh module to work.

     qsh     Allows pdsh to execute MPI	jobs over  QsNet.  Qshell
	     propagates	  the  current	working	 directory,  pdsh
	     environment, and Elan  capabilities  to  the  remote
	     process. The following environment	variable are also
	     appended to the environment:  RMS_RANK,  RMS_NODEID,
	     RMS_PROCID,  RMS_NNODES,  and RMS_NPROCS. Since pdsh
	     needs to run setuid root for qshell support,  qshell
	     does    not    directly   support	 propagation   of
	     LD_LIBRARY_PATH   and   LD_PREOPEN.   Instead    the
	     QSHELL_REMOTE_LD_LIBRARY_PATH		      and
	     QSHELL_REMOTE_LD_PREOPEN environment variables  will
	     may  be used and will be remapped to LD_LIBRARY_PATH
	     and LD_PREOPEN by the qshell daemon if set.

     mqsh    Similar  to  qshell,  but	uses  the  mrsh	 protocol
	     instead of	the rsh	protocol.



pdsh-2.18	    Last change: solaris2.11			2






User Commands						  pdsh(1)



     krb4    The krb4 module allows users to execute remote  com-
	     mands after authenticating	with kerberos. Of course,
	     the remote	rshd daemons must be kerberized.

     xcpu    The xcpu module uses the  xcpu  service  to  execute
	     remote commands.


OPTIONS
     The list of available options is determined  at  runtime  by
     supplementing  the	 list  of  standard pdsh options with any
     options provided by loaded	rcmd and misc modules.	 In  some
     cases,  options  provided	by modules may conflict	with each
     other. In these cases, the	modules	are incompatible and  the
     first module loaded wins.


Standard target	nodelist options
     -w	[rcmd_type:][user@]host,host,...
	  Target the specified list of hosts. Do not use with any
	  other	 node  selection options (e.g. -a, -g if they are
	  available).  No  spaces  are	allowed	 in  the   comma-
	  separated  list.   A	list  consisting  of a single `-'
	  character causes the	target	hosts  to  be  read  from
	  stdin, one per line. The host	list may contain hostlist
	  expressions  of  the	form  ``host[1-5,7]''.	For  more
	  information about the	hostlist format, see the HOSTLIST
	  EXPRESSIONS section below. A list of hosts may also  be
	  preceded  by "user@" to specify a remote username other
	  than the default, or "rcmd_type:" to specify an  alter-
	  nate	rcmd  connection  type for these hosts.	When used
	  together, the	rcmd type must be specified  first,  e.g.
	  "ssh:user1@host0"  would use ssh to connect to host0 as
	  user "user1."

     -x	host,host,...
	  Exclude the specified	hosts. May be specified	 in  con-
	  junction with	other target node list options such as -a
	  and -g (when available). Hostlists may also  be  speci-
	  fied	to  the	 -x  option (see the HOSTLIST EXPRESSIONS
	  section below).


Standard pdsh options
     -S	  Return the largest of	the remote command return values.

     -h	  Output usage menu and	quit. A	list  of  available  rcmd
	  modules  will	 also  be printed at the end of	the usage
	  message.

     -s	  Only on AIX, separate	remote command stderr and  stdout
	  into two sockets.



pdsh-2.18	    Last change: solaris2.11			3






User Commands						  pdsh(1)



     -q	  List option values and the  target  nodelist	and  exit
	  without action.

     -b	  Disable ctrl-C status	feature	so that	a  single  ctrl-C
	  kills	parallel job. (Batch Mode)

     -l	user
	  This option may be  used  to	run  remote  commands  as
	  another  user,  subject to authorization. For	BSD rcmd,
	  this means the invoking user and system must be  listed
	  in the user's	.rhosts	file (even for root).

     -t	seconds
	  Set the connect timeout. Default is 10 seconds.

     -u	seconds
	  Set a	limit on the amount of time a remote  command  is
	  allowed  to  execute.	 Default is no limit. See note in
	  LIMITATIONS if using -u with ssh.

     -f	number
	  Set the maximum number of simultaneous remote	 commands
	  to number.  The default is 32.

     -R	name
	  Set rcmd module to name. This	option may  also  be  set
	  via  the PDSH_RCMD_TYPE environment variable.	A list of
	  available rcmd modules may be	obtained via the -h,  -V,
	  or  -L  options.  The	default	will be	listed with -h or
	  -V.

     -L	  List info on all loaded pdsh modules and quit.

     -N	  Disable hostname: prefix on lines of output.

     -d	  Include more complete	 thread	 status	 when  SIGINT  is
	  received,  and display connect and command time statis-
	  tics on stderr when done.

     -V	  Output pdsh version information,  along  with	 list  of
	  currently loaded modules, and	exit.


qsh/mqsh module	options
     -n	tasks_per_node
	  Set the number of tasks spawned per node. Default is 1.

     -m	block |	cyclic
	  Set block versus  cyclic  allocation	of  processes  to
	  nodes. Default is block.

     -r	railmask



pdsh-2.18	    Last change: solaris2.11			4






User Commands						  pdsh(1)



	  Set the rail bitmask for a job on a  multirail  system.
	  The  default railmask	is 1, which corresponds	to rail	0
	  only.	Each bit set in	the argument to	-r corresponds to
	  a  rail on the system, so a value of 2 would correspond
	  to rail 1 only, and 3	would indicate to use both rail	1
	  and rail 0.


machines module	options
     -a	  Target all nodes from	machines file.


genders	module options
     In	addition to the	 genders  options  presented  below,  the
     genders  attribute	 pdsh_rcmd_type	 may  also be used in the
     genders database to specify an alternate rcmd  connect  type
     than the pdsh default in the genders file

       host0 pdsh_rcmd_type=ssh

     would cause pdsh to use ssh to connect to host0, even if rsh
     were the default.	This can be overridden on the commandline
     with the "rcmd_type:host0"	syntax.


     -A	  Target all nodes in genders  database.  The  -A  option
	  will target every host listed	in genders -- if you want
	  to omit some hosts by	default, see the -a option below.

     -a	  Target all nodes in genders database except those  with
	  the  "pdsh_all_skip"	attribute.  This is shorthand for
	  running "pdsh	-A -X pdsh_all_skip ..."

     -g	attr[=val][,attr[=val],...]
	  Target nodes that match any of  the  specified  genders
	  attributes  (with  optional  values).	Conflicts with -a
	  and -w options. This option targets the alternate host-
	  names	in the genders database	by default. The	-i option
	  provided by the genders module may be	used to	translate
	  these	 to  the  canonical  genders  hostnames.  If  the
	  installed version of genders	supports  it,  attributes
	  supplied  to	-g  may	 also  take  the  form of genders
	  queries. Genders queries will	query the  genders  data-
	  base	for  the union,	intersection, difference, or com-
	  plement of genders  attributes  and  values.	 The  set
	  operation  union  is	represented  by	 two pipe symbols
	  ('||'), intersection by two ampersand	 symbols  ('&&'),
	  difference  by two minus symbols ('--'), and complement
	  by a tilde ('~').  Parentheses may be	 used  to  change
	  the  order  of  operations. See the nodeattr(1) manpage
	  for examples of genders queries.




pdsh-2.18	    Last change: solaris2.11			5






User Commands						  pdsh(1)



     -X	attr[=val][,attr[=val],...]
	  Exclude nodes	that match any of the  specified  genders
	  attributes  (optionally  with	values).  This option may
	  be used in combination  with	any  other  of	the  node
	  selection  options  (e.g.  -w, -g, -a, -X may	also take
	  the form of genders queries. Please  see  documentation
	  for  the  genders  -g	option for more	information about
	  genders queries.

     -i	  Request translation  between	canonical  and	alternate
	  hostnames.

     -F	filename
	  Read genders information from	filename instead  of  the
	  system default genders file.


nodeupdown module options
     -v	  Eliminate target nodes that are  considered  "down"  by
	  libnodeupdown.


slurm module options
     The slurm module  allows  pdsh  to	 target	 nodes	based  on
     currently	running	SLURM jobs. The	slurm module is	typically
     called after all other node selection options have	been pro-
     cessed,  and if no	nodes have been	selected, the module will
     attempt  to  read	a  running  jobid  from	 the  SLURM_JOBID
     environment  variable  (which  is	set  when running under	a
     SLURM allocation).	If SLURM_JOBID references an invalid job,
     it	will be	silently ignored.

     -j	jobid[,jobid,...]
	  Target list of nodes allocated to the	SLURM job  jobid.
	  This option may be used multiple times to target multi-
	  ple SLURM jobs. The special argument "all" can be  used
	  to target all	nodes running SLURM jobs, e.g.	-j all.


rms module options
     The rms module allows pdsh	to target nodes	based on  an  RMS
     resource. The rms module is typically called after	all other
     node selection options, and if no nodes have been	selected,
     the module	will examine the RMS_RESOURCEID	environment vari-
     able and attempt to set the target	 list  of  hosts  to  the
     nodes  in	the  RMS  resource.  If	 an  invalid  resource is
     denoted, the variable is silently ignored.


SDR module options
     The SDR module supports targeting hosts via the System  Data
     Repository	on IBM SPs.



pdsh-2.18	    Last change: solaris2.11			6






User Commands						  pdsh(1)



     -a	  Target all nodes in the SDR. The list	is generated from
	  the "reliable	hostname" in the SDR by	default.

     -i	  Translate hostnames between reliable and initial in the
	  SDR, when applicable.	 If the	a target hostname matches
	  either the initial or	reliable hostname in the SDR, the
	  alternate name will be substitued. Thus a list composed
	  of initial hostnames will instead be	replaced  with	a
	  list	of  reliable  hostnames.   For example,	when used
	  with -a above, all initial hostnames	in  the	 SDR  are
	  targeted.

     -v	  Do not target	nodes that are marked as  not  responding
	  in  the  SDR	on the targeted	interface. (If a hostname
	  does not appear in the SDR, then that	name will  remain
	  in the target	hostlist.)

     -G	  In combination with -a, include all partitions.


nodeattr module	options
     The nodeattr module supports access to the	genders	 database
     via  the  nodeattr(1) command. See	the genders section above
     for a list	of support options with	this module.  The  option
     usage  with  the  nodeattr	 module	 is  the same as genders,
     above, with the exception that the	-i  option  may	 only  be
     used  with	 -a  or	-g. NOTE: This module will only	work with
     very old releases of genders where	the  nodeattr(1)  command
     supports  the  -r	option,	and before the libgenders API was
     available.	Users running newer versions of	genders	will need
     to	use the	genders	module instead.


dshgroup module	options
     The dshgroup module allows	pdsh  to  use  dsh  (or	 Dancer's
     shell)   style   group   files   from   /etc/dsh/group/   or
     ~/.dsh/group/.

     -g	groupname,...
	  Target nodes in dsh group  file  "groupname"	found  in
	  either	     ~/.dsh/group/groupname	       or
	  /etc/dsh/group/groupname.

     -X	groupname,...
	  Exclude nodes	in dsh group file "groupname."


netgroup module	options
     The netgroup module allows	pdsh  to  use  standard	 netgroup
     entries  to  build	 lists of target hosts.	(/etc/netgroup or
     NIS)




pdsh-2.18	    Last change: solaris2.11			7






User Commands						  pdsh(1)



     -g	groupname,...
	  Target nodes in netgroup "groupname."

     -X	groupname,...
	  Exclude nodes	in netgroup "groupname."


ENVIRONMENT VARIABLES
     PDSH_RCMD_TYPE
	  Equivalent to	the -R option, the value of this environ-
	  ment	variable  will	be  used  to set the default rcmd
	  module for pdsh to use (e.g. ssh, rsh).

     PDSH_SSH_ARGS
	  Override the standard	arguments that pdsh passes to the
	  ssh(1) command ("-2 -a -x").

     PDSH_SSH_ARGS_APPEND
	  Append additional options to the ssh(1) command invoked
	  by  pdsh.  For example, PDSH_SSH_ARGS_APPEND="-q" would
	  run ssh in quiet mode, or "-v" would increase	the  ver-
	  bosity of ssh.

     WCOLL
	  If no	other node selection option is	used,  the  WCOLL
	  environment  variable	 may  be  set  to a filename from
	  which	a list of target hosts will  be	 read.	The  file
	  should  contain  a  list of hosts, one per line (though
	  each line may	contain	a hostlist expression.	See HOST-
	  LIST EXPRESSIONS section below).

     DSHPATH
	  If set, the path in DSHPATH will be used  as	the  PATH
	  for the remote processes.

     FANOUT
	  Set the pdsh fanout (See description of -f above).


HOSTLIST EXPRESSIONS
     As	noted in sections above	pdsh accepts lists of  hosts  the
     general  form:  prefix[n-m,l-k,...],  where n < m and l < k,
     etc., as an alternative to	explicit  lists	 of  hosts.  This
     form  should not be confused with regular expression charac-
     ter classes (also denoted by ``[]''). For	example,  foo[19]
     does  not represent an expression matching	foo1 or	foo9, but
     rather represents the degenerate hostlist:	foo19.

     The hostlist syntax is meant only as a convenience	on  clus-
     ters  with	a "prefixNNN" naming convention	and specification
     of	 ranges	 should	 not  be  considered  necessary	 --  this
     foo1,foo9	could  be  specified  as such, or by the hostlist



pdsh-2.18	    Last change: solaris2.11			8






User Commands						  pdsh(1)



     foo[1,9].

     Some examples of usage follow:


     Run command on foo01,foo02,...,foo05
	 pdsh -w foo[01-05] command

     Run command on foo7,foo9,foo10
	 pdsh -w foo[7,9-10] command

     Run command on foo0,foo4,foo5
	 pdsh -w foo[0-5] -x foo[1-3] command


     A suffix on the hostname is also supported:


     Run command on foo0-eth0,foo1-eth0,foo2-eth0,foo3-eth0
	pdsh -w	foo[0-3]-eth0 command


     As	a reminder to the  reader,  some  shells  will	interpret
     brackets  ('['  and ']') for pattern matching.  Depending on
     your shell, it may	be  necessary  to  enclose  ranged  lists
     within  quotes.   For  example,  in  tcsh,	the first example
     above should be executed as:

	 pdsh -w "foo[01-05]" command


ORIGIN
     Originally	 a  rewrite  of	 IBM  dsh(1)   by   Jim	  Garlick
     <garlick@llnl.gov>	 on  LLNL's ASCI Blue-Pacific IBM SP sys-
     tem. It is	now used on Linux clusters at LLNL.


LIMITATIONS
     When using	ssh for	remote execution, expect  the  stderr  of
     ssh  to  be  folded in with that of the remote command. When
     invoked by	pdsh, it is not	possible for ssh  to  prompt  for
     passwords	if  RSA/DSA  keys  are configured properly, etc..
     For ssh implementations  that  suppport  a	 connect  timeout
     option,  pdsh  attempts  to  use  that option to enforce the
     timeout (e.g.  -oConnectTimeout=T	for  OpenSSH),	otherwise
     connect timeouts are not supported	when using ssh.	 Finally,
     there is no reliable way for pdsh to ensure that remote com-
     mands  are	actually terminated when using a command timeout.
     Thus if -u	is used	with ssh commands may be left running  on
     remote  hosts  even  after	 timeout  has  killed  local  ssh
     processes.




pdsh-2.18	    Last change: solaris2.11			9






User Commands						  pdsh(1)



     Output from multiple processes per	node may be  interspersed
     when using	qshell or mqshell rcmd modules.

     The number	of nodes that  pdsh  can  simultaneously  execute
     remote  jobs  on is limited by the	maximum	number of threads
     that can be created concurrently, as well as the  availabil-
     ity of reserved ports in the rsh and qshell rcmd modules. On
     systems that implement Posix threads, the limit is	typically
     defined by	the constant PTHREADS_THREADS_MAX.


FILES
ATTRIBUTES
     See attributes(5) for descriptions	of the	following  attri-
     butes:



     ____________________________________________________________
    |	    ATTRIBUTE TYPE	  |	  ATTRIBUTE VALUE	|
    |_____________________________|_____________________________|
    | Availability		  | SUNWpdsh			|
    |_____________________________|_____________________________|
    | Interface	Stability	  | uncommitted			|
    |_____________________________|_____________________________|


SEE ALSO
     rsh(1),	     ssh(1),	      dshbak(1),	  pdcp(1)
     http://sourceforge.net/projects/pdsh/

NOTES
     Source for	pdsh is	available on http://opensolaris.org






















pdsh-2.18	    Last change: solaris2.11		       10




--Boundary_(ID_b1FlBRXwNB6pB84SpHAFHw)
Content-type: application/octet-stream; name=dshbak.1
Content-transfer-encoding: QUOTED-PRINTABLE
Content-disposition: attachment; filename=dshbak.1

'\" te=0A.\"^M=0A.\" CDDL HEADER START^M=0A.\"^M=0A.\" The contents o=
f this file are subject to the terms of the^M=0A.\" Common Developmen=
t and Distribution License (the "License").^M=0A.\" You may not use t=
his file except in compliance with the License.^M=0A.\"^M=0A.\" You c=
an obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE^M=0A.\=
" or http://www.opensolaris.org/os/licensing.^M=0A.\" See the License=
 for the specific language governing permissions^M=0A.\" and limitati=
ons under the License.^M=0A.\"^M=0A.\" When distributing Covered Code=
, include this CDDL HEADER in each^M=0A.\" file and include the Licen=
se file at usr/src/OPENSOLARIS.LICENSE.^M=0A.\" If applicable, add th=
e following below this CDDL HEADER, with the^M=0A.\" fields enclosed =
by brackets "[]" replaced with your own identifying^M=0A.\" informati=
on: Portions Copyright [yyyy] [name of copyright owner]^M=0A.\"^M=
=0A.\" CDDL HEADER END^M=0A.\"^M=0A.\" Copyright 2009 Sun Microsystem=
s, Inc. All rights reserved.^M=0A.\" Use is subject to license terms.=
^M=0A.\"^M=0A\." $Id: dshbak.1 2 2001-04-25 21:00:43Z garlick $=0A.TH=
 DSHBAK 1 "Release 1.3" "LLNL" "DSHBAK"=0A.SH NAME=0Adshbak \- format=
 output from pdsh command=0A.SH SYNOPSIS=0A.B dshbak=0A.I "[-c]"=0A.b=
r=0A.SH DESCRIPTION=0A.B dshbak=0Aformats=0A.B pdsh=0Aoutput for huma=
ns.  Output from each node is consolidated, the leading=0A.I "node:"=
=0Aprefix is stripped, and a header block with the node name is added=
.=0AIf the=0A.I "-c"=0Aoption is specified, nodes with identical outp=
ut are not displayed twice;=0Ainstead, the header will contain a list=
 of nodes.  The list of nodes is=0Afurther compressed into node range=
s if the node names have a numeric suffix.=0A=0A.SH "ORIGIN"=0AA rewr=
ite of IBM dshbak(1) by Jim Garlick=0A.br=0A<garlick@llnl.gov>=0Aon L=
LNL's ASCI Blue-Pacific IBM SP system.=0A=0A.SH ATTRIBUTES=0A.sp=0A.L=
P=0ASee \fBattributes\fR(5) for descriptions of the following attribu=
tes:=0A.sp=0A=0A.sp=0A.TS=0Atab(=07) box;=0Acw(2.75i) |cw(2.75i) =
=0Alw(2.75i) |lw(2.75i) =0A.=0AATTRIBUTE TYPE=07ATTRIBUTE VALUE=0A_=
=0AAvailability=07SUNWpdsh=0A_=0AInterface Stability=07uncommitted=
=0A.TE=0A=0A.SH SEE ALSO=0Apdsh(1)=0A=

--Boundary_(ID_b1FlBRXwNB6pB84SpHAFHw)
Content-type: text/plain; name=FastTrack_pdsh.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=FastTrack_pdsh.txt

Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction
    1.1. Project/Component Working Name:
	 pdsh Ver 2.18
    1.2. Name of Document Author/Supplier:
	 Author:  Vivek R. Titarmare
    1.3  Date of This Document:
	 3rd April, 2009

2. Project Summary
   2.1 Project Description

	Parallel command execution for clusters

4. Technical Description:

	Pdsh is a high-performance, parallel remote shell utility. It has built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and can call SSH externally (though with reduced performance). Pdsh uses a "sliding window" parallel algorithm to conserve socket resources on the initiating node and to allow progress to continue while timeouts occur on some connections.
	
	Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which runs commands on a single remote host, pdsh can run multiple remote commands in parallel. pdsh uses a "sliding window" (or fanout) of threads to conserve resources on the the initiating host while allowing some connections to time out. 	

5. Interfaces 

	The binary file "pdsh" contains following interface.

   Exported interface                   Classification 		Interface type
   =============================        ============== 		==============
   	usr/bin/dshbak			Uncommitted		binary
   	usr/bin/pdcp			Uncommitted		binary
   	usr/bin/pdsh			Uncommitted		binary
   	usr/bin/rpdcp			Uncommitted		binary
   	usr/lib/pdsh/xrcmd.so		Uncommitted		shared library
   	usr/lib/pdsh/xrcmd.la		Uncommitted		library tool
   	usr/lib/pdsh/xrcmd.a		Uncommitted		static library
   	usr/lib/pdsh/execcmd.so		Uncommitted		shared library
   	usr/lib/pdsh/execcmd.la		Uncommitted		library tool
   	usr/lib/pdsh/execcmd.a		Uncommitted		static library
   	
	PDSH_RCMD_TYPE			Uncommitted		override standard argument
	PDSH_SSH_ARGS			Uncommitted		override standard argument
	PDSH_SSH_ARGS_APPEND		Uncommitted		override standard argument
	WCOLL				Uncommitted		override standard argument
	DSHPATH				Uncommitted		override standard argument
	FANOUT				Uncommitted		override standard argument
	QSHELL_REMOTE_LD_LIBRARY_PATH	Uncommitted		override standard argument
	QSHELL_REMOTE_LD_PREOPEN	Uncommitted		override standard argument
	

   Imported interface        Classification   Comments
   =======================   ==============   =================================== 
	None

   The binary file would go in "usr/bin" and the libraries would go in "usr/lib"


6. Resources and Schedule
    6.4. Steering Committee requested information
   	6.4.1. Consolidation C-team Name:
		SFW
    6.5. ARC review type: FastTrack
    6.6. ARC Exposure: open

--Boundary_(ID_b1FlBRXwNB6pB84SpHAFHw)
Content-type: text/plain; name=FOSS_pdsh.txt
Content-transfer-encoding: 7BIT
Content-disposition: attachment; filename=FOSS_pdsh.txt

FCL--FOSS Check List

1.0 Project Information
1.1 Name of project/component
	pdsh  Ver 2.18

1.2 Author of document
	Vivek R. Titarmare

2.0 Project Summary
  2.1 Project Description

	Pdsh is a high-performance, parallel remote shell utility. It has built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and can call SSH externally (though with reduced performance). Pdsh uses a "sliding window" parallel algorithm to conserve socket resources on the initiating node and to allow progress to continue while timeouts occur on some connections.
	
	Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which runs commands on a single remote host, pdsh can run multiple remote commands in parallel. pdsh uses a "sliding window" (or fanout) of threads to conserve resources on the the initiating host while allowing some connections to time out. 	

	Pdsh is a an efficient, multithreaded remote shell client which executes commands on multiple remote hosts in parallel. Pdsh implements dynamically loadable modules for extended functionality such as new remote shell services and remote host selection

  2.2 Release binding
      What is is the release binding?
      (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/)
      [ ] Major
      [X] Minor
      [ ] Patch or Micro
      [ ] Unknown -- ARC review required

  2.3 Type of project
      Is this case a Linux Familiarity project?
      [X] Yes
      [ ] No

  2.4 Originating Community
    2.4.1 Community Name
	    PDSH (http://sourceforge.net/projects/pdsh/)
    
    2.4.2 Community Involvement
      Indicate Sun's involvement in the community
      [ ] Maintainer
      [ ] Contributor
      [X] Monitoring
      
      Will the project team work with the upstream community to resolve
      architectural issues of interest to Sun?
      [X] Yes 
      [ ] No - briefly explain
      
	
      Will we or are we forking from the community?
      [ ] Yes - ARC review required prior to forking
      [X] No
      
3.0 Technical Description
  3.1 Installation & Sharable
    3.1.1S Solaris Installation - section only required for Solaris Software
      (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details)
      Does this project follow the Install Locations best practice?
      [X] Yes 
      [ ] No - ARC review required
      
      Does this project install into /usr under [sbin|bin|lib|include|man|share]?
      [X] Yes
      [ ] No or N/A
      
      Does this project install into /opt?
      [ ] Yes - explain below
      [X] No or N/A
      
      Does this project install into a different directory structure?
      [ ] Yes - ARC review required
      [X] No or N/A
      
      Do any of the components of this project conflict with anything under /usr?
      (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details)
      [ ] Yes - explain below
      [X] No
      
      If conflicts exist then will this project install under /usr/gnu?
      [ ] Yes
      [ ] No - ARC review required
      [X] N/A
      
      Is this project installing into /usr/sfw?
      [ ] Yes - ARC review required
      [X] No
      
    3.1.1W Windows Installation - section only required for Windows Software
      (see http://sac.sfbay/WSARC/2002/494 for details)
      Does this project install software into a 
      <system drive>:\Program Files\Sun\<product> or <system drive>:\Sun\<product>
      directory?
      [ ] Yes
      [ ] No - ARC review required
      
      Does the project use the Windows registry?
      [ ] Yes
      [ ] No - ARC review required
      
      Does the project use 
      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\<product>\<version>
      for the registry key?
      [ ] Yes
      [ ] No - ARC review required
      
      Is the project's stored location
      HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\<product id>\<version id>\Path?
      [ ] Yes
      [ ] No - ARC review required
      
    3.1.2 Share and Sharable
      Does the module include any components that are used or shared by 
      other projects?
      [X] Yes
      [ ] No
    
      If yes are these components packaged to be shared with the other FOSS?
      [X] Yes
      [ ] No - ARC review required
      [ ] N/A
    
      Are these components already in the Solaris WOS?
      [X] Yes
      [ ] No - continue with next section (section 3.2)
    
      If yes are these newer versions being delivered?
      [X] Yes
      [ ] No - ARC review required
      
      If yes are the newer versions replacing the existing versions?
      [X] Yes
      [ ] No - ARC review required

  3.2 Exported Libraries
      Are libraries being delivered by this project?
      [ ] Yes
      [X] No - continue with next section (section 3.3)
      
      Are 64-bit versions of the libraries being delivered?
      [ ] Yes
      [ ] No - ARC review required
    
      Are static versions of the libraries being delivered?
      [ ] Yes - ARC review required
      [ ] No 
      
  3.3 Services and the /etc Directory
      (see http://opensolaris.org/os/community/arc/policies/SMF-policy/)
      Does the project integrate anything into /etc/init.d or /etc/rc?.d?
      [ ] Yes - ARC review required
      [X] No
      
      Does the project integrate any new entries into /etc/inittab or
      /etc/inetd.conf?
      [ ] Yes - ARC review required
      [X] No
      
      Does the project integrate any private non-public files into /etc/default
      or /etc/ configuration files?
      [ ] Yes - ARC review required
      [X] No
      
      Does the service manifests method context grant rights above that
      of the noaccess user and basic privilege set?
      [ ] Yes - ARC review required
      [X] No
        
  3.4 Security
    3.4.1 Secure By Default 
      (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details)
      (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details)
      (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for
       addtional details)
      Are there any network services provided by this project?
      [ ] Yes
      [X] No - continue with the next section (section 3.4.2)
      
      Are network services enabled by default?
      [ ] Yes - ARC review required
      [ ] No
      [X] N/A
      
      Are network services automatically enabled by the project during installation?
      [ ] Yes - ARC review required
      [ ] No
      [X] N/A
      
      Are inbound network communications denied by default?
      [ ] Yes
      [ ] No - ARC review required
      [X] N/A
      
      Is inbound data checked to prevent content-based attacks?
      [ ] Yes
      [ ] No - ARC review required
      [X] N/A
      
      Is the outbound receiver authenticated?
      [ ] Yes
      [ ] No - ARC review required
      [X] N/A
      
      Is the receiver authenticated prior to receiving any sensitive outbound communication?
      [ ] Yes
      [ ] No - ARC review required
      [X] N/A
      
    3.4.2 Authorization
      (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and
	   http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and
	   http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/
           for details)
      Are there any setuid/setgid privileged binaries in the project?
      [ ] Yes - ARC review required
      [X] No - continue with next section (section 3.4.3)
      
      If yes then are the setuid/setgid privileges handled by the use of roles?
      [ ] Yes
      [ ] No - ARC review required

    3.4.3 Auditing
      (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details)
      (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details)
      Does this component contain administrative or security enforcing software?
      [ ] Yes - ARC review required
      [X] No - continue to next section (section 3.4.4)
      
      (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details)
      Do the components create audit logs detailing what took place including what event
      took place, who was involved, when the event took place?
      [ ] Yes - ARC contract and Audit project team review required
      [ ] No - ARC review required
        
        
    3.4.4 Authentication
      (see http://opensolaris.org/os/community/arc/policies/PAM/)
      Do the components contain any authentication code?
      [ ] Yes
      [X] No - continue to next section (section 3.4.5)
      
      If yes do the components use PAM (plugable authentication modules) for authentication?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes is a single PAM session maintained during authentication?
      [ ] Yes
      [ ] No - ARC review required
      
      If yes are the components sufficiently privileged to allow the requested 
      operations (authentication, password change, process credential manipulation, 
      audit state initialization)?
      [ ] Yes - briefly describe below
      [ ] No - ARC review required
      
    3.4.5 Passwords
      (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and
           http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details)
      Do any of the components for the project deal with passwords?
      [ ] Yes
      [X] No - continue to next section (section 3.4.6)
      
      If yes are these passwords entered via the CLI or environment?
      [ ] Yes - ARC review required
      [ ] No
      
      Are passwords stored within the file system for the component?
      [ ] Yes
      [ ] No - continue to next section (section 3.4.6)
      
      If yes are the permissions on the file such to protect exposing the password(s)?
      [ ] Yes
      [ ] No - ARC review required
      
    3.4.6 General Security Questions
      (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details)
      Are there any network protocols used by this project?
      [X] Yes
      [ ] No - continue with the next section (section 3.5)
      
      Do the components use standard network protocols?
      [X] Yes
      [ ] No - ARC review required
      
      Do network services for the project make decisions based upon user, host or 
      service identities?
      [X] Yes - explain below
      [ ] No
      [ ] N/A
      
      	pdsh makes decision on network services based upon service identities. pdsh is a variant of the rsh(1) command. The core functionality of pdsh may be supplemented by dynamically loadable modules. The modules may provide a new connection protocol (replacing the standard rcmd(3) protocol used by rsh(1)), filtering options (e.g. removing hosts that are "down" from the target list), and/or host selection options (e.g., -a selects all hosts from a configuration file.).Pdsh modules come in two flavors at this time: rcmd and miscellaneous. 
      		
      	The rcmd modules provide remote command functionality for pdsh. A list of rcmd modules currently distributed with pdsh follows. 
      		rsh Uses an internal, thread-safe implementation of BSD rcmd(3) to run commands using the standard rsh(1) protocol. 
      		ssh Uses a variant of popen(3) to run multiple copies of the ssh(1) command. 
      		mrsh This module uses the mrsh(1) protocol to execute jobs on remote hosts. The mrsh protocol uses a credential based authentication, forgoing the need to allocate reserved ports. In other aspects, it acts just like rsh. Remote nodes must be running mrshd(8) in order for the mrsh module to work. 
               	qsh  Allows pdsh to execute MPI jobs over QsNet. Qshell propagates the current working directory, pdsh environment, and Elan capabilities to the remote process. The following environment variable are also appended to the environment: RMS_RANK, RMS_NODEID, RMS_PROCID, RMS_NNODES, and RMS_NPROCS. 
        Since pdsh needs to run setuid root for qshell support, qshell does not directly support propagation of LD_LIBRARY_PATH and LD_PREOPEN. Instead the QSHELL_REMOTE_LD_LIBRARY_PATH and QSHELL_REMOTE_LD_PREOPEN environment variables will may be used and will be remapped to LD_LIBRARY_PATH and LD_PREOPEN by the qshell daemon if set. 
                mqsh Similar to qshell, but uses the mrsh protocol instead of the rsh protocol. 
                krb4 The krb4 module allows users to execute remote commands after authenticating with kerberos. Of course, the remote rshd daemons must be kerberized. 
                xcpu The xcpu module uses the xcpu service to execute remote commands
      
      Do the components make use of secret information during authentication and/or
      authorization?
      [ ] Yes - explain below
      [X] No
      [ ] N/A
  
  3.5 Networking
      Do the components access the network?
      [X] Yes
      [ ] No - continue with the next section (section 3.6)
      
      If yes do the components support IPv6?
      [X] Yes 
      [ ] No - ARC review required
          
  3.6 Core Solaris Components
      Do the components of this project compete with or duplicate core 
      Solaris components?
      [ ] Yes - ARC review required
      [X] No 
             
4.0 Interfaces
  (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details)
  4.1 Exported Interfaces
  
    The binary file "pdsh" contains following interface.

    Interface Name			Classification  	    	Comments
    ---------------------------     ------------------- 	---------------------------
   	usr/bin/dshbak			Uncommitted		binary
   	usr/bin/pdcp			Uncommitted		binary
   	usr/bin/pdsh			Uncommitted		binary
   	usr/bin/rpdcp			Uncommitted		binary
   	usr/lib/pdsh/xrcmd.so		Uncommitted		shared library
   	usr/lib/pdsh/xrcmd.la		Uncommitted		library tool
   	usr/lib/pdsh/xrcmd.a		Uncommitted		static library
   	usr/lib/pdsh/execcmd.so		Uncommitted		shared library
   	usr/lib/pdsh/execcmd.la		Uncommitted		library tool
   	usr/lib/pdsh/execcmd.a		Uncommitted		static library
   	
	PDSH_RCMD_TYPE			Uncommitted		override standard argument
	PDSH_SSH_ARGS			Uncommitted		override standard argument
	PDSH_SSH_ARGS_APPEND		Uncommitted		override standard argument
	WCOLL				Uncommitted		override standard argument
	DSHPATH				Uncommitted		override standard argument
	FANOUT				Uncommitted		override standard argument
	QSHELL_REMOTE_LD_LIBRARY_PATH	Uncommitted		override standard argument
	QSHELL_REMOTE_LD_PREOPEN	Uncommitted		override standard argument
	

  4.2 Imported Interfaces
    Interface Name		Classification       Comments
    --------------------------- -------------------- --------------------------
	None    

The binary file would go in "/usr/bin" and the libraries would go in "/usr/lib"

Appendix B - Suggested case materials
  1. man pages

     Attached are the man pages (pdsh.1, pdcp.1, dshbak.1)

  2. SMF manifests
  3. links to contracts
  

--Boundary_(ID_b1FlBRXwNB6pB84SpHAFHw)--

From margot.miller@sun.com Wed Apr 22 09:43:57 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3MGhrvr017919
	for <LSARC-ext@sac.sfbay.sun.com>; Wed, 22 Apr 2009 09:43:53 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3MGhcWo021446;
	Wed, 22 Apr 2009 17:43:45 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KII00C0RH4XAY00@nwk-avmta-2.sfbay.sun.com>; Wed,
 22 Apr 2009 09:43:45 -0700 (PDT)
Received: from jurassic-x4600.sfbay.sun.com ([129.146.17.59])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KII006SMH4WY380@nwk-avmta-2.sfbay.sun.com>; Wed,
 22 Apr 2009 09:43:44 -0700 (PDT)
Received: from [10.7.250.251]
 (punchin-client-10-7-250-251.SFBay.Sun.COM [10.7.250.251])
	by jurassic-x4600.sfbay.sun.com (8.14.3+Sun/8.14.3)
 with ESMTP id n3MGhaWh379885; Wed, 22 Apr 2009 09:43:37 -0700 (PDT)
Date: Wed, 22 Apr 2009 09:38:38 -0700
From: Margot Miller <margot.miller@sun.com>
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <024601c9c34b$7b459110$71d0b330$%Titarmare@Sun.com>
To: Vivek Titarmare <Vivek.Titarmare@sun.com>
Cc: "'Danek Duvall'" <Danek.Duvall@sun.com>,
        "'Mark Carlson'" <markcarl@sac.sfbay.sun.com>, James.D.Carlson@sun.com,
        Nicolas.Williams@sun.com, LSARC-ext@sun.com
Message-id: <49EF480E.4070106@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
 <20090413205436.GX7978@mumak.SFBay.Sun.COM>
 <003001c9bd02$8997a1d0$9cc6e570$%Titarmare@Sun.com>
 <20090414150713.GA7978@mumak.SFBay.Sun.COM>
 <013801c9c2a4$e270fb10$a752f130$%Titarmare@Sun.com>
 <20090421180905.GF4425@mumak.SFBay.Sun.COM>
 <024601c9c34b$7b459110$71d0b330$%Titarmare@Sun.com>
User-Agent: Thunderbird 2.0b1 (X11/20070115)
Status: RO
Content-Length: 55667

Vivek,

Please add the package SUNWpdsh to the interface table.

In the pdsh man page, it has:

     qsh     Allows pdsh to execute MPI	jobs over  QsNet.  Qshell
	     propagates	  the  current	working	 directory,  pdsh
	     environment, and Elan  capabilities  to  the  remote
	     process. The following environment	variable are also
	     appended to the environment:  RMS_RANK,  RMS_NODEID,
	     RMS_PROCID,  RMS_NNODES,  and RMS_NPROCS. Since pdsh
	     needs to run setuid root for qshell support,  qshell
	     does    not    directly   support	 propagation   of
	     LD_LIBRARY_PATH   and   LD_PREOPEN.   Instead    the
	     QSHELL_REMOTE_LD_LIBRARY_PATH		      and
	     QSHELL_REMOTE_LD_PREOPEN environment variables  will
	     may  be used and will be remapped to LD_LIBRARY_PATH
	     and LD_PREOPEN by the qshell daemon if set.

Does this project support Qshell?  

Also, there is a section in one of the man pages about slurm
module options.  Per Danek in the below email, this is not
relevant for Solaris.  The documentation needs to be updated
to reflect that this isn't supported on Solaris.

Please check through all the man pages to ensure that everything
in the man pages is correct wrt Solaris and what is in the man pages
is reflected in the interface table.

Also, please have your sponsor review all the materials
before you resend the updated documents.

Thanks
Margot




Vivek Titarmare wrote:
> Hi Danek and the team,
>
> I have updated the Fasttrack and FOSS check list for pdsh. Major changes in
> the interface tables would be seen. Actually a rework was done on this
> package and found that the interface table needed a change. 
>
> Pl. ignore the previous Interface related conflicts.
>
> Let me know if this looks good to go.
>
> Pl. find attached all the files required for this ARC review.
>
> Thanks,
> ~Vivek R. Titarmare
>
>
>
> -----Original Message-----
> From: Danek Duvall [mailto:Danek.Duvall@Sun.COM] 
> Sent: Tuesday, April 21, 2009 11:39 PM
> To: Vivek Titarmare
> Cc: 'Mark Carlson'; James.D.Carlson@Sun.COM; Nicolas.Williams@Sun.COM;
> Manisha.Jha@Sun.COM
> Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
>
> [ Please use standard email quoting techniques -- a "> " prefix to every
> line that you're responding to, and not to your own; what you're doing
> makes your email responses incredibly difficult to read.  Perhaps not using
> Outlook would help.  This is Sun, after all; you should be running Solaris.
> ]
>
> On Tue, Apr 21, 2009 at 10:46:14PM +0530, Vivek Titarmare wrote:
>
>   
>>> No, I want you to not deliver those interfaces.  You can't ship
>>>       
> components
>   
>>> that don't work.  This is a commercial OS, not a grad student project,
>>>       
> and
>   
>>> it costs Sun tons of money to field calls from customers complaining
>>>       
> about
>   
>>> things that don't work.  It's best not to ship them at all if we know
>>> they're busted.  Given how much of the man page is filled with text
>>> describing options and arguments that won't be useful on Solaris, you'll
>>> need to remove this extraneous documentation before delivery, too.
>>>       
>> [VIVEK] I am sorry, I think I confused you. All the components work, for
>> those components to work we need to override the environment variables
>>     
> which
>   
>> I am adding those in the Interface table. I this case, do we still need to
>> remove the contents from the man pages. Pl. let me know.
>>     
>
> The components that are unavailable (libgenders, nodeattr, etc) will cause
> portions of pdsh (pdsh-mod-genders, pdsh-mod-nodeattr, etc) not to work,
> environment variables or not.  There is no way that "pdsh-mod-slurm" is
> going to work unless slurm is installed, and since there is no slurm
> available for Solaris, then "pdsh-mod-slurm" is not going to work on
> Solaris.  So don't ship it, and don't document it.
>
> Danek
> ------------------------------------------------------------------------
>
>
>
>
> DSHBAK							DSHBAK(1)
>
>
>
> NAME
>      dshbak - format output from pdsh command
>
> SYNOPSIS
>      dshbak [-c]
>
> DESCRIPTION
>      dshbak formats pdsh output	for  humans.   Output  from  each
>      node  is consolidated, the	leading	node: prefix is	stripped,
>      and a header block	with the node name is added.  If  the  -c
>      option  is	 specified,  nodes  with identical output are not
>      displayed twice; instead, the header will contain a list  of
>      nodes.   The  list	 of nodes is further compressed	into node
>      ranges if the node	names have a numeric suffix.
>
>
> ORIGIN
>      A rewrite of IBM dshbak(1)	by Jim Garlick
>      <garlick@llnl.gov>	on LLNL's ASCI Blue-Pacific IBM	 SP  sys-
>      tem.
>
>
> ATTRIBUTES
>      See attributes(5) for descriptions	of the	following  attri-
>      butes:
>
>
>
>      ____________________________________________________________
>     |	    ATTRIBUTE TYPE	  |	  ATTRIBUTE VALUE	|
>     |_____________________________|_____________________________|
>     | Availability		  | SUNWpdsh			|
>     |_____________________________|_____________________________|
>     | Interface	Stability	  | uncommitted			|
>     |_____________________________|_____________________________|
>
>
> SEE ALSO
>      pdsh(1)
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> LLNL		    Last change: Release 1.3			1
>
>
>   
> ------------------------------------------------------------------------
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
> NAME
>      pdcp - copy files to groups of hosts in parallel
>      rpdcp - (reverse pdcp) copy files from a group of	hosts  in
>      parallel
>
>
> SYNOPSIS
>      pdcp [options]... src [src2...] dest
>      rpdcp [options]...	src [src2...] dir
>
>
> DESCRIPTION
>      pdcp is a variant of the  rcp(1)  command.	  Unlike  rcp(1),
>      which  copies  files  to a	single remote host, pdcp can copy
>      files to multiple remote hosts in parallel.   However,  pdcp
>      does not recognize	files in the format ``rname@rhost:path,''
>      therefore all  source  files  must	 be  on	 the  local  host
>      machine.	Destination nodes must be listed on the	pdcp com-
>      mand line using a suitable	target nodelist	option	(See  the
>      OPTIONS  section  below).	Each destination node listed must
>      have pdcp installed for the copy to succeed.
>
>      When pdcp receives	SIGINT (ctrl-C), it lists the  status  of
>      current  threads.	 A  second  SIGINT within one second ter-
>      minates the program. Pending  threads  may	 be  canceled  by
>      issuing ctrl-Z within one second of ctrl-C.  Pending threads
>      are those that have not yet been initiated, or are	still  in
>      the process of connecting to the remote host.
>
>      Like pdsh(1), the functionality of	pdcp may be  supplemented
>      by	 dynamically  loadable	modules. In pdcp, the modules may
>      provide a	new  connect  protocol	(replacing  the	 standard
>      rsh(1)  protocol),	 filtering  options (e.g. excluding hosts
>      that are down),  and/or  host  selection  options	(e.g.  -a
>      selects  all  nodes  from a local config file).  By default,
>      pdcp requires at least one	"rcmd" module to  be  loaded  (to
>      provide the channel for remote copy).
>
>
> REVERSE	PDCP
>      rpdcp performs a reverse parallel copy.  Rather than copying
>      files to remote hosts, files are retrieved	from remote hosts
>      and stored	locally.  All directories or files retrieved will
>      be	 stored	 with  their  remote  hostname	appended  to  the
>      filename.	The destination	file must  be  a  directory  when
>      this option is used.
>
>      In	other respects,	rpdcp is exactly like pdcp,  and  further
>      statements	 regarding  pdcp  in  this  manual  also apply to
>      rpdcp.
>
>
>
>
>
> pdsh-2.18	    Last change: solaris2.11			1
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
> RCMD MODULES
>      The method	by which pdcp connects to  remote  hosts  may  be
>      selected at runtime using the -R option (See OPTIONS below).
>      This functionality	is ultimately implemented via dynamically
>      loadable  modules,	 and so	the list of available options may
>      be	different from installation to installation.  A	 list  of
>      currently	available  rcmd	modules	is printed when	using any
>      of	the -h,	-V, or -L options. The default rcmd  module  will
>      also be displayed with the	-h and -V options.
>
>      A list of rcmd modules currently distributed with pdcp  fol-
>      lows.
>
>      rsh     Uses an internal, thread-safe implementation of  BSD
> 	     rcmd(3)  to  run  commands	using the standard rsh(1)
> 	     protocol.
>
>      ssh     Uses a variant of popen(3)	to run multiple	copies of
> 	     the ssh(1)	command.
>
>      mrsh    This module uses the  mrsh(1)  protocol  to  execute
> 	     jobs  on  remote  hosts.	The  mrsh protocol uses	a
> 	     credential	based authentication, forgoing	the  need
> 	     to	 allocate  reserved  ports.  In	other aspects, it
> 	     acts just like rsh.
>
>      krb4    The krb4 module allows users to execute remote  com-
> 	     mands after authenticating	with kerberos. Of course,
> 	     the remote	rshd daemons must be kerberized.
>
>      xcpu    The xcpu module uses the  xcpu  service  to  execute
> 	     remote commands.
>
>
> OPTIONS
>      The list of available pdcp	options	is determined at  runtime
>      by	 supplementing the list	of standard pdcp options with any
>      options provided by loaded	rcmd and misc modules.	 In  some
>      cases,  options  provided	by modules may conflict	with each
>      other. In these cases, the	modules	are incompatible and  the
>      first module loaded wins.
>
>
> Standard target	nodelist options
>      -w	host,host,...
> 	  Target the specified list of hosts. Do not use with any
> 	  other	 node  selection options (e.g. -a, -g if they are
> 	  available).  No  spaces  are	allowed	 in  the   comma-
> 	  separated  list.   A	list  consisting  of a single `-'
> 	  character causes the	target	hosts  to  be  read  from
> 	  stdin, one per line. The host	list may contain hostlist
> 	  expressions  of  the	form  ``host[1-5,7]''.	For  more
>
>
>
> pdsh-2.18	    Last change: solaris2.11			2
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
> 	  information about the	hostlist format, see the HOSTLIST
> 	  EXPRESSIONS section below.
>
>      -x	host,host,...
> 	  Exclude the specified	hosts. May be specified	 in  con-
> 	  junction with	other target node list options such as -a
> 	  and -g (when available). Hostlists may also  be  speci-
> 	  fied	to the -x option (see HOSTLIST EXPRESSIONS secion
> 	  below).
>
>
> Standard pdcp options
>      -h	  Output usage menu and	quit. A	list  of  available  rcmd
> 	  modules  will	 be  printed at	the end	of the usage mes-
> 	  sage.
>
>      -q	  List option values and the  target  nodelist	and  exit
> 	  without action.
>
>      -b	  Disable ctrl-C status	feature	so that	a  single  ctrl-C
> 	  kills	parallel copy. (Batch Mode)
>
>      -r	  Copy directories recursively.
>
>      -p	  Preserve modification	time and modes.
>
>      -e	PATH
> 	  Explicitly specify path to remote pdcp  binary  instead
> 	  of using the locally executed	path.
>
>      -l	user
> 	  This option may be used to copy files	as another  user,
> 	  subject  to authorization. For BSD rcmd, this	means the
> 	  invoking user	and system must	be listed in  the  user's
> 	  .rhosts file (even for root).
>
>      -t	seconds
> 	  Set the connect timeout. Default is 10 seconds.
>
>      -f	number
> 	  Set the maximum number of simultaneous remote	copies to
> 	  number.  The default is 32.
>
>      -R	name
> 	  Set rcmd module to name. This	option may  also  be  set
> 	  via  the PDSH_RCMD_TYPE environment variable.	A list of
> 	  available rcmd modules may be	obtained via  either  the
> 	  -h or	-L options.
>
>      -R	name
> 	  Set rcmd module to name. This	option may  also  be  set
> 	  via  the PDSH_RCMD_TYPE environment variable.	A list of
>
>
>
> pdsh-2.18	    Last change: solaris2.11			3
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
> 	  available rcmd modules may be	obtained via  either  the
> 	  -h or	-L options.
>
>      -L	  List info on all loaded pdcp modules and quit.
>
>      -d	  Include more complete	 thread	 status	 when  SIGINT  is
> 	  received,  and display connect and command time statis-
> 	  tics on stderr when done.
>
>      -V	  Output pdcp version information,  along  with	 list  of
> 	  currently loaded modules, and	exit.
>
>
>
> HOSTLIST EXPRESSIONS
>      As	noted in sections above, pdcp accepts ranges of	hostnames
>      in	 the general form: prefix[n-m,l-k,...],	where n	< m and	l
>      < k, etc.,	as an alternative to  explicit	lists  of  hosts.
>      This  form	 should	 not  be confused with regular expression
>      character classes (also denoted  by  ``[]'').  For	 example,
>      foo[19]   does  not  represent  foo1  or  foo9,  but  rather
>      represents	a degenerate range: foo19.
>
>      This range	syntax is meant	only as	a convenience on clusters
>      with  a  prefixNN	naming	convention  and	 specification of
>      ranges should  not	 be  considered	 necessary  --	the  list
>      foo1,foo9	could  be  specified  as  such,	 or  by	the range
>      foo[1,9].
>
>      Some examples of range usage follow:
>
>
>      Copy /etc/hosts to	foo01,foo02,...,foo05
> 	 pdcp -w foo[01-05] /etc/hosts /etc
>
>      Copy /etc/hosts to	foo7,foo9,foo10
> 	 pdcp -w foo[7,9-10] /etc/hosts	/etc
>
>      Copy /etc/hosts to	foo0,foo4,foo5
>       pdcp -w foo[0-5] -x foo[1-3] /etc/hosts /etc
>
>
>      As	a reminder to the  reader,  some  shells  will	interpret
>      brackets  ('['  and ']') for pattern matching.  Depending on
>      your shell, it may	be  necessary  to  enclose  ranged  lists
>      within  quotes.   For  example,  in  tcsh,	the first example
>      above should be executed as:
>
> 	 pdcp -w "foo[01-05]" /etc/hosts /etc
>
>
>
>
>
>
> pdsh-2.18	    Last change: solaris2.11			4
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
> ORIGIN
>      Pdsh/pdcp was originally a	rewrite	of IBM dsh(1) by Jim Gar-
>      lick  <garlick@llnl.gov>  on LLNL's ASCI Blue-Pacific IBM SP
>      system.  It is now	also used on Linux clusters at LLNL.
>
>
> LIMITATIONS
>      When using	ssh for	remote execution, stderr  of  ssh  to  be
>      folded  in	with that of the remote	command.  When invoked by
>      pdcp, it is not possible for ssh to prompt	for  confirmation
>      if	 a host	key changes, prompt for	passwords if RSA keys are
>      not configured properly, etc..  Finally, the connect timeout
>      is	 only  adjustable with ssh when	the underlying ssh imple-
>      mentation supports	it, and	pdsh has been built  to	 use  the
>      correct option.
>
>
> ATTRIBUTES
>      See attributes(5) for descriptions	of the	following  attri-
>      butes:
>
>
>
>      ____________________________________________________________
>     |	    ATTRIBUTE TYPE	  |	  ATTRIBUTE VALUE	|
>     |_____________________________|_____________________________|
>     | Availability		  | SUNWpdsh			|
>     |_____________________________|_____________________________|
>     | Interface	Stability	  | uncommitted			|
>     |_____________________________|_____________________________|
>
>
> SEE ALSO
>      pdsh(1)
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> pdsh-2.18	    Last change: solaris2.11			5
>
>
>   
> ------------------------------------------------------------------------
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
> NAME
>      pdsh - issue commands to groups of	hosts in parallel
>
>
> SYNOPSIS
>      pdsh [options]... command
>
>
> DESCRIPTION
>      pdsh is a variant of  the	rsh(1)	command.  Unlike  rsh(1),
>      which  runs  commands  on a single	remote host, pdsh can run
>      multiple remote commands in parallel. pdsh	uses  a	 "sliding
>      window"  (or fanout) of threads to	conserve resources on the
>      initiating	host while allowing some connections to	time out.
>
>      When pdsh receives	SIGINT (ctrl-C), it lists the  status  of
>      current  threads.	A  second  SIGINT  within one second ter-
>      minates the program. Pending  threads  may	 be  canceled  by
>      issuing ctrl-Z within one second of ctrl-C.  Pending threads
>      are those that have not yet been initiated, or are	still  in
>      the process of connecting to the remote host.
>
>
>      If	a remote command is not	specified on  the  command  line,
>      pdsh  runs	interactively, prompting for commands and execut-
>      ing them when terminated with a carriage return. In interac-
>      tive  mode,  target nodes that time out on	the first command
>      are not contacted for subsequent commands,	and commands pre-
>      fixed  with  an  exclamation  point  will be executed on the
>      local system.
>
>      The core functionality of pdsh may	be supplemented	by dynam-
>      ically  loadable modules. The modules may provide a new con-
>      nection protocol (replacing the  standard	rcmd(3)	 protocol
>      used by rsh(1)), filtering	options	(e.g. removing hosts that
>      are "down"	from the  target  list),  and/or  host	selection
>      options  (e.g.,  -a  selects  all hosts from a configuration
>      file.). By	default, pdsh  must  have  at  least  one  "rcmd"
>      module  loaded. See the RCMD MODULES section for more infor-
>      mation.
>
>
> RCMD MODULES
>      The method	by which pdsh runs commands on remote  hosts  may
>      be	 selected  at  runtime	using  the -R option (See OPTIONS
>      below).  This functionality is  ultimately	 implemented  via
>      dynamically  loadable  modules, and so the	list of	available
>      options may be different from installation	to  installation.
>      A	list  of currently available rcmd modules is printed when
>      using any of the -h, -V, or -L  options.  The  default  rcmd
>      module will also be displayed with	the -h and -V options.
>
>
>
>
> pdsh-2.18	    Last change: solaris2.11			1
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
>      A list of rcmd modules currently distributed with pdsh  fol-
>      lows.
>
>      rsh     Uses an internal, thread-safe implementation of  BSD
> 	     rcmd(3)  to  run  commands	using the standard rsh(1)
> 	     protocol.
>
>      exec    Executes an arbitrary command for each target  host.
> 	     The  first	of the pdsh remote arguments is	the local
> 	     command to	execute, followed by  any  further  argu-
> 	     ments.  Some simple parameters are	substitued on the
> 	     command line, including %h	for the	target	hostname,
> 	     %u	 for  the  remote username, and	%n for the remote
> 	     rank [0-n]	(To get	a literal % use	%%).   For  exam-
> 	     ple,  the	following  would  duplicate using the ssh
> 	     module to run hostname(1) across  the  hosts  foo[0-
> 	     10]:
>
> 		pdsh -R	exec -w	foo[0-10] ssh -x -l %u %h hostname
>
> 	     and this command line would run grep(1) in	 parallel
> 	     across the	files console.foo[0-10]:
>
> 		pdsh -R	exec -w	foo[0-10] grep BUG console.%h
>
>
>      ssh     Uses a variant of popen(3)	to run multiple	copies of
> 	     the ssh(1)	command.
>
>      mrsh    This module uses the  mrsh(1)  protocol  to  execute
> 	     jobs  on  remote  hosts.	The  mrsh protocol uses	a
> 	     credential	based authentication, forgoing	the  need
> 	     to	 allocate  reserved  ports.  In	other aspects, it
> 	     acts just like rsh. Remote	 nodes	must  be  running
> 	     mrshd(8) in order for the mrsh module to work.
>
>      qsh     Allows pdsh to execute MPI	jobs over  QsNet.  Qshell
> 	     propagates	  the  current	working	 directory,  pdsh
> 	     environment, and Elan  capabilities  to  the  remote
> 	     process. The following environment	variable are also
> 	     appended to the environment:  RMS_RANK,  RMS_NODEID,
> 	     RMS_PROCID,  RMS_NNODES,  and RMS_NPROCS. Since pdsh
> 	     needs to run setuid root for qshell support,  qshell
> 	     does    not    directly   support	 propagation   of
> 	     LD_LIBRARY_PATH   and   LD_PREOPEN.   Instead    the
> 	     QSHELL_REMOTE_LD_LIBRARY_PATH		      and
> 	     QSHELL_REMOTE_LD_PREOPEN environment variables  will
> 	     may  be used and will be remapped to LD_LIBRARY_PATH
> 	     and LD_PREOPEN by the qshell daemon if set.
>
>      mqsh    Similar  to  qshell,  but	uses  the  mrsh	 protocol
> 	     instead of	the rsh	protocol.
>
>
>
> pdsh-2.18	    Last change: solaris2.11			2
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
>      krb4    The krb4 module allows users to execute remote  com-
> 	     mands after authenticating	with kerberos. Of course,
> 	     the remote	rshd daemons must be kerberized.
>
>      xcpu    The xcpu module uses the  xcpu  service  to  execute
> 	     remote commands.
>
>
> OPTIONS
>      The list of available options is determined  at  runtime  by
>      supplementing  the	 list  of  standard pdsh options with any
>      options provided by loaded	rcmd and misc modules.	 In  some
>      cases,  options  provided	by modules may conflict	with each
>      other. In these cases, the	modules	are incompatible and  the
>      first module loaded wins.
>
>
> Standard target	nodelist options
>      -w	[rcmd_type:][user@]host,host,...
> 	  Target the specified list of hosts. Do not use with any
> 	  other	 node  selection options (e.g. -a, -g if they are
> 	  available).  No  spaces  are	allowed	 in  the   comma-
> 	  separated  list.   A	list  consisting  of a single `-'
> 	  character causes the	target	hosts  to  be  read  from
> 	  stdin, one per line. The host	list may contain hostlist
> 	  expressions  of  the	form  ``host[1-5,7]''.	For  more
> 	  information about the	hostlist format, see the HOSTLIST
> 	  EXPRESSIONS section below. A list of hosts may also  be
> 	  preceded  by "user@" to specify a remote username other
> 	  than the default, or "rcmd_type:" to specify an  alter-
> 	  nate	rcmd  connection  type for these hosts.	When used
> 	  together, the	rcmd type must be specified  first,  e.g.
> 	  "ssh:user1@host0"  would use ssh to connect to host0 as
> 	  user "user1."
>
>      -x	host,host,...
> 	  Exclude the specified	hosts. May be specified	 in  con-
> 	  junction with	other target node list options such as -a
> 	  and -g (when available). Hostlists may also  be  speci-
> 	  fied	to  the	 -x  option (see the HOSTLIST EXPRESSIONS
> 	  section below).
>
>
> Standard pdsh options
>      -S	  Return the largest of	the remote command return values.
>
>      -h	  Output usage menu and	quit. A	list  of  available  rcmd
> 	  modules  will	 also  be printed at the end of	the usage
> 	  message.
>
>      -s	  Only on AIX, separate	remote command stderr and  stdout
> 	  into two sockets.
>
>
>
> pdsh-2.18	    Last change: solaris2.11			3
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
>      -q	  List option values and the  target  nodelist	and  exit
> 	  without action.
>
>      -b	  Disable ctrl-C status	feature	so that	a  single  ctrl-C
> 	  kills	parallel job. (Batch Mode)
>
>      -l	user
> 	  This option may be  used  to	run  remote  commands  as
> 	  another  user,  subject to authorization. For	BSD rcmd,
> 	  this means the invoking user and system must be  listed
> 	  in the user's	.rhosts	file (even for root).
>
>      -t	seconds
> 	  Set the connect timeout. Default is 10 seconds.
>
>      -u	seconds
> 	  Set a	limit on the amount of time a remote  command  is
> 	  allowed  to  execute.	 Default is no limit. See note in
> 	  LIMITATIONS if using -u with ssh.
>
>      -f	number
> 	  Set the maximum number of simultaneous remote	 commands
> 	  to number.  The default is 32.
>
>      -R	name
> 	  Set rcmd module to name. This	option may  also  be  set
> 	  via  the PDSH_RCMD_TYPE environment variable.	A list of
> 	  available rcmd modules may be	obtained via the -h,  -V,
> 	  or  -L  options.  The	default	will be	listed with -h or
> 	  -V.
>
>      -L	  List info on all loaded pdsh modules and quit.
>
>      -N	  Disable hostname: prefix on lines of output.
>
>      -d	  Include more complete	 thread	 status	 when  SIGINT  is
> 	  received,  and display connect and command time statis-
> 	  tics on stderr when done.
>
>      -V	  Output pdsh version information,  along  with	 list  of
> 	  currently loaded modules, and	exit.
>
>
> qsh/mqsh module	options
>      -n	tasks_per_node
> 	  Set the number of tasks spawned per node. Default is 1.
>
>      -m	block |	cyclic
> 	  Set block versus  cyclic  allocation	of  processes  to
> 	  nodes. Default is block.
>
>      -r	railmask
>
>
>
> pdsh-2.18	    Last change: solaris2.11			4
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
> 	  Set the rail bitmask for a job on a  multirail  system.
> 	  The  default railmask	is 1, which corresponds	to rail	0
> 	  only.	Each bit set in	the argument to	-r corresponds to
> 	  a  rail on the system, so a value of 2 would correspond
> 	  to rail 1 only, and 3	would indicate to use both rail	1
> 	  and rail 0.
>
>
> machines module	options
>      -a	  Target all nodes from	machines file.
>
>
> genders	module options
>      In	addition to the	 genders  options  presented  below,  the
>      genders  attribute	 pdsh_rcmd_type	 may  also be used in the
>      genders database to specify an alternate rcmd  connect  type
>      than the pdsh default in the genders file
>
>        host0 pdsh_rcmd_type=ssh
>
>      would cause pdsh to use ssh to connect to host0, even if rsh
>      were the default.	This can be overridden on the commandline
>      with the "rcmd_type:host0"	syntax.
>
>
>      -A	  Target all nodes in genders  database.  The  -A  option
> 	  will target every host listed	in genders -- if you want
> 	  to omit some hosts by	default, see the -a option below.
>
>      -a	  Target all nodes in genders database except those  with
> 	  the  "pdsh_all_skip"	attribute.  This is shorthand for
> 	  running "pdsh	-A -X pdsh_all_skip ..."
>
>      -g	attr[=val][,attr[=val],...]
> 	  Target nodes that match any of  the  specified  genders
> 	  attributes  (with  optional  values).	Conflicts with -a
> 	  and -w options. This option targets the alternate host-
> 	  names	in the genders database	by default. The	-i option
> 	  provided by the genders module may be	used to	translate
> 	  these	 to  the  canonical  genders  hostnames.  If  the
> 	  installed version of genders	supports  it,  attributes
> 	  supplied  to	-g  may	 also  take  the  form of genders
> 	  queries. Genders queries will	query the  genders  data-
> 	  base	for  the union,	intersection, difference, or com-
> 	  plement of genders  attributes  and  values.	 The  set
> 	  operation  union  is	represented  by	 two pipe symbols
> 	  ('||'), intersection by two ampersand	 symbols  ('&&'),
> 	  difference  by two minus symbols ('--'), and complement
> 	  by a tilde ('~').  Parentheses may be	 used  to  change
> 	  the  order  of  operations. See the nodeattr(1) manpage
> 	  for examples of genders queries.
>
>
>
>
> pdsh-2.18	    Last change: solaris2.11			5
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
>      -X	attr[=val][,attr[=val],...]
> 	  Exclude nodes	that match any of the  specified  genders
> 	  attributes  (optionally  with	values).  This option may
> 	  be used in combination  with	any  other  of	the  node
> 	  selection  options  (e.g.  -w, -g, -a, -X may	also take
> 	  the form of genders queries. Please  see  documentation
> 	  for  the  genders  -g	option for more	information about
> 	  genders queries.
>
>      -i	  Request translation  between	canonical  and	alternate
> 	  hostnames.
>
>      -F	filename
> 	  Read genders information from	filename instead  of  the
> 	  system default genders file.
>
>
> nodeupdown module options
>      -v	  Eliminate target nodes that are  considered  "down"  by
> 	  libnodeupdown.
>
>
> slurm module options
>      The slurm module  allows  pdsh  to	 target	 nodes	based  on
>      currently	running	SLURM jobs. The	slurm module is	typically
>      called after all other node selection options have	been pro-
>      cessed,  and if no	nodes have been	selected, the module will
>      attempt  to  read	a  running  jobid  from	 the  SLURM_JOBID
>      environment  variable  (which  is	set  when running under	a
>      SLURM allocation).	If SLURM_JOBID references an invalid job,
>      it	will be	silently ignored.
>
>      -j	jobid[,jobid,...]
> 	  Target list of nodes allocated to the	SLURM job  jobid.
> 	  This option may be used multiple times to target multi-
> 	  ple SLURM jobs. The special argument "all" can be  used
> 	  to target all	nodes running SLURM jobs, e.g.	-j all.
>
>
> rms module options
>      The rms module allows pdsh	to target nodes	based on  an  RMS
>      resource. The rms module is typically called after	all other
>      node selection options, and if no nodes have been	selected,
>      the module	will examine the RMS_RESOURCEID	environment vari-
>      able and attempt to set the target	 list  of  hosts  to  the
>      nodes  in	the  RMS  resource.  If	 an  invalid  resource is
>      denoted, the variable is silently ignored.
>
>
> SDR module options
>      The SDR module supports targeting hosts via the System  Data
>      Repository	on IBM SPs.
>
>
>
> pdsh-2.18	    Last change: solaris2.11			6
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
>      -a	  Target all nodes in the SDR. The list	is generated from
> 	  the "reliable	hostname" in the SDR by	default.
>
>      -i	  Translate hostnames between reliable and initial in the
> 	  SDR, when applicable.	 If the	a target hostname matches
> 	  either the initial or	reliable hostname in the SDR, the
> 	  alternate name will be substitued. Thus a list composed
> 	  of initial hostnames will instead be	replaced  with	a
> 	  list	of  reliable  hostnames.   For example,	when used
> 	  with -a above, all initial hostnames	in  the	 SDR  are
> 	  targeted.
>
>      -v	  Do not target	nodes that are marked as  not  responding
> 	  in  the  SDR	on the targeted	interface. (If a hostname
> 	  does not appear in the SDR, then that	name will  remain
> 	  in the target	hostlist.)
>
>      -G	  In combination with -a, include all partitions.
>
>
> nodeattr module	options
>      The nodeattr module supports access to the	genders	 database
>      via  the  nodeattr(1) command. See	the genders section above
>      for a list	of support options with	this module.  The  option
>      usage  with  the  nodeattr	 module	 is  the same as genders,
>      above, with the exception that the	-i  option  may	 only  be
>      used  with	 -a  or	-g. NOTE: This module will only	work with
>      very old releases of genders where	the  nodeattr(1)  command
>      supports  the  -r	option,	and before the libgenders API was
>      available.	Users running newer versions of	genders	will need
>      to	use the	genders	module instead.
>
>
> dshgroup module	options
>      The dshgroup module allows	pdsh  to  use  dsh  (or	 Dancer's
>      shell)   style   group   files   from   /etc/dsh/group/   or
>      ~/.dsh/group/.
>
>      -g	groupname,...
> 	  Target nodes in dsh group  file  "groupname"	found  in
> 	  either	     ~/.dsh/group/groupname	       or
> 	  /etc/dsh/group/groupname.
>
>      -X	groupname,...
> 	  Exclude nodes	in dsh group file "groupname."
>
>
> netgroup module	options
>      The netgroup module allows	pdsh  to  use  standard	 netgroup
>      entries  to  build	 lists of target hosts.	(/etc/netgroup or
>      NIS)
>
>
>
>
> pdsh-2.18	    Last change: solaris2.11			7
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
>      -g	groupname,...
> 	  Target nodes in netgroup "groupname."
>
>      -X	groupname,...
> 	  Exclude nodes	in netgroup "groupname."
>
>
> ENVIRONMENT VARIABLES
>      PDSH_RCMD_TYPE
> 	  Equivalent to	the -R option, the value of this environ-
> 	  ment	variable  will	be  used  to set the default rcmd
> 	  module for pdsh to use (e.g. ssh, rsh).
>
>      PDSH_SSH_ARGS
> 	  Override the standard	arguments that pdsh passes to the
> 	  ssh(1) command ("-2 -a -x").
>
>      PDSH_SSH_ARGS_APPEND
> 	  Append additional options to the ssh(1) command invoked
> 	  by  pdsh.  For example, PDSH_SSH_ARGS_APPEND="-q" would
> 	  run ssh in quiet mode, or "-v" would increase	the  ver-
> 	  bosity of ssh.
>
>      WCOLL
> 	  If no	other node selection option is	used,  the  WCOLL
> 	  environment  variable	 may  be  set  to a filename from
> 	  which	a list of target hosts will  be	 read.	The  file
> 	  should  contain  a  list of hosts, one per line (though
> 	  each line may	contain	a hostlist expression.	See HOST-
> 	  LIST EXPRESSIONS section below).
>
>      DSHPATH
> 	  If set, the path in DSHPATH will be used  as	the  PATH
> 	  for the remote processes.
>
>      FANOUT
> 	  Set the pdsh fanout (See description of -f above).
>
>
> HOSTLIST EXPRESSIONS
>      As	noted in sections above	pdsh accepts lists of  hosts  the
>      general  form:  prefix[n-m,l-k,...],  where n < m and l < k,
>      etc., as an alternative to	explicit  lists	 of  hosts.  This
>      form  should not be confused with regular expression charac-
>      ter classes (also denoted by ``[]''). For	example,  foo[19]
>      does  not represent an expression matching	foo1 or	foo9, but
>      rather represents the degenerate hostlist:	foo19.
>
>      The hostlist syntax is meant only as a convenience	on  clus-
>      ters  with	a "prefixNNN" naming convention	and specification
>      of	 ranges	 should	 not  be  considered  necessary	 --  this
>      foo1,foo9	could  be  specified  as such, or by the hostlist
>
>
>
> pdsh-2.18	    Last change: solaris2.11			8
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
>      foo[1,9].
>
>      Some examples of usage follow:
>
>
>      Run command on foo01,foo02,...,foo05
> 	 pdsh -w foo[01-05] command
>
>      Run command on foo7,foo9,foo10
> 	 pdsh -w foo[7,9-10] command
>
>      Run command on foo0,foo4,foo5
> 	 pdsh -w foo[0-5] -x foo[1-3] command
>
>
>      A suffix on the hostname is also supported:
>
>
>      Run command on foo0-eth0,foo1-eth0,foo2-eth0,foo3-eth0
> 	pdsh -w	foo[0-3]-eth0 command
>
>
>      As	a reminder to the  reader,  some  shells  will	interpret
>      brackets  ('['  and ']') for pattern matching.  Depending on
>      your shell, it may	be  necessary  to  enclose  ranged  lists
>      within  quotes.   For  example,  in  tcsh,	the first example
>      above should be executed as:
>
> 	 pdsh -w "foo[01-05]" command
>
>
> ORIGIN
>      Originally	 a  rewrite  of	 IBM  dsh(1)   by   Jim	  Garlick
>      <garlick@llnl.gov>	 on  LLNL's ASCI Blue-Pacific IBM SP sys-
>      tem. It is	now used on Linux clusters at LLNL.
>
>
> LIMITATIONS
>      When using	ssh for	remote execution, expect  the  stderr  of
>      ssh  to  be  folded in with that of the remote command. When
>      invoked by	pdsh, it is not	possible for ssh  to  prompt  for
>      passwords	if  RSA/DSA  keys  are configured properly, etc..
>      For ssh implementations  that  suppport  a	 connect  timeout
>      option,  pdsh  attempts  to  use  that option to enforce the
>      timeout (e.g.  -oConnectTimeout=T	for  OpenSSH),	otherwise
>      connect timeouts are not supported	when using ssh.	 Finally,
>      there is no reliable way for pdsh to ensure that remote com-
>      mands  are	actually terminated when using a command timeout.
>      Thus if -u	is used	with ssh commands may be left running  on
>      remote  hosts  even  after	 timeout  has  killed  local  ssh
>      processes.
>
>
>
>
> pdsh-2.18	    Last change: solaris2.11			9
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
>      Output from multiple processes per	node may be  interspersed
>      when using	qshell or mqshell rcmd modules.
>
>      The number	of nodes that  pdsh  can  simultaneously  execute
>      remote  jobs  on is limited by the	maximum	number of threads
>      that can be created concurrently, as well as the  availabil-
>      ity of reserved ports in the rsh and qshell rcmd modules. On
>      systems that implement Posix threads, the limit is	typically
>      defined by	the constant PTHREADS_THREADS_MAX.
>
>
> FILES
> ATTRIBUTES
>      See attributes(5) for descriptions	of the	following  attri-
>      butes:
>
>
>
>      ____________________________________________________________
>     |	    ATTRIBUTE TYPE	  |	  ATTRIBUTE VALUE	|
>     |_____________________________|_____________________________|
>     | Availability		  | SUNWpdsh			|
>     |_____________________________|_____________________________|
>     | Interface	Stability	  | uncommitted			|
>     |_____________________________|_____________________________|
>
>
> SEE ALSO
>      rsh(1),	     ssh(1),	      dshbak(1),	  pdcp(1)
>      http://sourceforge.net/projects/pdsh/
>
> NOTES
>      Source for	pdsh is	available on http://opensolaris.org
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> pdsh-2.18	    Last change: solaris2.11		       10
>
>
>   
> ------------------------------------------------------------------------
>
> Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2009 Sun Microsystems 1. Introduction
>     1.1. Project/Component Working Name:
> 	 pdsh Ver 2.18
>     1.2. Name of Document Author/Supplier:
> 	 Author:  Vivek R. Titarmare
>     1.3  Date of This Document:
> 	 3rd April, 2009
>
> 2. Project Summary
>    2.1 Project Description
>
> 	Parallel command execution for clusters
>
> 4. Technical Description:
>
> 	Pdsh is a high-performance, parallel remote shell utility. It has built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and can call SSH externally (though with reduced performance). Pdsh uses a "sliding window" parallel algorithm to conserve socket resources on the initiating node and to allow progress to continue while timeouts occur on some connections.
> 	
> 	Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which runs commands on a single remote host, pdsh can run multiple remote commands in parallel. pdsh uses a "sliding window" (or fanout) of threads to conserve resources on the the initiating host while allowing some connections to time out. 	
>
> 5. Interfaces 
>
> 	The binary file "pdsh" contains following interface.
>
>    Exported interface                   Classification 		Interface type
>    =============================        ============== 		==============
>    	usr/bin/dshbak			Uncommitted		binary
>    	usr/bin/pdcp			Uncommitted		binary
>    	usr/bin/pdsh			Uncommitted		binary
>    	usr/bin/rpdcp			Uncommitted		binary
>    	usr/lib/pdsh/xrcmd.so		Uncommitted		shared library
>    	usr/lib/pdsh/xrcmd.la		Uncommitted		library tool
>    	usr/lib/pdsh/xrcmd.a		Uncommitted		static library
>    	usr/lib/pdsh/execcmd.so		Uncommitted		shared library
>    	usr/lib/pdsh/execcmd.la		Uncommitted		library tool
>    	usr/lib/pdsh/execcmd.a		Uncommitted		static library
>    	
> 	PDSH_RCMD_TYPE			Uncommitted		override standard argument
> 	PDSH_SSH_ARGS			Uncommitted		override standard argument
> 	PDSH_SSH_ARGS_APPEND		Uncommitted		override standard argument
> 	WCOLL				Uncommitted		override standard argument
> 	DSHPATH				Uncommitted		override standard argument
> 	FANOUT				Uncommitted		override standard argument
> 	QSHELL_REMOTE_LD_LIBRARY_PATH	Uncommitted		override standard argument
> 	QSHELL_REMOTE_LD_PREOPEN	Uncommitted		override standard argument
> 	
>
>    Imported interface        Classification   Comments
>    =======================   ==============   =================================== 
> 	None
>
>    The binary file would go in "usr/bin" and the libraries would go in "usr/lib"
>
>
> 6. Resources and Schedule
>     6.4. Steering Committee requested information
>    	6.4.1. Consolidation C-team Name:
> 		SFW
>     6.5. ARC review type: FastTrack
>     6.6. ARC Exposure: open
> ------------------------------------------------------------------------
>
> FCL--FOSS Check List
>
> 1.0 Project Information
> 1.1 Name of project/component
> 	pdsh  Ver 2.18
>
> 1.2 Author of document
> 	Vivek R. Titarmare
>
> 2.0 Project Summary
>   2.1 Project Description
>
> 	Pdsh is a high-performance, parallel remote shell utility. It has built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and can call SSH externally (though with reduced performance). Pdsh uses a "sliding window" parallel algorithm to conserve socket resources on the initiating node and to allow progress to continue while timeouts occur on some connections.
> 	
> 	Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which runs commands on a single remote host, pdsh can run multiple remote commands in parallel. pdsh uses a "sliding window" (or fanout) of threads to conserve resources on the the initiating host while allowing some connections to time out. 	
>
> 	Pdsh is a an efficient, multithreaded remote shell client which executes commands on multiple remote hosts in parallel. Pdsh implements dynamically loadable modules for extended functionality such as new remote shell services and remote host selection
>
>   2.2 Release binding
>       What is is the release binding?
>       (see http://opensolaris.org/os/community/arc/policies/release-taxonomy/)
>       [ ] Major
>       [X] Minor
>       [ ] Patch or Micro
>       [ ] Unknown -- ARC review required
>
>   2.3 Type of project
>       Is this case a Linux Familiarity project?
>       [X] Yes
>       [ ] No
>
>   2.4 Originating Community
>     2.4.1 Community Name
> 	    PDSH (http://sourceforge.net/projects/pdsh/)
>     
>     2.4.2 Community Involvement
>       Indicate Sun's involvement in the community
>       [ ] Maintainer
>       [ ] Contributor
>       [X] Monitoring
>       
>       Will the project team work with the upstream community to resolve
>       architectural issues of interest to Sun?
>       [X] Yes 
>       [ ] No - briefly explain
>       
> 	
>       Will we or are we forking from the community?
>       [ ] Yes - ARC review required prior to forking
>       [X] No
>       
> 3.0 Technical Description
>   3.1 Installation & Sharable
>     3.1.1S Solaris Installation - section only required for Solaris Software
>       (see http://opensolaris.org/os/community/arc/policies/install-locations/ for details)
>       Does this project follow the Install Locations best practice?
>       [X] Yes 
>       [ ] No - ARC review required
>       
>       Does this project install into /usr under [sbin|bin|lib|include|man|share]?
>       [X] Yes
>       [ ] No or N/A
>       
>       Does this project install into /opt?
>       [ ] Yes - explain below
>       [X] No or N/A
>       
>       Does this project install into a different directory structure?
>       [ ] Yes - ARC review required
>       [X] No or N/A
>       
>       Do any of the components of this project conflict with anything under /usr?
>       (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for details)
>       [ ] Yes - explain below
>       [X] No
>       
>       If conflicts exist then will this project install under /usr/gnu?
>       [ ] Yes
>       [ ] No - ARC review required
>       [X] N/A
>       
>       Is this project installing into /usr/sfw?
>       [ ] Yes - ARC review required
>       [X] No
>       
>     3.1.1W Windows Installation - section only required for Windows Software
>       (see http://sac.sfbay/WSARC/2002/494 for details)
>       Does this project install software into a 
>       <system drive>:\Program Files\Sun\<product> or <system drive>:\Sun\<product>
>       directory?
>       [ ] Yes
>       [ ] No - ARC review required
>       
>       Does the project use the Windows registry?
>       [ ] Yes
>       [ ] No - ARC review required
>       
>       Does the project use 
>       HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\<product>\<version>
>       for the registry key?
>       [ ] Yes
>       [ ] No - ARC review required
>       
>       Is the project's stored location
>       HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\<product id>\<version id>\Path?
>       [ ] Yes
>       [ ] No - ARC review required
>       
>     3.1.2 Share and Sharable
>       Does the module include any components that are used or shared by 
>       other projects?
>       [X] Yes
>       [ ] No
>     
>       If yes are these components packaged to be shared with the other FOSS?
>       [X] Yes
>       [ ] No - ARC review required
>       [ ] N/A
>     
>       Are these components already in the Solaris WOS?
>       [X] Yes
>       [ ] No - continue with next section (section 3.2)
>     
>       If yes are these newer versions being delivered?
>       [X] Yes
>       [ ] No - ARC review required
>       
>       If yes are the newer versions replacing the existing versions?
>       [X] Yes
>       [ ] No - ARC review required
>
>   3.2 Exported Libraries
>       Are libraries being delivered by this project?
>       [ ] Yes
>       [X] No - continue with next section (section 3.3)
>       
>       Are 64-bit versions of the libraries being delivered?
>       [ ] Yes
>       [ ] No - ARC review required
>     
>       Are static versions of the libraries being delivered?
>       [ ] Yes - ARC review required
>       [ ] No 
>       
>   3.3 Services and the /etc Directory
>       (see http://opensolaris.org/os/community/arc/policies/SMF-policy/)
>       Does the project integrate anything into /etc/init.d or /etc/rc?.d?
>       [ ] Yes - ARC review required
>       [X] No
>       
>       Does the project integrate any new entries into /etc/inittab or
>       /etc/inetd.conf?
>       [ ] Yes - ARC review required
>       [X] No
>       
>       Does the project integrate any private non-public files into /etc/default
>       or /etc/ configuration files?
>       [ ] Yes - ARC review required
>       [X] No
>       
>       Does the service manifests method context grant rights above that
>       of the noaccess user and basic privilege set?
>       [ ] Yes - ARC review required
>       [X] No
>         
>   3.4 Security
>     3.4.1 Secure By Default 
>       (see http://opensolaris.org/os/community/arc/policies/secure-by-default/ for details)
>       (see http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for details)
>       (see parts of http://opensolaris.org/os/community/arc/policies/SMF-policy/ for
>        addtional details)
>       Are there any network services provided by this project?
>       [ ] Yes
>       [X] No - continue with the next section (section 3.4.2)
>       
>       Are network services enabled by default?
>       [ ] Yes - ARC review required
>       [ ] No
>       [X] N/A
>       
>       Are network services automatically enabled by the project during installation?
>       [ ] Yes - ARC review required
>       [ ] No
>       [X] N/A
>       
>       Are inbound network communications denied by default?
>       [ ] Yes
>       [ ] No - ARC review required
>       [X] N/A
>       
>       Is inbound data checked to prevent content-based attacks?
>       [ ] Yes
>       [ ] No - ARC review required
>       [X] N/A
>       
>       Is the outbound receiver authenticated?
>       [ ] Yes
>       [ ] No - ARC review required
>       [X] N/A
>       
>       Is the receiver authenticated prior to receiving any sensitive outbound communication?
>       [ ] Yes
>       [ ] No - ARC review required
>       [X] N/A
>       
>     3.4.2 Authorization
>       (see http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and
> 	   http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and
> 	   http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/
>            for details)
>       Are there any setuid/setgid privileged binaries in the project?
>       [ ] Yes - ARC review required
>       [X] No - continue with next section (section 3.4.3)
>       
>       If yes then are the setuid/setgid privileges handled by the use of roles?
>       [ ] Yes
>       [ ] No - ARC review required
>
>     3.4.3 Auditing
>       (see http://opensolaris.org/os/community/arc/policies/audit-policy/ for details)
>       (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details)
>       Does this component contain administrative or security enforcing software?
>       [ ] Yes - ARC review required
>       [X] No - continue to next section (section 3.4.4)
>       
>       (see http://opensolaris.org/os/community/arc/caselog/2003/397 for details)
>       Do the components create audit logs detailing what took place including what event
>       took place, who was involved, when the event took place?
>       [ ] Yes - ARC contract and Audit project team review required
>       [ ] No - ARC review required
>         
>         
>     3.4.4 Authentication
>       (see http://opensolaris.org/os/community/arc/policies/PAM/)
>       Do the components contain any authentication code?
>       [ ] Yes
>       [X] No - continue to next section (section 3.4.5)
>       
>       If yes do the components use PAM (plugable authentication modules) for authentication?
>       [ ] Yes
>       [ ] No - ARC review required
>       
>       If yes is a single PAM session maintained during authentication?
>       [ ] Yes
>       [ ] No - ARC review required
>       
>       If yes are the components sufficiently privileged to allow the requested 
>       operations (authentication, password change, process credential manipulation, 
>       audit state initialization)?
>       [ ] Yes - briefly describe below
>       [ ] No - ARC review required
>       
>     3.4.5 Passwords
>       (see http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and
>            http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for details)
>       Do any of the components for the project deal with passwords?
>       [ ] Yes
>       [X] No - continue to next section (section 3.4.6)
>       
>       If yes are these passwords entered via the CLI or environment?
>       [ ] Yes - ARC review required
>       [ ] No
>       
>       Are passwords stored within the file system for the component?
>       [ ] Yes
>       [ ] No - continue to next section (section 3.4.6)
>       
>       If yes are the permissions on the file such to protect exposing the password(s)?
>       [ ] Yes
>       [ ] No - ARC review required
>       
>     3.4.6 General Security Questions
>       (see http://opensolaris.org/os/community/arc/bestpractices/security-questions/ for details)
>       Are there any network protocols used by this project?
>       [X] Yes
>       [ ] No - continue with the next section (section 3.5)
>       
>       Do the components use standard network protocols?
>       [X] Yes
>       [ ] No - ARC review required
>       
>       Do network services for the project make decisions based upon user, host or 
>       service identities?
>       [X] Yes - explain below
>       [ ] No
>       [ ] N/A
>       
>       	pdsh makes decision on network services based upon service identities. pdsh is a variant of the rsh(1) command. The core functionality of pdsh may be supplemented by dynamically loadable modules. The modules may provide a new connection protocol (replacing the standard rcmd(3) protocol used by rsh(1)), filtering options (e.g. removing hosts that are "down" from the target list), and/or host selection options (e.g., -a selects all hosts from a configuration file.).Pdsh modules come in two flavors at this time: rcmd and miscellaneous. 
>       		
>       	The rcmd modules provide remote command functionality for pdsh. A list of rcmd modules currently distributed with pdsh follows. 
>       		rsh Uses an internal, thread-safe implementation of BSD rcmd(3) to run commands using the standard rsh(1) protocol. 
>       		ssh Uses a variant of popen(3) to run multiple copies of the ssh(1) command. 
>       		mrsh This module uses the mrsh(1) protocol to execute jobs on remote hosts. The mrsh protocol uses a credential based authentication, forgoing the need to allocate reserved ports. In other aspects, it acts just like rsh. Remote nodes must be running mrshd(8) in order for the mrsh module to work. 
>                	qsh  Allows pdsh to execute MPI jobs over QsNet. Qshell propagates the current working directory, pdsh environment, and Elan capabilities to the remote process. The following environment variable are also appended to the environment: RMS_RANK, RMS_NODEID, RMS_PROCID, RMS_NNODES, and RMS_NPROCS. 
>         Since pdsh needs to run setuid root for qshell support, qshell does not directly support propagation of LD_LIBRARY_PATH and LD_PREOPEN. Instead the QSHELL_REMOTE_LD_LIBRARY_PATH and QSHELL_REMOTE_LD_PREOPEN environment variables will may be used and will be remapped to LD_LIBRARY_PATH and LD_PREOPEN by the qshell daemon if set. 
>                 mqsh Similar to qshell, but uses the mrsh protocol instead of the rsh protocol. 
>                 krb4 The krb4 module allows users to execute remote commands after authenticating with kerberos. Of course, the remote rshd daemons must be kerberized. 
>                 xcpu The xcpu module uses the xcpu service to execute remote commands
>       
>       Do the components make use of secret information during authentication and/or
>       authorization?
>       [ ] Yes - explain below
>       [X] No
>       [ ] N/A
>   
>   3.5 Networking
>       Do the components access the network?
>       [X] Yes
>       [ ] No - continue with the next section (section 3.6)
>       
>       If yes do the components support IPv6?
>       [X] Yes 
>       [ ] No - ARC review required
>           
>   3.6 Core Solaris Components
>       Do the components of this project compete with or duplicate core 
>       Solaris components?
>       [ ] Yes - ARC review required
>       [X] No 
>              
> 4.0 Interfaces
>   (see http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ for details)
>   4.1 Exported Interfaces
>   
>     The binary file "pdsh" contains following interface.
>
>     Interface Name			Classification  	    	Comments
>     ---------------------------     ------------------- 	---------------------------
>    	usr/bin/dshbak			Uncommitted		binary
>    	usr/bin/pdcp			Uncommitted		binary
>    	usr/bin/pdsh			Uncommitted		binary
>    	usr/bin/rpdcp			Uncommitted		binary
>    	usr/lib/pdsh/xrcmd.so		Uncommitted		shared library
>    	usr/lib/pdsh/xrcmd.la		Uncommitted		library tool
>    	usr/lib/pdsh/xrcmd.a		Uncommitted		static library
>    	usr/lib/pdsh/execcmd.so		Uncommitted		shared library
>    	usr/lib/pdsh/execcmd.la		Uncommitted		library tool
>    	usr/lib/pdsh/execcmd.a		Uncommitted		static library
>    	
> 	PDSH_RCMD_TYPE			Uncommitted		override standard argument
> 	PDSH_SSH_ARGS			Uncommitted		override standard argument
> 	PDSH_SSH_ARGS_APPEND		Uncommitted		override standard argument
> 	WCOLL				Uncommitted		override standard argument
> 	DSHPATH				Uncommitted		override standard argument
> 	FANOUT				Uncommitted		override standard argument
> 	QSHELL_REMOTE_LD_LIBRARY_PATH	Uncommitted		override standard argument
> 	QSHELL_REMOTE_LD_PREOPEN	Uncommitted		override standard argument
> 	
>
>   4.2 Imported Interfaces
>     Interface Name		Classification       Comments
>     --------------------------- -------------------- --------------------------
> 	None    
>
> The binary file would go in "/usr/bin" and the libraries would go in "/usr/lib"
>
> Appendix B - Suggested case materials
>   1. man pages
>
>      Attached are the man pages (pdsh.1, pdcp.1, dshbak.1)
>
>   2. SMF manifests
>   3. links to contracts
>   


From Vivek.Titarmare@sun.com Thu Apr 23 21:15:32 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3O4FVFv024892
	for <LSARC-ext@sac.sfbay.sun.com>; Thu, 23 Apr 2009 21:15:31 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3O4FRUW029953
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Fri, 24 Apr 2009 05:15:30 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KIL003097TUDF00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Thu, 23 Apr 2009 21:15:30 -0700 (PDT)
Received: from sineb-mail-1.sun.com ([192.18.19.6])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KIL002K57TR9U00@nwk-avmta-1.sfbay.Sun.COM> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Thu,
 23 Apr 2009 21:15:29 -0700 (PDT)
Received: from fe-apac-06.sun.com
 (fe-apac-06.sun.com [192.18.19.177] (may be forged))
	by sineb-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3O4FRrY029162	for
 <LSARC-ext@sun.com>; Fri, 24 Apr 2009 04:15:27 +0000 (GMT)
Received: from conversion-daemon.mail-apac.sun.com by mail-apac.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KIL00C007EUX500@mail-apac.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Fri, 24 Apr 2009 12:15:27 +0800 (SGT)
Received: from VivekTPC ([unknown] [203.199.144.195])
 by mail-apac.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit
 (built Feb 19 2009)) with ESMTPSA id <0KIL00FQU7TLFB40@mail-apac.sun.com>; Fri,
 24 Apr 2009 12:15:26 +0800 (SGT)
Date: Fri, 24 Apr 2009 09:45:19 +0530
From: Vivek Titarmare <Vivek.Titarmare@sun.com>
Subject: RE: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <49EF480E.4070106@sun.com>
Sender: Vivek.Titarmare@sun.com
To: "'Margot Miller'" <Margot.Miller@sun.com>
Cc: "'Danek Duvall'" <Danek.Duvall@sun.com>,
        "'Mark Carlson'" <markcarl@sac.sfbay.sun.com>, James.D.Carlson@sun.com,
        Nicolas.Williams@sun.com, LSARC-ext@sun.com
Message-id: <043b01c9c493$497041a0$dc50c4e0$%Titarmare@Sun.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=us-ascii
Content-language: en-us
Content-transfer-encoding: 7BIT
Thread-index: AcnDaY4ckaNUVmsvRHGSDRcEZOCeNQBKYpyA
X-PMX-Version: 5.4.1.325704
x-cr-hashedpuzzle: Bk0Z D22D MUxU XeKJ cZl1 dg+k hTJk jcTc k+IX lkd5 lpWH mLoG
 tQ9s ueqj 1VCy
 AAtNBg==;6;ZABhAG4AZQBrAC4AZAB1AHYAYQBsAGwAQABzAHUAbgAuAGMAbwBtADsAagBhAG0AZQBzAC4AZAAuAGMAYQByAGwAcwBvAG4AQABzAHUAbgAuAGMAbwBtADsAbABzAGEAcgBjAC0AZQB4AHQAQABzAHUAbgAuAGMAbwBtADsAbQBhAHIAZwBvAHQALgBtAGkAbABsAGUAcgBAAHMAdQBuAC4AYwBvAG0AOwBtAGEAcgBrAGMAYQByAGwAQABzAGEAYwAuAHMAZgBiAGEAeQAuAHMAdQBuAC4AYwBvAG0AOwBuAGkAYwBvAGwAYQBzAC4AdwBpAGwAbABpAGEAbQBzAEAAcwB1AG4ALgBjAG8AbQA=;Sosha1_v1;7;{7903F622-38BA-4C5B-9A8D-7BF1654B2989};dgBpAHYAZQBrAC4AdABpAHQAYQByAG0AYQByAGUAQABzAHUAbgAuAGMAbwBtAA==;Fri,
 24 Apr 2009 04:14:33
 GMT;UgBFADoAIABwAGQAcwBoACAAVgBlAHIAIAAyAC4AMQA4ACAAWwBMAFMAQQBSAEMALwAyADAAMAA5AC8AMgAzADgAIABGAGEAcwB0AFQAcgBhAGMAawAgAHQAaQBtAGUAbwB1AHQAIAAwADQALwAyADAALwAyADAAMAA5AF0A
x-cr-puzzleid: {7903F622-38BA-4C5B-9A8D-7BF1654B2989}
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
 <20090413205436.GX7978@mumak.SFBay.Sun.COM>
 <003001c9bd02$8997a1d0$9cc6e570$%Titarmare@Sun.com>
 <20090414150713.GA7978@mumak.SFBay.Sun.COM>
 <013801c9c2a4$e270fb10$a752f130$%Titarmare@Sun.com>
 <20090421180905.GF4425@mumak.SFBay.Sun.COM>
 <024601c9c34b$7b459110$71d0b330$%Titarmare@Sun.com> <49EF480E.4070106@sun.com>
Status: RO
Content-Length: 56101

Hi Margot,

Yes, I will be changing the man pages accordingly. This would take another
day to complete and resubmit.

Thanks,
~Vivek R. Titarmare

-----Original Message-----
From: Margot Miller [mailto:Margot.Miller@Sun.COM] 
Sent: Wednesday, April 22, 2009 10:09 PM
To: Vivek Titarmare
Cc: 'Danek Duvall'; 'Mark Carlson'; James.D.Carlson@Sun.COM;
Nicolas.Williams@Sun.COM; LSARC-ext@sun.com
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]

Vivek,

Please add the package SUNWpdsh to the interface table.

In the pdsh man page, it has:

     qsh     Allows pdsh to execute MPI	jobs over  QsNet.  Qshell
	     propagates	  the  current	working	 directory,  pdsh
	     environment, and Elan  capabilities  to  the  remote
	     process. The following environment	variable are also
	     appended to the environment:  RMS_RANK,  RMS_NODEID,
	     RMS_PROCID,  RMS_NNODES,  and RMS_NPROCS. Since pdsh
	     needs to run setuid root for qshell support,  qshell
	     does    not    directly   support	 propagation   of
	     LD_LIBRARY_PATH   and   LD_PREOPEN.   Instead    the
	     QSHELL_REMOTE_LD_LIBRARY_PATH		      and
	     QSHELL_REMOTE_LD_PREOPEN environment variables  will
	     may  be used and will be remapped to LD_LIBRARY_PATH
	     and LD_PREOPEN by the qshell daemon if set.

Does this project support Qshell?  

Also, there is a section in one of the man pages about slurm
module options.  Per Danek in the below email, this is not
relevant for Solaris.  The documentation needs to be updated
to reflect that this isn't supported on Solaris.

Please check through all the man pages to ensure that everything
in the man pages is correct wrt Solaris and what is in the man pages
is reflected in the interface table.

Also, please have your sponsor review all the materials
before you resend the updated documents.

Thanks
Margot




Vivek Titarmare wrote:
> Hi Danek and the team,
>
> I have updated the Fasttrack and FOSS check list for pdsh. Major changes
in
> the interface tables would be seen. Actually a rework was done on this
> package and found that the interface table needed a change. 
>
> Pl. ignore the previous Interface related conflicts.
>
> Let me know if this looks good to go.
>
> Pl. find attached all the files required for this ARC review.
>
> Thanks,
> ~Vivek R. Titarmare
>
>
>
> -----Original Message-----
> From: Danek Duvall [mailto:Danek.Duvall@Sun.COM] 
> Sent: Tuesday, April 21, 2009 11:39 PM
> To: Vivek Titarmare
> Cc: 'Mark Carlson'; James.D.Carlson@Sun.COM; Nicolas.Williams@Sun.COM;
> Manisha.Jha@Sun.COM
> Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
>
> [ Please use standard email quoting techniques -- a "> " prefix to every
> line that you're responding to, and not to your own; what you're doing
> makes your email responses incredibly difficult to read.  Perhaps not
using
> Outlook would help.  This is Sun, after all; you should be running
Solaris.
> ]
>
> On Tue, Apr 21, 2009 at 10:46:14PM +0530, Vivek Titarmare wrote:
>
>   
>>> No, I want you to not deliver those interfaces.  You can't ship
>>>       
> components
>   
>>> that don't work.  This is a commercial OS, not a grad student project,
>>>       
> and
>   
>>> it costs Sun tons of money to field calls from customers complaining
>>>       
> about
>   
>>> things that don't work.  It's best not to ship them at all if we know
>>> they're busted.  Given how much of the man page is filled with text
>>> describing options and arguments that won't be useful on Solaris, you'll
>>> need to remove this extraneous documentation before delivery, too.
>>>       
>> [VIVEK] I am sorry, I think I confused you. All the components work, for
>> those components to work we need to override the environment variables
>>     
> which
>   
>> I am adding those in the Interface table. I this case, do we still need
to
>> remove the contents from the man pages. Pl. let me know.
>>     
>
> The components that are unavailable (libgenders, nodeattr, etc) will cause
> portions of pdsh (pdsh-mod-genders, pdsh-mod-nodeattr, etc) not to work,
> environment variables or not.  There is no way that "pdsh-mod-slurm" is
> going to work unless slurm is installed, and since there is no slurm
> available for Solaris, then "pdsh-mod-slurm" is not going to work on
> Solaris.  So don't ship it, and don't document it.
>
> Danek
> ------------------------------------------------------------------------
>
>
>
>
> DSHBAK							DSHBAK(1)
>
>
>
> NAME
>      dshbak - format output from pdsh command
>
> SYNOPSIS
>      dshbak [-c]
>
> DESCRIPTION
>      dshbak formats pdsh output	for  humans.   Output  from  each
>      node  is consolidated, the	leading	node: prefix is	stripped,
>      and a header block	with the node name is added.  If  the  -c
>      option  is	 specified,  nodes  with identical output are not
>      displayed twice; instead, the header will contain a list  of
>      nodes.   The  list	 of nodes is further compressed	into node
>      ranges if the node	names have a numeric suffix.
>
>
> ORIGIN
>      A rewrite of IBM dshbak(1)	by Jim Garlick
>      <garlick@llnl.gov>	on LLNL's ASCI Blue-Pacific IBM	 SP  sys-
>      tem.
>
>
> ATTRIBUTES
>      See attributes(5) for descriptions	of the	following  attri-
>      butes:
>
>
>
>      ____________________________________________________________
>     |	    ATTRIBUTE TYPE	  |	  ATTRIBUTE VALUE	|
>     |_____________________________|_____________________________|
>     | Availability		  | SUNWpdsh			|
>     |_____________________________|_____________________________|
>     | Interface	Stability	  | uncommitted			|
>     |_____________________________|_____________________________|
>
>
> SEE ALSO
>      pdsh(1)
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> LLNL		    Last change: Release 1.3			1
>
>
>   
> ------------------------------------------------------------------------
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
> NAME
>      pdcp - copy files to groups of hosts in parallel
>      rpdcp - (reverse pdcp) copy files from a group of	hosts  in
>      parallel
>
>
> SYNOPSIS
>      pdcp [options]... src [src2...] dest
>      rpdcp [options]...	src [src2...] dir
>
>
> DESCRIPTION
>      pdcp is a variant of the  rcp(1)  command.	  Unlike  rcp(1),
>      which  copies  files  to a	single remote host, pdcp can copy
>      files to multiple remote hosts in parallel.   However,  pdcp
>      does not recognize	files in the format ``rname@rhost:path,''
>      therefore all  source  files  must	 be  on	 the  local  host
>      machine.	Destination nodes must be listed on the	pdcp com-
>      mand line using a suitable	target nodelist	option	(See  the
>      OPTIONS  section  below).	Each destination node listed must
>      have pdcp installed for the copy to succeed.
>
>      When pdcp receives	SIGINT (ctrl-C), it lists the  status  of
>      current  threads.	 A  second  SIGINT within one second ter-
>      minates the program. Pending  threads  may	 be  canceled  by
>      issuing ctrl-Z within one second of ctrl-C.  Pending threads
>      are those that have not yet been initiated, or are	still  in
>      the process of connecting to the remote host.
>
>      Like pdsh(1), the functionality of	pdcp may be  supplemented
>      by	 dynamically  loadable	modules. In pdcp, the modules may
>      provide a	new  connect  protocol	(replacing  the	 standard
>      rsh(1)  protocol),	 filtering  options (e.g. excluding hosts
>      that are down),  and/or  host  selection  options	(e.g.  -a
>      selects  all  nodes  from a local config file).  By default,
>      pdcp requires at least one	"rcmd" module to  be  loaded  (to
>      provide the channel for remote copy).
>
>
> REVERSE	PDCP
>      rpdcp performs a reverse parallel copy.  Rather than copying
>      files to remote hosts, files are retrieved	from remote hosts
>      and stored	locally.  All directories or files retrieved will
>      be	 stored	 with  their  remote  hostname	appended  to  the
>      filename.	The destination	file must  be  a  directory  when
>      this option is used.
>
>      In	other respects,	rpdcp is exactly like pdcp,  and  further
>      statements	 regarding  pdcp  in  this  manual  also apply to
>      rpdcp.
>
>
>
>
>
> pdsh-2.18	    Last change: solaris2.11			1
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
> RCMD MODULES
>      The method	by which pdcp connects to  remote  hosts  may  be
>      selected at runtime using the -R option (See OPTIONS below).
>      This functionality	is ultimately implemented via dynamically
>      loadable  modules,	 and so	the list of available options may
>      be	different from installation to installation.  A	 list  of
>      currently	available  rcmd	modules	is printed when	using any
>      of	the -h,	-V, or -L options. The default rcmd  module  will
>      also be displayed with the	-h and -V options.
>
>      A list of rcmd modules currently distributed with pdcp  fol-
>      lows.
>
>      rsh     Uses an internal, thread-safe implementation of  BSD
> 	     rcmd(3)  to  run  commands	using the standard rsh(1)
> 	     protocol.
>
>      ssh     Uses a variant of popen(3)	to run multiple	copies of
> 	     the ssh(1)	command.
>
>      mrsh    This module uses the  mrsh(1)  protocol  to  execute
> 	     jobs  on  remote  hosts.	The  mrsh protocol uses	a
> 	     credential	based authentication, forgoing	the  need
> 	     to	 allocate  reserved  ports.  In	other aspects, it
> 	     acts just like rsh.
>
>      krb4    The krb4 module allows users to execute remote  com-
> 	     mands after authenticating	with kerberos. Of course,
> 	     the remote	rshd daemons must be kerberized.
>
>      xcpu    The xcpu module uses the  xcpu  service  to  execute
> 	     remote commands.
>
>
> OPTIONS
>      The list of available pdcp	options	is determined at  runtime
>      by	 supplementing the list	of standard pdcp options with any
>      options provided by loaded	rcmd and misc modules.	 In  some
>      cases,  options  provided	by modules may conflict	with each
>      other. In these cases, the	modules	are incompatible and  the
>      first module loaded wins.
>
>
> Standard target	nodelist options
>      -w	host,host,...
> 	  Target the specified list of hosts. Do not use with any
> 	  other	 node  selection options (e.g. -a, -g if they are
> 	  available).  No  spaces  are	allowed	 in  the   comma-
> 	  separated  list.   A	list  consisting  of a single `-'
> 	  character causes the	target	hosts  to  be  read  from
> 	  stdin, one per line. The host	list may contain hostlist
> 	  expressions  of  the	form  ``host[1-5,7]''.	For  more
>
>
>
> pdsh-2.18	    Last change: solaris2.11			2
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
> 	  information about the	hostlist format, see the HOSTLIST
> 	  EXPRESSIONS section below.
>
>      -x	host,host,...
> 	  Exclude the specified	hosts. May be specified	 in  con-
> 	  junction with	other target node list options such as -a
> 	  and -g (when available). Hostlists may also  be  speci-
> 	  fied	to the -x option (see HOSTLIST EXPRESSIONS secion
> 	  below).
>
>
> Standard pdcp options
>      -h	  Output usage menu and	quit. A	list  of  available  rcmd
> 	  modules  will	 be  printed at	the end	of the usage mes-
> 	  sage.
>
>      -q	  List option values and the  target  nodelist	and  exit
> 	  without action.
>
>      -b	  Disable ctrl-C status	feature	so that	a  single  ctrl-C
> 	  kills	parallel copy. (Batch Mode)
>
>      -r	  Copy directories recursively.
>
>      -p	  Preserve modification	time and modes.
>
>      -e	PATH
> 	  Explicitly specify path to remote pdcp  binary  instead
> 	  of using the locally executed	path.
>
>      -l	user
> 	  This option may be used to copy files	as another  user,
> 	  subject  to authorization. For BSD rcmd, this	means the
> 	  invoking user	and system must	be listed in  the  user's
> 	  .rhosts file (even for root).
>
>      -t	seconds
> 	  Set the connect timeout. Default is 10 seconds.
>
>      -f	number
> 	  Set the maximum number of simultaneous remote	copies to
> 	  number.  The default is 32.
>
>      -R	name
> 	  Set rcmd module to name. This	option may  also  be  set
> 	  via  the PDSH_RCMD_TYPE environment variable.	A list of
> 	  available rcmd modules may be	obtained via  either  the
> 	  -h or	-L options.
>
>      -R	name
> 	  Set rcmd module to name. This	option may  also  be  set
> 	  via  the PDSH_RCMD_TYPE environment variable.	A list of
>
>
>
> pdsh-2.18	    Last change: solaris2.11			3
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
> 	  available rcmd modules may be	obtained via  either  the
> 	  -h or	-L options.
>
>      -L	  List info on all loaded pdcp modules and quit.
>
>      -d	  Include more complete	 thread	 status	 when  SIGINT  is
> 	  received,  and display connect and command time statis-
> 	  tics on stderr when done.
>
>      -V	  Output pdcp version information,  along  with	 list  of
> 	  currently loaded modules, and	exit.
>
>
>
> HOSTLIST EXPRESSIONS
>      As	noted in sections above, pdcp accepts ranges of	hostnames
>      in	 the general form: prefix[n-m,l-k,...],	where n	< m and	l
>      < k, etc.,	as an alternative to  explicit	lists  of  hosts.
>      This  form	 should	 not  be confused with regular expression
>      character classes (also denoted  by  ``[]'').  For	 example,
>      foo[19]   does  not  represent  foo1  or  foo9,  but  rather
>      represents	a degenerate range: foo19.
>
>      This range	syntax is meant	only as	a convenience on clusters
>      with  a  prefixNN	naming	convention  and	 specification of
>      ranges should  not	 be  considered	 necessary  --	the  list
>      foo1,foo9	could  be  specified  as  such,	 or  by	the range
>      foo[1,9].
>
>      Some examples of range usage follow:
>
>
>      Copy /etc/hosts to	foo01,foo02,...,foo05
> 	 pdcp -w foo[01-05] /etc/hosts /etc
>
>      Copy /etc/hosts to	foo7,foo9,foo10
> 	 pdcp -w foo[7,9-10] /etc/hosts	/etc
>
>      Copy /etc/hosts to	foo0,foo4,foo5
>       pdcp -w foo[0-5] -x foo[1-3] /etc/hosts /etc
>
>
>      As	a reminder to the  reader,  some  shells  will	interpret
>      brackets  ('['  and ']') for pattern matching.  Depending on
>      your shell, it may	be  necessary  to  enclose  ranged  lists
>      within  quotes.   For  example,  in  tcsh,	the first example
>      above should be executed as:
>
> 	 pdcp -w "foo[01-05]" /etc/hosts /etc
>
>
>
>
>
>
> pdsh-2.18	    Last change: solaris2.11			4
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
> ORIGIN
>      Pdsh/pdcp was originally a	rewrite	of IBM dsh(1) by Jim Gar-
>      lick  <garlick@llnl.gov>  on LLNL's ASCI Blue-Pacific IBM SP
>      system.  It is now	also used on Linux clusters at LLNL.
>
>
> LIMITATIONS
>      When using	ssh for	remote execution, stderr  of  ssh  to  be
>      folded  in	with that of the remote	command.  When invoked by
>      pdcp, it is not possible for ssh to prompt	for  confirmation
>      if	 a host	key changes, prompt for	passwords if RSA keys are
>      not configured properly, etc..  Finally, the connect timeout
>      is	 only  adjustable with ssh when	the underlying ssh imple-
>      mentation supports	it, and	pdsh has been built  to	 use  the
>      correct option.
>
>
> ATTRIBUTES
>      See attributes(5) for descriptions	of the	following  attri-
>      butes:
>
>
>
>      ____________________________________________________________
>     |	    ATTRIBUTE TYPE	  |	  ATTRIBUTE VALUE	|
>     |_____________________________|_____________________________|
>     | Availability		  | SUNWpdsh			|
>     |_____________________________|_____________________________|
>     | Interface	Stability	  | uncommitted			|
>     |_____________________________|_____________________________|
>
>
> SEE ALSO
>      pdsh(1)
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> pdsh-2.18	    Last change: solaris2.11			5
>
>
>   
> ------------------------------------------------------------------------
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
> NAME
>      pdsh - issue commands to groups of	hosts in parallel
>
>
> SYNOPSIS
>      pdsh [options]... command
>
>
> DESCRIPTION
>      pdsh is a variant of  the	rsh(1)	command.  Unlike  rsh(1),
>      which  runs  commands  on a single	remote host, pdsh can run
>      multiple remote commands in parallel. pdsh	uses  a	 "sliding
>      window"  (or fanout) of threads to	conserve resources on the
>      initiating	host while allowing some connections to	time out.
>
>      When pdsh receives	SIGINT (ctrl-C), it lists the  status  of
>      current  threads.	A  second  SIGINT  within one second ter-
>      minates the program. Pending  threads  may	 be  canceled  by
>      issuing ctrl-Z within one second of ctrl-C.  Pending threads
>      are those that have not yet been initiated, or are	still  in
>      the process of connecting to the remote host.
>
>
>      If	a remote command is not	specified on  the  command  line,
>      pdsh  runs	interactively, prompting for commands and execut-
>      ing them when terminated with a carriage return. In interac-
>      tive  mode,  target nodes that time out on	the first command
>      are not contacted for subsequent commands,	and commands pre-
>      fixed  with  an  exclamation  point  will be executed on the
>      local system.
>
>      The core functionality of pdsh may	be supplemented	by dynam-
>      ically  loadable modules. The modules may provide a new con-
>      nection protocol (replacing the  standard	rcmd(3)	 protocol
>      used by rsh(1)), filtering	options	(e.g. removing hosts that
>      are "down"	from the  target  list),  and/or  host	selection
>      options  (e.g.,  -a  selects  all hosts from a configuration
>      file.). By	default, pdsh  must  have  at  least  one  "rcmd"
>      module  loaded. See the RCMD MODULES section for more infor-
>      mation.
>
>
> RCMD MODULES
>      The method	by which pdsh runs commands on remote  hosts  may
>      be	 selected  at  runtime	using  the -R option (See OPTIONS
>      below).  This functionality is  ultimately	 implemented  via
>      dynamically  loadable  modules, and so the	list of	available
>      options may be different from installation	to  installation.
>      A	list  of currently available rcmd modules is printed when
>      using any of the -h, -V, or -L  options.  The  default  rcmd
>      module will also be displayed with	the -h and -V options.
>
>
>
>
> pdsh-2.18	    Last change: solaris2.11			1
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
>      A list of rcmd modules currently distributed with pdsh  fol-
>      lows.
>
>      rsh     Uses an internal, thread-safe implementation of  BSD
> 	     rcmd(3)  to  run  commands	using the standard rsh(1)
> 	     protocol.
>
>      exec    Executes an arbitrary command for each target  host.
> 	     The  first	of the pdsh remote arguments is	the local
> 	     command to	execute, followed by  any  further  argu-
> 	     ments.  Some simple parameters are	substitued on the
> 	     command line, including %h	for the	target	hostname,
> 	     %u	 for  the  remote username, and	%n for the remote
> 	     rank [0-n]	(To get	a literal % use	%%).   For  exam-
> 	     ple,  the	following  would  duplicate using the ssh
> 	     module to run hostname(1) across  the  hosts  foo[0-
> 	     10]:
>
> 		pdsh -R	exec -w	foo[0-10] ssh -x -l %u %h hostname
>
> 	     and this command line would run grep(1) in	 parallel
> 	     across the	files console.foo[0-10]:
>
> 		pdsh -R	exec -w	foo[0-10] grep BUG console.%h
>
>
>      ssh     Uses a variant of popen(3)	to run multiple	copies of
> 	     the ssh(1)	command.
>
>      mrsh    This module uses the  mrsh(1)  protocol  to  execute
> 	     jobs  on  remote  hosts.	The  mrsh protocol uses	a
> 	     credential	based authentication, forgoing	the  need
> 	     to	 allocate  reserved  ports.  In	other aspects, it
> 	     acts just like rsh. Remote	 nodes	must  be  running
> 	     mrshd(8) in order for the mrsh module to work.
>
>      qsh     Allows pdsh to execute MPI	jobs over  QsNet.  Qshell
> 	     propagates	  the  current	working	 directory,  pdsh
> 	     environment, and Elan  capabilities  to  the  remote
> 	     process. The following environment	variable are also
> 	     appended to the environment:  RMS_RANK,  RMS_NODEID,
> 	     RMS_PROCID,  RMS_NNODES,  and RMS_NPROCS. Since pdsh
> 	     needs to run setuid root for qshell support,  qshell
> 	     does    not    directly   support	 propagation   of
> 	     LD_LIBRARY_PATH   and   LD_PREOPEN.   Instead    the
> 	     QSHELL_REMOTE_LD_LIBRARY_PATH		      and
> 	     QSHELL_REMOTE_LD_PREOPEN environment variables  will
> 	     may  be used and will be remapped to LD_LIBRARY_PATH
> 	     and LD_PREOPEN by the qshell daemon if set.
>
>      mqsh    Similar  to  qshell,  but	uses  the  mrsh	 protocol
> 	     instead of	the rsh	protocol.
>
>
>
> pdsh-2.18	    Last change: solaris2.11			2
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
>      krb4    The krb4 module allows users to execute remote  com-
> 	     mands after authenticating	with kerberos. Of course,
> 	     the remote	rshd daemons must be kerberized.
>
>      xcpu    The xcpu module uses the  xcpu  service  to  execute
> 	     remote commands.
>
>
> OPTIONS
>      The list of available options is determined  at  runtime  by
>      supplementing  the	 list  of  standard pdsh options with any
>      options provided by loaded	rcmd and misc modules.	 In  some
>      cases,  options  provided	by modules may conflict	with each
>      other. In these cases, the	modules	are incompatible and  the
>      first module loaded wins.
>
>
> Standard target	nodelist options
>      -w	[rcmd_type:][user@]host,host,...
> 	  Target the specified list of hosts. Do not use with any
> 	  other	 node  selection options (e.g. -a, -g if they are
> 	  available).  No  spaces  are	allowed	 in  the   comma-
> 	  separated  list.   A	list  consisting  of a single `-'
> 	  character causes the	target	hosts  to  be  read  from
> 	  stdin, one per line. The host	list may contain hostlist
> 	  expressions  of  the	form  ``host[1-5,7]''.	For  more
> 	  information about the	hostlist format, see the HOSTLIST
> 	  EXPRESSIONS section below. A list of hosts may also  be
> 	  preceded  by "user@" to specify a remote username other
> 	  than the default, or "rcmd_type:" to specify an  alter-
> 	  nate	rcmd  connection  type for these hosts.	When used
> 	  together, the	rcmd type must be specified  first,  e.g.
> 	  "ssh:user1@host0"  would use ssh to connect to host0 as
> 	  user "user1."
>
>      -x	host,host,...
> 	  Exclude the specified	hosts. May be specified	 in  con-
> 	  junction with	other target node list options such as -a
> 	  and -g (when available). Hostlists may also  be  speci-
> 	  fied	to  the	 -x  option (see the HOSTLIST EXPRESSIONS
> 	  section below).
>
>
> Standard pdsh options
>      -S	  Return the largest of	the remote command return values.
>
>      -h	  Output usage menu and	quit. A	list  of  available  rcmd
> 	  modules  will	 also  be printed at the end of	the usage
> 	  message.
>
>      -s	  Only on AIX, separate	remote command stderr and  stdout
> 	  into two sockets.
>
>
>
> pdsh-2.18	    Last change: solaris2.11			3
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
>      -q	  List option values and the  target  nodelist	and  exit
> 	  without action.
>
>      -b	  Disable ctrl-C status	feature	so that	a  single  ctrl-C
> 	  kills	parallel job. (Batch Mode)
>
>      -l	user
> 	  This option may be  used  to	run  remote  commands  as
> 	  another  user,  subject to authorization. For	BSD rcmd,
> 	  this means the invoking user and system must be  listed
> 	  in the user's	.rhosts	file (even for root).
>
>      -t	seconds
> 	  Set the connect timeout. Default is 10 seconds.
>
>      -u	seconds
> 	  Set a	limit on the amount of time a remote  command  is
> 	  allowed  to  execute.	 Default is no limit. See note in
> 	  LIMITATIONS if using -u with ssh.
>
>      -f	number
> 	  Set the maximum number of simultaneous remote	 commands
> 	  to number.  The default is 32.
>
>      -R	name
> 	  Set rcmd module to name. This	option may  also  be  set
> 	  via  the PDSH_RCMD_TYPE environment variable.	A list of
> 	  available rcmd modules may be	obtained via the -h,  -V,
> 	  or  -L  options.  The	default	will be	listed with -h or
> 	  -V.
>
>      -L	  List info on all loaded pdsh modules and quit.
>
>      -N	  Disable hostname: prefix on lines of output.
>
>      -d	  Include more complete	 thread	 status	 when  SIGINT  is
> 	  received,  and display connect and command time statis-
> 	  tics on stderr when done.
>
>      -V	  Output pdsh version information,  along  with	 list  of
> 	  currently loaded modules, and	exit.
>
>
> qsh/mqsh module	options
>      -n	tasks_per_node
> 	  Set the number of tasks spawned per node. Default is 1.
>
>      -m	block |	cyclic
> 	  Set block versus  cyclic  allocation	of  processes  to
> 	  nodes. Default is block.
>
>      -r	railmask
>
>
>
> pdsh-2.18	    Last change: solaris2.11			4
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
> 	  Set the rail bitmask for a job on a  multirail  system.
> 	  The  default railmask	is 1, which corresponds	to rail	0
> 	  only.	Each bit set in	the argument to	-r corresponds to
> 	  a  rail on the system, so a value of 2 would correspond
> 	  to rail 1 only, and 3	would indicate to use both rail	1
> 	  and rail 0.
>
>
> machines module	options
>      -a	  Target all nodes from	machines file.
>
>
> genders	module options
>      In	addition to the	 genders  options  presented  below,  the
>      genders  attribute	 pdsh_rcmd_type	 may  also be used in the
>      genders database to specify an alternate rcmd  connect  type
>      than the pdsh default in the genders file
>
>        host0 pdsh_rcmd_type=ssh
>
>      would cause pdsh to use ssh to connect to host0, even if rsh
>      were the default.	This can be overridden on the commandline
>      with the "rcmd_type:host0"	syntax.
>
>
>      -A	  Target all nodes in genders  database.  The  -A  option
> 	  will target every host listed	in genders -- if you want
> 	  to omit some hosts by	default, see the -a option below.
>
>      -a	  Target all nodes in genders database except those  with
> 	  the  "pdsh_all_skip"	attribute.  This is shorthand for
> 	  running "pdsh	-A -X pdsh_all_skip ..."
>
>      -g	attr[=val][,attr[=val],...]
> 	  Target nodes that match any of  the  specified  genders
> 	  attributes  (with  optional  values).	Conflicts with -a
> 	  and -w options. This option targets the alternate host-
> 	  names	in the genders database	by default. The	-i option
> 	  provided by the genders module may be	used to	translate
> 	  these	 to  the  canonical  genders  hostnames.  If  the
> 	  installed version of genders	supports  it,  attributes
> 	  supplied  to	-g  may	 also  take  the  form of genders
> 	  queries. Genders queries will	query the  genders  data-
> 	  base	for  the union,	intersection, difference, or com-
> 	  plement of genders  attributes  and  values.	 The  set
> 	  operation  union  is	represented  by	 two pipe symbols
> 	  ('||'), intersection by two ampersand	 symbols  ('&&'),
> 	  difference  by two minus symbols ('--'), and complement
> 	  by a tilde ('~').  Parentheses may be	 used  to  change
> 	  the  order  of  operations. See the nodeattr(1) manpage
> 	  for examples of genders queries.
>
>
>
>
> pdsh-2.18	    Last change: solaris2.11			5
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
>      -X	attr[=val][,attr[=val],...]
> 	  Exclude nodes	that match any of the  specified  genders
> 	  attributes  (optionally  with	values).  This option may
> 	  be used in combination  with	any  other  of	the  node
> 	  selection  options  (e.g.  -w, -g, -a, -X may	also take
> 	  the form of genders queries. Please  see  documentation
> 	  for  the  genders  -g	option for more	information about
> 	  genders queries.
>
>      -i	  Request translation  between	canonical  and	alternate
> 	  hostnames.
>
>      -F	filename
> 	  Read genders information from	filename instead  of  the
> 	  system default genders file.
>
>
> nodeupdown module options
>      -v	  Eliminate target nodes that are  considered  "down"  by
> 	  libnodeupdown.
>
>
> slurm module options
>      The slurm module  allows  pdsh  to	 target	 nodes	based  on
>      currently	running	SLURM jobs. The	slurm module is	typically
>      called after all other node selection options have	been pro-
>      cessed,  and if no	nodes have been	selected, the module will
>      attempt  to  read	a  running  jobid  from	 the  SLURM_JOBID
>      environment  variable  (which  is	set  when running under	a
>      SLURM allocation).	If SLURM_JOBID references an invalid job,
>      it	will be	silently ignored.
>
>      -j	jobid[,jobid,...]
> 	  Target list of nodes allocated to the	SLURM job  jobid.
> 	  This option may be used multiple times to target multi-
> 	  ple SLURM jobs. The special argument "all" can be  used
> 	  to target all	nodes running SLURM jobs, e.g.	-j all.
>
>
> rms module options
>      The rms module allows pdsh	to target nodes	based on  an  RMS
>      resource. The rms module is typically called after	all other
>      node selection options, and if no nodes have been	selected,
>      the module	will examine the RMS_RESOURCEID	environment vari-
>      able and attempt to set the target	 list  of  hosts  to  the
>      nodes  in	the  RMS  resource.  If	 an  invalid  resource is
>      denoted, the variable is silently ignored.
>
>
> SDR module options
>      The SDR module supports targeting hosts via the System  Data
>      Repository	on IBM SPs.
>
>
>
> pdsh-2.18	    Last change: solaris2.11			6
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
>      -a	  Target all nodes in the SDR. The list	is generated from
> 	  the "reliable	hostname" in the SDR by	default.
>
>      -i	  Translate hostnames between reliable and initial in the
> 	  SDR, when applicable.	 If the	a target hostname matches
> 	  either the initial or	reliable hostname in the SDR, the
> 	  alternate name will be substitued. Thus a list composed
> 	  of initial hostnames will instead be	replaced  with	a
> 	  list	of  reliable  hostnames.   For example,	when used
> 	  with -a above, all initial hostnames	in  the	 SDR  are
> 	  targeted.
>
>      -v	  Do not target	nodes that are marked as  not  responding
> 	  in  the  SDR	on the targeted	interface. (If a hostname
> 	  does not appear in the SDR, then that	name will  remain
> 	  in the target	hostlist.)
>
>      -G	  In combination with -a, include all partitions.
>
>
> nodeattr module	options
>      The nodeattr module supports access to the	genders	 database
>      via  the  nodeattr(1) command. See	the genders section above
>      for a list	of support options with	this module.  The  option
>      usage  with  the  nodeattr	 module	 is  the same as genders,
>      above, with the exception that the	-i  option  may	 only  be
>      used  with	 -a  or	-g. NOTE: This module will only	work with
>      very old releases of genders where	the  nodeattr(1)  command
>      supports  the  -r	option,	and before the libgenders API was
>      available.	Users running newer versions of	genders	will need
>      to	use the	genders	module instead.
>
>
> dshgroup module	options
>      The dshgroup module allows	pdsh  to  use  dsh  (or	 Dancer's
>      shell)   style   group   files   from   /etc/dsh/group/   or
>      ~/.dsh/group/.
>
>      -g	groupname,...
> 	  Target nodes in dsh group  file  "groupname"	found  in
> 	  either	     ~/.dsh/group/groupname	       or
> 	  /etc/dsh/group/groupname.
>
>      -X	groupname,...
> 	  Exclude nodes	in dsh group file "groupname."
>
>
> netgroup module	options
>      The netgroup module allows	pdsh  to  use  standard	 netgroup
>      entries  to  build	 lists of target hosts.	(/etc/netgroup or
>      NIS)
>
>
>
>
> pdsh-2.18	    Last change: solaris2.11			7
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
>      -g	groupname,...
> 	  Target nodes in netgroup "groupname."
>
>      -X	groupname,...
> 	  Exclude nodes	in netgroup "groupname."
>
>
> ENVIRONMENT VARIABLES
>      PDSH_RCMD_TYPE
> 	  Equivalent to	the -R option, the value of this environ-
> 	  ment	variable  will	be  used  to set the default rcmd
> 	  module for pdsh to use (e.g. ssh, rsh).
>
>      PDSH_SSH_ARGS
> 	  Override the standard	arguments that pdsh passes to the
> 	  ssh(1) command ("-2 -a -x").
>
>      PDSH_SSH_ARGS_APPEND
> 	  Append additional options to the ssh(1) command invoked
> 	  by  pdsh.  For example, PDSH_SSH_ARGS_APPEND="-q" would
> 	  run ssh in quiet mode, or "-v" would increase	the  ver-
> 	  bosity of ssh.
>
>      WCOLL
> 	  If no	other node selection option is	used,  the  WCOLL
> 	  environment  variable	 may  be  set  to a filename from
> 	  which	a list of target hosts will  be	 read.	The  file
> 	  should  contain  a  list of hosts, one per line (though
> 	  each line may	contain	a hostlist expression.	See HOST-
> 	  LIST EXPRESSIONS section below).
>
>      DSHPATH
> 	  If set, the path in DSHPATH will be used  as	the  PATH
> 	  for the remote processes.
>
>      FANOUT
> 	  Set the pdsh fanout (See description of -f above).
>
>
> HOSTLIST EXPRESSIONS
>      As	noted in sections above	pdsh accepts lists of  hosts  the
>      general  form:  prefix[n-m,l-k,...],  where n < m and l < k,
>      etc., as an alternative to	explicit  lists	 of  hosts.  This
>      form  should not be confused with regular expression charac-
>      ter classes (also denoted by ``[]''). For	example,  foo[19]
>      does  not represent an expression matching	foo1 or	foo9, but
>      rather represents the degenerate hostlist:	foo19.
>
>      The hostlist syntax is meant only as a convenience	on  clus-
>      ters  with	a "prefixNNN" naming convention	and specification
>      of	 ranges	 should	 not  be  considered  necessary	 --  this
>      foo1,foo9	could  be  specified  as such, or by the hostlist
>
>
>
> pdsh-2.18	    Last change: solaris2.11			8
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
>      foo[1,9].
>
>      Some examples of usage follow:
>
>
>      Run command on foo01,foo02,...,foo05
> 	 pdsh -w foo[01-05] command
>
>      Run command on foo7,foo9,foo10
> 	 pdsh -w foo[7,9-10] command
>
>      Run command on foo0,foo4,foo5
> 	 pdsh -w foo[0-5] -x foo[1-3] command
>
>
>      A suffix on the hostname is also supported:
>
>
>      Run command on foo0-eth0,foo1-eth0,foo2-eth0,foo3-eth0
> 	pdsh -w	foo[0-3]-eth0 command
>
>
>      As	a reminder to the  reader,  some  shells  will	interpret
>      brackets  ('['  and ']') for pattern matching.  Depending on
>      your shell, it may	be  necessary  to  enclose  ranged  lists
>      within  quotes.   For  example,  in  tcsh,	the first example
>      above should be executed as:
>
> 	 pdsh -w "foo[01-05]" command
>
>
> ORIGIN
>      Originally	 a  rewrite  of	 IBM  dsh(1)   by   Jim	  Garlick
>      <garlick@llnl.gov>	 on  LLNL's ASCI Blue-Pacific IBM SP sys-
>      tem. It is	now used on Linux clusters at LLNL.
>
>
> LIMITATIONS
>      When using	ssh for	remote execution, expect  the  stderr  of
>      ssh  to  be  folded in with that of the remote command. When
>      invoked by	pdsh, it is not	possible for ssh  to  prompt  for
>      passwords	if  RSA/DSA  keys  are configured properly, etc..
>      For ssh implementations  that  suppport  a	 connect  timeout
>      option,  pdsh  attempts  to  use  that option to enforce the
>      timeout (e.g.  -oConnectTimeout=T	for  OpenSSH),	otherwise
>      connect timeouts are not supported	when using ssh.	 Finally,
>      there is no reliable way for pdsh to ensure that remote com-
>      mands  are	actually terminated when using a command timeout.
>      Thus if -u	is used	with ssh commands may be left running  on
>      remote  hosts  even  after	 timeout  has  killed  local  ssh
>      processes.
>
>
>
>
> pdsh-2.18	    Last change: solaris2.11			9
>
>
>
>
>
>
> User Commands						  pdsh(1)
>
>
>
>      Output from multiple processes per	node may be  interspersed
>      when using	qshell or mqshell rcmd modules.
>
>      The number	of nodes that  pdsh  can  simultaneously  execute
>      remote  jobs  on is limited by the	maximum	number of threads
>      that can be created concurrently, as well as the  availabil-
>      ity of reserved ports in the rsh and qshell rcmd modules. On
>      systems that implement Posix threads, the limit is	typically
>      defined by	the constant PTHREADS_THREADS_MAX.
>
>
> FILES
> ATTRIBUTES
>      See attributes(5) for descriptions	of the	following  attri-
>      butes:
>
>
>
>      ____________________________________________________________
>     |	    ATTRIBUTE TYPE	  |	  ATTRIBUTE VALUE	|
>     |_____________________________|_____________________________|
>     | Availability		  | SUNWpdsh			|
>     |_____________________________|_____________________________|
>     | Interface	Stability	  | uncommitted			|
>     |_____________________________|_____________________________|
>
>
> SEE ALSO
>      rsh(1),	     ssh(1),	      dshbak(1),	  pdcp(1)
>      http://sourceforge.net/projects/pdsh/
>
> NOTES
>      Source for	pdsh is	available on http://opensolaris.org
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> pdsh-2.18	    Last change: solaris2.11		       10
>
>
>   
> ------------------------------------------------------------------------
>
> Template Version: @(#)sac_nextcase %I% %G% SMI This information is
Copyright 2009 Sun Microsystems 1. Introduction
>     1.1. Project/Component Working Name:
> 	 pdsh Ver 2.18
>     1.2. Name of Document Author/Supplier:
> 	 Author:  Vivek R. Titarmare
>     1.3  Date of This Document:
> 	 3rd April, 2009
>
> 2. Project Summary
>    2.1 Project Description
>
> 	Parallel command execution for clusters
>
> 4. Technical Description:
>
> 	Pdsh is a high-performance, parallel remote shell utility. It has
built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and can call
SSH externally (though with reduced performance). Pdsh uses a "sliding
window" parallel algorithm to conserve socket resources on the initiating
node and to allow progress to continue while timeouts occur on some
connections.
> 	
> 	Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which runs
commands on a single remote host, pdsh can run multiple remote commands in
parallel. pdsh uses a "sliding window" (or fanout) of threads to conserve
resources on the the initiating host while allowing some connections to time
out. 	
>
> 5. Interfaces 
>
> 	The binary file "pdsh" contains following interface.
>
>    Exported interface                   Classification
Interface type
>    =============================        ==============
==============
>    	usr/bin/dshbak			Uncommitted		binary
>    	usr/bin/pdcp			Uncommitted		binary
>    	usr/bin/pdsh			Uncommitted		binary
>    	usr/bin/rpdcp			Uncommitted		binary
>    	usr/lib/pdsh/xrcmd.so		Uncommitted		shared
library
>    	usr/lib/pdsh/xrcmd.la		Uncommitted		library tool
>    	usr/lib/pdsh/xrcmd.a		Uncommitted		static
library
>    	usr/lib/pdsh/execcmd.so		Uncommitted		shared
library
>    	usr/lib/pdsh/execcmd.la		Uncommitted		library tool
>    	usr/lib/pdsh/execcmd.a		Uncommitted		static
library
>    	
> 	PDSH_RCMD_TYPE			Uncommitted		override
standard argument
> 	PDSH_SSH_ARGS			Uncommitted		override
standard argument
> 	PDSH_SSH_ARGS_APPEND		Uncommitted		override
standard argument
> 	WCOLL				Uncommitted		override
standard argument
> 	DSHPATH				Uncommitted		override
standard argument
> 	FANOUT				Uncommitted		override
standard argument
> 	QSHELL_REMOTE_LD_LIBRARY_PATH	Uncommitted		override
standard argument
> 	QSHELL_REMOTE_LD_PREOPEN	Uncommitted		override
standard argument
> 	
>
>    Imported interface        Classification   Comments
>    =======================   ==============
=================================== 
> 	None
>
>    The binary file would go in "usr/bin" and the libraries would go in
"usr/lib"
>
>
> 6. Resources and Schedule
>     6.4. Steering Committee requested information
>    	6.4.1. Consolidation C-team Name:
> 		SFW
>     6.5. ARC review type: FastTrack
>     6.6. ARC Exposure: open
> ------------------------------------------------------------------------
>
> FCL--FOSS Check List
>
> 1.0 Project Information
> 1.1 Name of project/component
> 	pdsh  Ver 2.18
>
> 1.2 Author of document
> 	Vivek R. Titarmare
>
> 2.0 Project Summary
>   2.1 Project Description
>
> 	Pdsh is a high-performance, parallel remote shell utility. It has
built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and can call
SSH externally (though with reduced performance). Pdsh uses a "sliding
window" parallel algorithm to conserve socket resources on the initiating
node and to allow progress to continue while timeouts occur on some
connections.
> 	
> 	Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which runs
commands on a single remote host, pdsh can run multiple remote commands in
parallel. pdsh uses a "sliding window" (or fanout) of threads to conserve
resources on the the initiating host while allowing some connections to time
out. 	
>
> 	Pdsh is a an efficient, multithreaded remote shell client which
executes commands on multiple remote hosts in parallel. Pdsh implements
dynamically loadable modules for extended functionality such as new remote
shell services and remote host selection
>
>   2.2 Release binding
>       What is is the release binding?
>       (see
http://opensolaris.org/os/community/arc/policies/release-taxonomy/)
>       [ ] Major
>       [X] Minor
>       [ ] Patch or Micro
>       [ ] Unknown -- ARC review required
>
>   2.3 Type of project
>       Is this case a Linux Familiarity project?
>       [X] Yes
>       [ ] No
>
>   2.4 Originating Community
>     2.4.1 Community Name
> 	    PDSH (http://sourceforge.net/projects/pdsh/)
>     
>     2.4.2 Community Involvement
>       Indicate Sun's involvement in the community
>       [ ] Maintainer
>       [ ] Contributor
>       [X] Monitoring
>       
>       Will the project team work with the upstream community to resolve
>       architectural issues of interest to Sun?
>       [X] Yes 
>       [ ] No - briefly explain
>       
> 	
>       Will we or are we forking from the community?
>       [ ] Yes - ARC review required prior to forking
>       [X] No
>       
> 3.0 Technical Description
>   3.1 Installation & Sharable
>     3.1.1S Solaris Installation - section only required for Solaris
Software
>       (see
http://opensolaris.org/os/community/arc/policies/install-locations/ for
details)
>       Does this project follow the Install Locations best practice?
>       [X] Yes 
>       [ ] No - ARC review required
>       
>       Does this project install into /usr under
[sbin|bin|lib|include|man|share]?
>       [X] Yes
>       [ ] No or N/A
>       
>       Does this project install into /opt?
>       [ ] Yes - explain below
>       [X] No or N/A
>       
>       Does this project install into a different directory structure?
>       [ ] Yes - ARC review required
>       [X] No or N/A
>       
>       Do any of the components of this project conflict with anything
under /usr?
>       (see http://opensolaris.org/os/community/arc/caselog/2007/047/ for
details)
>       [ ] Yes - explain below
>       [X] No
>       
>       If conflicts exist then will this project install under /usr/gnu?
>       [ ] Yes
>       [ ] No - ARC review required
>       [X] N/A
>       
>       Is this project installing into /usr/sfw?
>       [ ] Yes - ARC review required
>       [X] No
>       
>     3.1.1W Windows Installation - section only required for Windows
Software
>       (see http://sac.sfbay/WSARC/2002/494 for details)
>       Does this project install software into a 
>       <system drive>:\Program Files\Sun\<product> or <system
drive>:\Sun\<product>
>       directory?
>       [ ] Yes
>       [ ] No - ARC review required
>       
>       Does the project use the Windows registry?
>       [ ] Yes
>       [ ] No - ARC review required
>       
>       Does the project use 
>       HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\<product>\<version>
>       for the registry key?
>       [ ] Yes
>       [ ] No - ARC review required
>       
>       Is the project's stored location
>       HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\<product id>\<version
id>\Path?
>       [ ] Yes
>       [ ] No - ARC review required
>       
>     3.1.2 Share and Sharable
>       Does the module include any components that are used or shared by 
>       other projects?
>       [X] Yes
>       [ ] No
>     
>       If yes are these components packaged to be shared with the other
FOSS?
>       [X] Yes
>       [ ] No - ARC review required
>       [ ] N/A
>     
>       Are these components already in the Solaris WOS?
>       [X] Yes
>       [ ] No - continue with next section (section 3.2)
>     
>       If yes are these newer versions being delivered?
>       [X] Yes
>       [ ] No - ARC review required
>       
>       If yes are the newer versions replacing the existing versions?
>       [X] Yes
>       [ ] No - ARC review required
>
>   3.2 Exported Libraries
>       Are libraries being delivered by this project?
>       [ ] Yes
>       [X] No - continue with next section (section 3.3)
>       
>       Are 64-bit versions of the libraries being delivered?
>       [ ] Yes
>       [ ] No - ARC review required
>     
>       Are static versions of the libraries being delivered?
>       [ ] Yes - ARC review required
>       [ ] No 
>       
>   3.3 Services and the /etc Directory
>       (see http://opensolaris.org/os/community/arc/policies/SMF-policy/)
>       Does the project integrate anything into /etc/init.d or /etc/rc?.d?
>       [ ] Yes - ARC review required
>       [X] No
>       
>       Does the project integrate any new entries into /etc/inittab or
>       /etc/inetd.conf?
>       [ ] Yes - ARC review required
>       [X] No
>       
>       Does the project integrate any private non-public files into
/etc/default
>       or /etc/ configuration files?
>       [ ] Yes - ARC review required
>       [X] No
>       
>       Does the service manifests method context grant rights above that
>       of the noaccess user and basic privilege set?
>       [ ] Yes - ARC review required
>       [X] No
>         
>   3.4 Security
>     3.4.1 Secure By Default 
>       (see
http://opensolaris.org/os/community/arc/policies/secure-by-default/ for
details)
>       (see
http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for
details)
>       (see parts of
http://opensolaris.org/os/community/arc/policies/SMF-policy/ for
>        addtional details)
>       Are there any network services provided by this project?
>       [ ] Yes
>       [X] No - continue with the next section (section 3.4.2)
>       
>       Are network services enabled by default?
>       [ ] Yes - ARC review required
>       [ ] No
>       [X] N/A
>       
>       Are network services automatically enabled by the project during
installation?
>       [ ] Yes - ARC review required
>       [ ] No
>       [X] N/A
>       
>       Are inbound network communications denied by default?
>       [ ] Yes
>       [ ] No - ARC review required
>       [X] N/A
>       
>       Is inbound data checked to prevent content-based attacks?
>       [ ] Yes
>       [ ] No - ARC review required
>       [X] N/A
>       
>       Is the outbound receiver authenticated?
>       [ ] Yes
>       [ ] No - ARC review required
>       [X] N/A
>       
>       Is the receiver authenticated prior to receiving any sensitive
outbound communication?
>       [ ] Yes
>       [ ] No - ARC review required
>       [X] N/A
>       
>     3.4.2 Authorization
>       (see
http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and
>
http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and
>
http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/
>            for details)
>       Are there any setuid/setgid privileged binaries in the project?
>       [ ] Yes - ARC review required
>       [X] No - continue with next section (section 3.4.3)
>       
>       If yes then are the setuid/setgid privileges handled by the use of
roles?
>       [ ] Yes
>       [ ] No - ARC review required
>
>     3.4.3 Auditing
>       (see http://opensolaris.org/os/community/arc/policies/audit-policy/
for details)
>       (see http://opensolaris.org/os/community/arc/caselog/2003/397 for
details)
>       Does this component contain administrative or security enforcing
software?
>       [ ] Yes - ARC review required
>       [X] No - continue to next section (section 3.4.4)
>       
>       (see http://opensolaris.org/os/community/arc/caselog/2003/397 for
details)
>       Do the components create audit logs detailing what took place
including what event
>       took place, who was involved, when the event took place?
>       [ ] Yes - ARC contract and Audit project team review required
>       [ ] No - ARC review required
>         
>         
>     3.4.4 Authentication
>       (see http://opensolaris.org/os/community/arc/policies/PAM/)
>       Do the components contain any authentication code?
>       [ ] Yes
>       [X] No - continue to next section (section 3.4.5)
>       
>       If yes do the components use PAM (plugable authentication modules)
for authentication?
>       [ ] Yes
>       [ ] No - ARC review required
>       
>       If yes is a single PAM session maintained during authentication?
>       [ ] Yes
>       [ ] No - ARC review required
>       
>       If yes are the components sufficiently privileged to allow the
requested 
>       operations (authentication, password change, process credential
manipulation, 
>       audit state initialization)?
>       [ ] Yes - briefly describe below
>       [ ] No - ARC review required
>       
>     3.4.5 Passwords
>       (see
http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and
>
http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ for
details)
>       Do any of the components for the project deal with passwords?
>       [ ] Yes
>       [X] No - continue to next section (section 3.4.6)
>       
>       If yes are these passwords entered via the CLI or environment?
>       [ ] Yes - ARC review required
>       [ ] No
>       
>       Are passwords stored within the file system for the component?
>       [ ] Yes
>       [ ] No - continue to next section (section 3.4.6)
>       
>       If yes are the permissions on the file such to protect exposing the
password(s)?
>       [ ] Yes
>       [ ] No - ARC review required
>       
>     3.4.6 General Security Questions
>       (see
http://opensolaris.org/os/community/arc/bestpractices/security-questions/
for details)
>       Are there any network protocols used by this project?
>       [X] Yes
>       [ ] No - continue with the next section (section 3.5)
>       
>       Do the components use standard network protocols?
>       [X] Yes
>       [ ] No - ARC review required
>       
>       Do network services for the project make decisions based upon user,
host or 
>       service identities?
>       [X] Yes - explain below
>       [ ] No
>       [ ] N/A
>       
>       	pdsh makes decision on network services based upon service
identities. pdsh is a variant of the rsh(1) command. The core functionality
of pdsh may be supplemented by dynamically loadable modules. The modules may
provide a new connection protocol (replacing the standard rcmd(3) protocol
used by rsh(1)), filtering options (e.g. removing hosts that are "down" from
the target list), and/or host selection options (e.g., -a selects all hosts
from a configuration file.).Pdsh modules come in two flavors at this time:
rcmd and miscellaneous. 
>       		
>       	The rcmd modules provide remote command functionality for
pdsh. A list of rcmd modules currently distributed with pdsh follows. 
>       		rsh Uses an internal, thread-safe implementation of
BSD rcmd(3) to run commands using the standard rsh(1) protocol. 
>       		ssh Uses a variant of popen(3) to run multiple
copies of the ssh(1) command. 
>       		mrsh This module uses the mrsh(1) protocol to
execute jobs on remote hosts. The mrsh protocol uses a credential based
authentication, forgoing the need to allocate reserved ports. In other
aspects, it acts just like rsh. Remote nodes must be running mrshd(8) in
order for the mrsh module to work. 
>                	qsh  Allows pdsh to execute MPI jobs over QsNet.
Qshell propagates the current working directory, pdsh environment, and Elan
capabilities to the remote process. The following environment variable are
also appended to the environment: RMS_RANK, RMS_NODEID, RMS_PROCID,
RMS_NNODES, and RMS_NPROCS. 
>         Since pdsh needs to run setuid root for qshell support, qshell
does not directly support propagation of LD_LIBRARY_PATH and LD_PREOPEN.
Instead the QSHELL_REMOTE_LD_LIBRARY_PATH and QSHELL_REMOTE_LD_PREOPEN
environment variables will may be used and will be remapped to
LD_LIBRARY_PATH and LD_PREOPEN by the qshell daemon if set. 
>                 mqsh Similar to qshell, but uses the mrsh protocol instead
of the rsh protocol. 
>                 krb4 The krb4 module allows users to execute remote
commands after authenticating with kerberos. Of course, the remote rshd
daemons must be kerberized. 
>                 xcpu The xcpu module uses the xcpu service to execute
remote commands
>       
>       Do the components make use of secret information during
authentication and/or
>       authorization?
>       [ ] Yes - explain below
>       [X] No
>       [ ] N/A
>   
>   3.5 Networking
>       Do the components access the network?
>       [X] Yes
>       [ ] No - continue with the next section (section 3.6)
>       
>       If yes do the components support IPv6?
>       [X] Yes 
>       [ ] No - ARC review required
>           
>   3.6 Core Solaris Components
>       Do the components of this project compete with or duplicate core 
>       Solaris components?
>       [ ] Yes - ARC review required
>       [X] No 
>              
> 4.0 Interfaces
>   (see
http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ for
details)
>   4.1 Exported Interfaces
>   
>     The binary file "pdsh" contains following interface.
>
>     Interface Name			Classification
Comments
>     ---------------------------     -------------------
---------------------------
>    	usr/bin/dshbak			Uncommitted		binary
>    	usr/bin/pdcp			Uncommitted		binary
>    	usr/bin/pdsh			Uncommitted		binary
>    	usr/bin/rpdcp			Uncommitted		binary
>    	usr/lib/pdsh/xrcmd.so		Uncommitted		shared
library
>    	usr/lib/pdsh/xrcmd.la		Uncommitted		library tool
>    	usr/lib/pdsh/xrcmd.a		Uncommitted		static
library
>    	usr/lib/pdsh/execcmd.so		Uncommitted		shared
library
>    	usr/lib/pdsh/execcmd.la		Uncommitted		library tool
>    	usr/lib/pdsh/execcmd.a		Uncommitted		static
library
>    	
> 	PDSH_RCMD_TYPE			Uncommitted		override
standard argument
> 	PDSH_SSH_ARGS			Uncommitted		override
standard argument
> 	PDSH_SSH_ARGS_APPEND		Uncommitted		override
standard argument
> 	WCOLL				Uncommitted		override
standard argument
> 	DSHPATH				Uncommitted		override
standard argument
> 	FANOUT				Uncommitted		override
standard argument
> 	QSHELL_REMOTE_LD_LIBRARY_PATH	Uncommitted		override
standard argument
> 	QSHELL_REMOTE_LD_PREOPEN	Uncommitted		override
standard argument
> 	
>
>   4.2 Imported Interfaces
>     Interface Name		Classification       Comments
>     --------------------------- --------------------
--------------------------
> 	None    
>
> The binary file would go in "/usr/bin" and the libraries would go in
"/usr/lib"
>
> Appendix B - Suggested case materials
>   1. man pages
>
>      Attached are the man pages (pdsh.1, pdcp.1, dshbak.1)
>
>   2. SMF manifests
>   3. links to contracts
>   



From Mark.Carlson@Sun.COM Tue Apr 28 09:15:53 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3SGFqZf006231
	for <LSARC-ext@sac.sfbay.sun.com>; Tue, 28 Apr 2009 09:15:52 -0700 (PDT)
Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3SGFo6e002784
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Tue, 28 Apr 2009 17:15:50 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by
 nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KIT0000VJUDRU00@nwk-avmta-1.sfbay.Sun.COM> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 28 Apr 2009 09:15:49 -0700 (PDT)
Received: from brmea-mail-1.sun.com ([192.18.98.31])
 by nwk-avmta-1.sfbay.Sun.COM
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KIT0088LJUBHUB0@nwk-avmta-1.sfbay.Sun.COM> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@sun.com); Tue,
 28 Apr 2009 09:15:48 -0700 (PDT)
Received: from fe-amer-09.sun.com ([192.18.109.79])
	by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3SGFlNX027136	for
 <LSARC-ext@sun.com>; Tue, 28 Apr 2009 16:15:47 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KIT00M00J5TDC00@mail-amer.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@sun.com); Tue, 28 Apr 2009 10:15:47 -0600 (MDT)
Received: from Macintosh-335.local ([unknown] [129.150.36.215])
 by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 with ESMTPSA id <0KIT00BBVJTT2G60@mail-amer.sun.com>; Tue,
 28 Apr 2009 10:15:30 -0600 (MDT)
Date: Tue, 28 Apr 2009 10:15:28 -0600
From: "Mark A. Carlson" <Mark.Carlson@Sun.COM>
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <49EF480E.4070106@sun.com>
Sender: Mark.Carlson@Sun.COM
To: Margot Miller <Margot.Miller@Sun.COM>
Cc: Vivek Titarmare <Vivek.Titarmare@Sun.COM>, LSARC-ext@Sun.COM
Message-id: <49F72BA0.80109@sun.com>
MIME-version: 1.0
Content-type: multipart/alternative;
 boundary="Boundary_(ID_c23GdocVnywPtkpBCToWGw)"
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
 <20090413205436.GX7978@mumak.SFBay.Sun.COM>
 <003001c9bd02$8997a1d0$9cc6e570$%Titarmare@Sun.com>
 <20090414150713.GA7978@mumak.SFBay.Sun.COM>
 <013801c9c2a4$e270fb10$a752f130$%Titarmare@Sun.com>
 <20090421180905.GF4425@mumak.SFBay.Sun.COM>
 <024601c9c34b$7b459110$71d0b330$%Titarmare@Sun.com> <49EF480E.4070106@sun.com>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
Status: RO
Content-Length: 181131

This is a multi-part message in MIME format.

--Boundary_(ID_c23GdocVnywPtkpBCToWGw)
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

The case directory has been updated with new materials.

Any last issues before I close this case?

-- mark

Margot Miller wrote:
> Vivek,
>
> Please add the package SUNWpdsh to the interface table.
>
> In the pdsh man page, it has:
>
>     qsh     Allows pdsh to execute MPI    jobs over  QsNet.  Qshell
>          propagates      the  current    working     directory,  pdsh
>          environment, and Elan  capabilities  to  the  remote
>          process. The following environment    variable are also
>          appended to the environment:  RMS_RANK,  RMS_NODEID,
>          RMS_PROCID,  RMS_NNODES,  and RMS_NPROCS. Since pdsh
>          needs to run setuid root for qshell support,  qshell
>          does    not    directly   support     propagation   of
>          LD_LIBRARY_PATH   and   LD_PREOPEN.   Instead    the
>          QSHELL_REMOTE_LD_LIBRARY_PATH              and
>          QSHELL_REMOTE_LD_PREOPEN environment variables  will
>          may  be used and will be remapped to LD_LIBRARY_PATH
>          and LD_PREOPEN by the qshell daemon if set.
>
> Does this project support Qshell? 
> Also, there is a section in one of the man pages about slurm
> module options.  Per Danek in the below email, this is not
> relevant for Solaris.  The documentation needs to be updated
> to reflect that this isn't supported on Solaris.
>
> Please check through all the man pages to ensure that everything
> in the man pages is correct wrt Solaris and what is in the man pages
> is reflected in the interface table.
>
> Also, please have your sponsor review all the materials
> before you resend the updated documents.
>
> Thanks
> Margot
>
>
>
>
> Vivek Titarmare wrote:
>> Hi Danek and the team,
>>
>> I have updated the Fasttrack and FOSS check list for pdsh. Major 
>> changes in
>> the interface tables would be seen. Actually a rework was done on this
>> package and found that the interface table needed a change.
>> Pl. ignore the previous Interface related conflicts.
>>
>> Let me know if this looks good to go.
>>
>> Pl. find attached all the files required for this ARC review.
>>
>> Thanks,
>> ~Vivek R. Titarmare
>>
>>
>>
>> -----Original Message-----
>> From: Danek Duvall [mailto:Danek.Duvall@Sun.COM] Sent: Tuesday, April 
>> 21, 2009 11:39 PM
>> To: Vivek Titarmare
>> Cc: 'Mark Carlson'; James.D.Carlson@Sun.COM; Nicolas.Williams@Sun.COM;
>> Manisha.Jha@Sun.COM
>> Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
>>
>> [ Please use standard email quoting techniques -- a "> " prefix to every
>> line that you're responding to, and not to your own; what you're doing
>> makes your email responses incredibly difficult to read.  Perhaps not 
>> using
>> Outlook would help.  This is Sun, after all; you should be running 
>> Solaris.
>> ]
>>
>> On Tue, Apr 21, 2009 at 10:46:14PM +0530, Vivek Titarmare wrote:
>>
>>  
>>>> No, I want you to not deliver those interfaces.  You can't ship
>>>>       
>> components
>>  
>>>> that don't work.  This is a commercial OS, not a grad student project,
>>>>       
>> and
>>  
>>>> it costs Sun tons of money to field calls from customers complaining
>>>>       
>> about
>>  
>>>> things that don't work.  It's best not to ship them at all if we know
>>>> they're busted.  Given how much of the man page is filled with text
>>>> describing options and arguments that won't be useful on Solaris, 
>>>> you'll
>>>> need to remove this extraneous documentation before delivery, too.
>>>>       
>>> [VIVEK] I am sorry, I think I confused you. All the components work, 
>>> for
>>> those components to work we need to override the environment variables
>>>     
>> which
>>  
>>> I am adding those in the Interface table. I this case, do we still 
>>> need to
>>> remove the contents from the man pages. Pl. let me know.
>>>     
>>
>> The components that are unavailable (libgenders, nodeattr, etc) will 
>> cause
>> portions of pdsh (pdsh-mod-genders, pdsh-mod-nodeattr, etc) not to work,
>> environment variables or not.  There is no way that "pdsh-mod-slurm" is
>> going to work unless slurm is installed, and since there is no slurm
>> available for Solaris, then "pdsh-mod-slurm" is not going to work on
>> Solaris.  So don't ship it, and don't document it.
>>
>> Danek
>> ------------------------------------------------------------------------
>>
>>
>>
>>
>> DSHBAK                            DSHBAK(1)
>>
>>
>>
>> NAME
>>      dshbak - format output from pdsh command
>>
>> SYNOPSIS
>>      dshbak [-c]
>>
>> DESCRIPTION
>>      dshbak formats pdsh output    for  humans.   Output  from  each
>>      node  is consolidated, the    leading    node: prefix is    
>> stripped,
>>      and a header block    with the node name is added.  If  the  -c
>>      option  is     specified,  nodes  with identical output are not
>>      displayed twice; instead, the header will contain a list  of
>>      nodes.   The  list     of nodes is further compressed    into node
>>      ranges if the node    names have a numeric suffix.
>>
>>
>> ORIGIN
>>      A rewrite of IBM dshbak(1)    by Jim Garlick
>>      <garlick@llnl.gov>    on LLNL's ASCI Blue-Pacific IBM     SP  sys-
>>      tem.
>>
>>
>> ATTRIBUTES
>>      See attributes(5) for descriptions    of the    following  attri-
>>      butes:
>>
>>
>>
>>      ____________________________________________________________
>>     |        ATTRIBUTE TYPE      |      ATTRIBUTE VALUE    |
>>     |_____________________________|_____________________________|
>>     | Availability          | SUNWpdsh            |
>>     |_____________________________|_____________________________|
>>     | Interface    Stability      | uncommitted            |
>>     |_____________________________|_____________________________|
>>
>>
>> SEE ALSO
>>      pdsh(1)
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> LLNL            Last change: Release 1.3            1
>>
>>
>>   
>> ------------------------------------------------------------------------
>>
>>
>>
>>
>> User Commands                          pdsh(1)
>>
>>
>>
>> NAME
>>      pdcp - copy files to groups of hosts in parallel
>>      rpdcp - (reverse pdcp) copy files from a group of    hosts  in
>>      parallel
>>
>>
>> SYNOPSIS
>>      pdcp [options]... src [src2...] dest
>>      rpdcp [options]...    src [src2...] dir
>>
>>
>> DESCRIPTION
>>      pdcp is a variant of the  rcp(1)  command.      Unlike  rcp(1),
>>      which  copies  files  to a    single remote host, pdcp can copy
>>      files to multiple remote hosts in parallel.   However,  pdcp
>>      does not recognize    files in the format ``rname@rhost:path,''
>>      therefore all  source  files  must     be  on     the  local  host
>>      machine.    Destination nodes must be listed on the    pdcp com-
>>      mand line using a suitable    target nodelist    option    (See  
>> the
>>      OPTIONS  section  below).    Each destination node listed must
>>      have pdcp installed for the copy to succeed.
>>
>>      When pdcp receives    SIGINT (ctrl-C), it lists the  status  of
>>      current  threads.     A  second  SIGINT within one second ter-
>>      minates the program. Pending  threads  may     be  canceled  by
>>      issuing ctrl-Z within one second of ctrl-C.  Pending threads
>>      are those that have not yet been initiated, or are    still  in
>>      the process of connecting to the remote host.
>>
>>      Like pdsh(1), the functionality of    pdcp may be  supplemented
>>      by     dynamically  loadable    modules. In pdcp, the modules may
>>      provide a    new  connect  protocol    (replacing  the     standard
>>      rsh(1)  protocol),     filtering  options (e.g. excluding hosts
>>      that are down),  and/or  host  selection  options    (e.g.  -a
>>      selects  all  nodes  from a local config file).  By default,
>>      pdcp requires at least one    "rcmd" module to  be  loaded  (to
>>      provide the channel for remote copy).
>>
>>
>> REVERSE    PDCP
>>      rpdcp performs a reverse parallel copy.  Rather than copying
>>      files to remote hosts, files are retrieved    from remote hosts
>>      and stored    locally.  All directories or files retrieved will
>>      be     stored     with  their  remote  hostname    appended  to  
>> the
>>      filename.    The destination    file must  be  a  directory  when
>>      this option is used.
>>
>>      In    other respects,    rpdcp is exactly like pdcp,  and  further
>>      statements     regarding  pdcp  in  this  manual  also apply to
>>      rpdcp.
>>
>>
>>
>>
>>
>> pdsh-2.18        Last change: solaris2.11            1
>>
>>
>>
>>
>>
>>
>> User Commands                          pdsh(1)
>>
>>
>>
>> RCMD MODULES
>>      The method    by which pdcp connects to  remote  hosts  may  be
>>      selected at runtime using the -R option (See OPTIONS below).
>>      This functionality    is ultimately implemented via dynamically
>>      loadable  modules,     and so    the list of available options may
>>      be    different from installation to installation.  A     list  of
>>      currently    available  rcmd    modules    is printed when    
>> using any
>>      of    the -h,    -V, or -L options. The default rcmd  module  will
>>      also be displayed with the    -h and -V options.
>>
>>      A list of rcmd modules currently distributed with pdcp  fol-
>>      lows.
>>
>>      rsh     Uses an internal, thread-safe implementation of  BSD
>>          rcmd(3)  to  run  commands    using the standard rsh(1)
>>          protocol.
>>
>>      ssh     Uses a variant of popen(3)    to run multiple    copies of
>>          the ssh(1)    command.
>>
>>      mrsh    This module uses the  mrsh(1)  protocol  to  execute
>>          jobs  on  remote  hosts.    The  mrsh protocol uses    a
>>          credential    based authentication, forgoing    the  need
>>          to     allocate  reserved  ports.  In    other aspects, it
>>          acts just like rsh.
>>
>>      krb4    The krb4 module allows users to execute remote  com-
>>          mands after authenticating    with kerberos. Of course,
>>          the remote    rshd daemons must be kerberized.
>>
>>      xcpu    The xcpu module uses the  xcpu  service  to  execute
>>          remote commands.
>>
>>
>> OPTIONS
>>      The list of available pdcp    options    is determined at  runtime
>>      by     supplementing the list    of standard pdcp options with any
>>      options provided by loaded    rcmd and misc modules.     In  some
>>      cases,  options  provided    by modules may conflict    with each
>>      other. In these cases, the    modules    are incompatible and  the
>>      first module loaded wins.
>>
>>
>> Standard target    nodelist options
>>      -w    host,host,...
>>       Target the specified list of hosts. Do not use with any
>>       other     node  selection options (e.g. -a, -g if they are
>>       available).  No  spaces  are    allowed     in  the   comma-
>>       separated  list.   A    list  consisting  of a single `-'
>>       character causes the    target    hosts  to  be  read  from
>>       stdin, one per line. The host    list may contain hostlist
>>       expressions  of  the    form  ``host[1-5,7]''.    For  more
>>
>>
>>
>> pdsh-2.18        Last change: solaris2.11            2
>>
>>
>>
>>
>>
>>
>> User Commands                          pdsh(1)
>>
>>
>>
>>       information about the    hostlist format, see the HOSTLIST
>>       EXPRESSIONS section below.
>>
>>      -x    host,host,...
>>       Exclude the specified    hosts. May be specified     in  con-
>>       junction with    other target node list options such as -a
>>       and -g (when available). Hostlists may also  be  speci-
>>       fied    to the -x option (see HOSTLIST EXPRESSIONS secion
>>       below).
>>
>>
>> Standard pdcp options
>>      -h      Output usage menu and    quit. A    list  of  available  
>> rcmd
>>       modules  will     be  printed at    the end    of the usage mes-
>>       sage.
>>
>>      -q      List option values and the  target  nodelist    and  exit
>>       without action.
>>
>>      -b      Disable ctrl-C status    feature    so that    a  
>> single  ctrl-C
>>       kills    parallel copy. (Batch Mode)
>>
>>      -r      Copy directories recursively.
>>
>>      -p      Preserve modification    time and modes.
>>
>>      -e    PATH
>>       Explicitly specify path to remote pdcp  binary  instead
>>       of using the locally executed    path.
>>
>>      -l    user
>>       This option may be used to copy files    as another  user,
>>       subject  to authorization. For BSD rcmd, this    means the
>>       invoking user    and system must    be listed in  the  user's
>>       .rhosts file (even for root).
>>
>>      -t    seconds
>>       Set the connect timeout. Default is 10 seconds.
>>
>>      -f    number
>>       Set the maximum number of simultaneous remote    copies to
>>       number.  The default is 32.
>>
>>      -R    name
>>       Set rcmd module to name. This    option may  also  be  set
>>       via  the PDSH_RCMD_TYPE environment variable.    A list of
>>       available rcmd modules may be    obtained via  either  the
>>       -h or    -L options.
>>
>>      -R    name
>>       Set rcmd module to name. This    option may  also  be  set
>>       via  the PDSH_RCMD_TYPE environment variable.    A list of
>>
>>
>>
>> pdsh-2.18        Last change: solaris2.11            3
>>
>>
>>
>>
>>
>>
>> User Commands                          pdsh(1)
>>
>>
>>
>>       available rcmd modules may be    obtained via  either  the
>>       -h or    -L options.
>>
>>      -L      List info on all loaded pdcp modules and quit.
>>
>>      -d      Include more complete     thread     status     when  
>> SIGINT  is
>>       received,  and display connect and command time statis-
>>       tics on stderr when done.
>>
>>      -V      Output pdcp version information,  along  with     list  of
>>       currently loaded modules, and    exit.
>>
>>
>>
>> HOSTLIST EXPRESSIONS
>>      As    noted in sections above, pdcp accepts ranges of    hostnames
>>      in     the general form: prefix[n-m,l-k,...],    where n    < m 
>> and    l
>>      < k, etc.,    as an alternative to  explicit    lists  of  hosts.
>>      This  form     should     not  be confused with regular expression
>>      character classes (also denoted  by  ``[]'').  For     example,
>>      foo[19]   does  not  represent  foo1  or  foo9,  but  rather
>>      represents    a degenerate range: foo19.
>>
>>      This range    syntax is meant    only as    a convenience on 
>> clusters
>>      with  a  prefixNN    naming    convention  and     specification of
>>      ranges should  not     be  considered     necessary  --    the  
>> list
>>      foo1,foo9    could  be  specified  as  such,     or  by    the 
>> range
>>      foo[1,9].
>>
>>      Some examples of range usage follow:
>>
>>
>>      Copy /etc/hosts to    foo01,foo02,...,foo05
>>      pdcp -w foo[01-05] /etc/hosts /etc
>>
>>      Copy /etc/hosts to    foo7,foo9,foo10
>>      pdcp -w foo[7,9-10] /etc/hosts    /etc
>>
>>      Copy /etc/hosts to    foo0,foo4,foo5
>>       pdcp -w foo[0-5] -x foo[1-3] /etc/hosts /etc
>>
>>
>>      As    a reminder to the  reader,  some  shells  will    interpret
>>      brackets  ('['  and ']') for pattern matching.  Depending on
>>      your shell, it may    be  necessary  to  enclose  ranged  lists
>>      within  quotes.   For  example,  in  tcsh,    the first example
>>      above should be executed as:
>>
>>      pdcp -w "foo[01-05]" /etc/hosts /etc
>>
>>
>>
>>
>>
>>
>> pdsh-2.18        Last change: solaris2.11            4
>>
>>
>>
>>
>>
>>
>> User Commands                          pdsh(1)
>>
>>
>>
>> ORIGIN
>>      Pdsh/pdcp was originally a    rewrite    of IBM dsh(1) by Jim Gar-
>>      lick  <garlick@llnl.gov>  on LLNL's ASCI Blue-Pacific IBM SP
>>      system.  It is now    also used on Linux clusters at LLNL.
>>
>>
>> LIMITATIONS
>>      When using    ssh for    remote execution, stderr  of  ssh  to  be
>>      folded  in    with that of the remote    command.  When invoked by
>>      pdcp, it is not possible for ssh to prompt    for  confirmation
>>      if     a host    key changes, prompt for    passwords if RSA 
>> keys are
>>      not configured properly, etc..  Finally, the connect timeout
>>      is     only  adjustable with ssh when    the underlying ssh imple-
>>      mentation supports    it, and    pdsh has been built  to     
>> use  the
>>      correct option.
>>
>>
>> ATTRIBUTES
>>      See attributes(5) for descriptions    of the    following  attri-
>>      butes:
>>
>>
>>
>>      ____________________________________________________________
>>     |        ATTRIBUTE TYPE      |      ATTRIBUTE VALUE    |
>>     |_____________________________|_____________________________|
>>     | Availability          | SUNWpdsh            |
>>     |_____________________________|_____________________________|
>>     | Interface    Stability      | uncommitted            |
>>     |_____________________________|_____________________________|
>>
>>
>> SEE ALSO
>>      pdsh(1)
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> pdsh-2.18        Last change: solaris2.11            5
>>
>>
>>   
>> ------------------------------------------------------------------------
>>
>>
>>
>>
>> User Commands                          pdsh(1)
>>
>>
>>
>> NAME
>>      pdsh - issue commands to groups of    hosts in parallel
>>
>>
>> SYNOPSIS
>>      pdsh [options]... command
>>
>>
>> DESCRIPTION
>>      pdsh is a variant of  the    rsh(1)    command.  Unlike  rsh(1),
>>      which  runs  commands  on a single    remote host, pdsh can run
>>      multiple remote commands in parallel. pdsh    uses  a     "sliding
>>      window"  (or fanout) of threads to    conserve resources on the
>>      initiating    host while allowing some connections to    time out.
>>
>>      When pdsh receives    SIGINT (ctrl-C), it lists the  status  of
>>      current  threads.    A  second  SIGINT  within one second ter-
>>      minates the program. Pending  threads  may     be  canceled  by
>>      issuing ctrl-Z within one second of ctrl-C.  Pending threads
>>      are those that have not yet been initiated, or are    still  in
>>      the process of connecting to the remote host.
>>
>>
>>      If    a remote command is not    specified on  the  command  line,
>>      pdsh  runs    interactively, prompting for commands and execut-
>>      ing them when terminated with a carriage return. In interac-
>>      tive  mode,  target nodes that time out on    the first command
>>      are not contacted for subsequent commands,    and commands pre-
>>      fixed  with  an  exclamation  point  will be executed on the
>>      local system.
>>
>>      The core functionality of pdsh may    be supplemented    by dynam-
>>      ically  loadable modules. The modules may provide a new con-
>>      nection protocol (replacing the  standard    rcmd(3)     protocol
>>      used by rsh(1)), filtering    options    (e.g. removing hosts that
>>      are "down"    from the  target  list),  and/or  host    selection
>>      options  (e.g.,  -a  selects  all hosts from a configuration
>>      file.). By    default, pdsh  must  have  at  least  one  "rcmd"
>>      module  loaded. See the RCMD MODULES section for more infor-
>>      mation.
>>
>>
>> RCMD MODULES
>>      The method    by which pdsh runs commands on remote  hosts  may
>>      be     selected  at  runtime    using  the -R option (See OPTIONS
>>      below).  This functionality is  ultimately     implemented  via
>>      dynamically  loadable  modules, and so the    list of    available
>>      options may be different from installation    to  installation.
>>      A    list  of currently available rcmd modules is printed when
>>      using any of the -h, -V, or -L  options.  The  default  rcmd
>>      module will also be displayed with    the -h and -V options.
>>
>>
>>
>>
>> pdsh-2.18        Last change: solaris2.11            1
>>
>>
>>
>>
>>
>>
>> User Commands                          pdsh(1)
>>
>>
>>
>>      A list of rcmd modules currently distributed with pdsh  fol-
>>      lows.
>>
>>      rsh     Uses an internal, thread-safe implementation of  BSD
>>          rcmd(3)  to  run  commands    using the standard rsh(1)
>>          protocol.
>>
>>      exec    Executes an arbitrary command for each target  host.
>>          The  first    of the pdsh remote arguments is    the local
>>          command to    execute, followed by  any  further  argu-
>>          ments.  Some simple parameters are    substitued on the
>>          command line, including %h    for the    target    hostname,
>>          %u     for  the  remote username, and    %n for the remote
>>          rank [0-n]    (To get    a literal % use    %%).   For  exam-
>>          ple,  the    following  would  duplicate using the ssh
>>          module to run hostname(1) across  the  hosts  foo[0-
>>          10]:
>>
>>         pdsh -R    exec -w    foo[0-10] ssh -x -l %u %h hostname
>>
>>          and this command line would run grep(1) in     parallel
>>          across the    files console.foo[0-10]:
>>
>>         pdsh -R    exec -w    foo[0-10] grep BUG console.%h
>>
>>
>>      ssh     Uses a variant of popen(3)    to run multiple    copies of
>>          the ssh(1)    command.
>>
>>      mrsh    This module uses the  mrsh(1)  protocol  to  execute
>>          jobs  on  remote  hosts.    The  mrsh protocol uses    a
>>          credential    based authentication, forgoing    the  need
>>          to     allocate  reserved  ports.  In    other aspects, it
>>          acts just like rsh. Remote     nodes    must  be  running
>>          mrshd(8) in order for the mrsh module to work.
>>
>>      qsh     Allows pdsh to execute MPI    jobs over  QsNet.  Qshell
>>          propagates      the  current    working     directory,  pdsh
>>          environment, and Elan  capabilities  to  the  remote
>>          process. The following environment    variable are also
>>          appended to the environment:  RMS_RANK,  RMS_NODEID,
>>          RMS_PROCID,  RMS_NNODES,  and RMS_NPROCS. Since pdsh
>>          needs to run setuid root for qshell support,  qshell
>>          does    not    directly   support     propagation   of
>>          LD_LIBRARY_PATH   and   LD_PREOPEN.   Instead    the
>>          QSHELL_REMOTE_LD_LIBRARY_PATH              and
>>          QSHELL_REMOTE_LD_PREOPEN environment variables  will
>>          may  be used and will be remapped to LD_LIBRARY_PATH
>>          and LD_PREOPEN by the qshell daemon if set.
>>
>>      mqsh    Similar  to  qshell,  but    uses  the  mrsh     protocol
>>          instead of    the rsh    protocol.
>>
>>
>>
>> pdsh-2.18        Last change: solaris2.11            2
>>
>>
>>
>>
>>
>>
>> User Commands                          pdsh(1)
>>
>>
>>
>>      krb4    The krb4 module allows users to execute remote  com-
>>          mands after authenticating    with kerberos. Of course,
>>          the remote    rshd daemons must be kerberized.
>>
>>      xcpu    The xcpu module uses the  xcpu  service  to  execute
>>          remote commands.
>>
>>
>> OPTIONS
>>      The list of available options is determined  at  runtime  by
>>      supplementing  the     list  of  standard pdsh options with any
>>      options provided by loaded    rcmd and misc modules.     In  some
>>      cases,  options  provided    by modules may conflict    with each
>>      other. In these cases, the    modules    are incompatible and  the
>>      first module loaded wins.
>>
>>
>> Standard target    nodelist options
>>      -w    [rcmd_type:][user@]host,host,...
>>       Target the specified list of hosts. Do not use with any
>>       other     node  selection options (e.g. -a, -g if they are
>>       available).  No  spaces  are    allowed     in  the   comma-
>>       separated  list.   A    list  consisting  of a single `-'
>>       character causes the    target    hosts  to  be  read  from
>>       stdin, one per line. The host    list may contain hostlist
>>       expressions  of  the    form  ``host[1-5,7]''.    For  more
>>       information about the    hostlist format, see the HOSTLIST
>>       EXPRESSIONS section below. A list of hosts may also  be
>>       preceded  by "user@" to specify a remote username other
>>       than the default, or "rcmd_type:" to specify an  alter-
>>       nate    rcmd  connection  type for these hosts.    When used
>>       together, the    rcmd type must be specified  first,  e.g.
>>       "ssh:user1@host0"  would use ssh to connect to host0 as
>>       user "user1."
>>
>>      -x    host,host,...
>>       Exclude the specified    hosts. May be specified     in  con-
>>       junction with    other target node list options such as -a
>>       and -g (when available). Hostlists may also  be  speci-
>>       fied    to  the     -x  option (see the HOSTLIST EXPRESSIONS
>>       section below).
>>
>>
>> Standard pdsh options
>>      -S      Return the largest of    the remote command return values.
>>
>>      -h      Output usage menu and    quit. A    list  of  available  
>> rcmd
>>       modules  will     also  be printed at the end of    the usage
>>       message.
>>
>>      -s      Only on AIX, separate    remote command stderr and  stdout
>>       into two sockets.
>>
>>
>>
>> pdsh-2.18        Last change: solaris2.11            3
>>
>>
>>
>>
>>
>>
>> User Commands                          pdsh(1)
>>
>>
>>
>>      -q      List option values and the  target  nodelist    and  exit
>>       without action.
>>
>>      -b      Disable ctrl-C status    feature    so that    a  
>> single  ctrl-C
>>       kills    parallel job. (Batch Mode)
>>
>>      -l    user
>>       This option may be  used  to    run  remote  commands  as
>>       another  user,  subject to authorization. For    BSD rcmd,
>>       this means the invoking user and system must be  listed
>>       in the user's    .rhosts    file (even for root).
>>
>>      -t    seconds
>>       Set the connect timeout. Default is 10 seconds.
>>
>>      -u    seconds
>>       Set a    limit on the amount of time a remote  command  is
>>       allowed  to  execute.     Default is no limit. See note in
>>       LIMITATIONS if using -u with ssh.
>>
>>      -f    number
>>       Set the maximum number of simultaneous remote     commands
>>       to number.  The default is 32.
>>
>>      -R    name
>>       Set rcmd module to name. This    option may  also  be  set
>>       via  the PDSH_RCMD_TYPE environment variable.    A list of
>>       available rcmd modules may be    obtained via the -h,  -V,
>>       or  -L  options.  The    default    will be    listed with -h or
>>       -V.
>>
>>      -L      List info on all loaded pdsh modules and quit.
>>
>>      -N      Disable hostname: prefix on lines of output.
>>
>>      -d      Include more complete     thread     status     when  
>> SIGINT  is
>>       received,  and display connect and command time statis-
>>       tics on stderr when done.
>>
>>      -V      Output pdsh version information,  along  with     list  of
>>       currently loaded modules, and    exit.
>>
>>
>> qsh/mqsh module    options
>>      -n    tasks_per_node
>>       Set the number of tasks spawned per node. Default is 1.
>>
>>      -m    block |    cyclic
>>       Set block versus  cyclic  allocation    of  processes  to
>>       nodes. Default is block.
>>
>>      -r    railmask
>>
>>
>>
>> pdsh-2.18        Last change: solaris2.11            4
>>
>>
>>
>>
>>
>>
>> User Commands                          pdsh(1)
>>
>>
>>
>>       Set the rail bitmask for a job on a  multirail  system.
>>       The  default railmask    is 1, which corresponds    to rail    0
>>       only.    Each bit set in    the argument to    -r corresponds to
>>       a  rail on the system, so a value of 2 would correspond
>>       to rail 1 only, and 3    would indicate to use both rail    1
>>       and rail 0.
>>
>>
>> machines module    options
>>      -a      Target all nodes from    machines file.
>>
>>
>> genders    module options
>>      In    addition to the     genders  options  presented  below,  the
>>      genders  attribute     pdsh_rcmd_type     may  also be used in the
>>      genders database to specify an alternate rcmd  connect  type
>>      than the pdsh default in the genders file
>>
>>        host0 pdsh_rcmd_type=ssh
>>
>>      would cause pdsh to use ssh to connect to host0, even if rsh
>>      were the default.    This can be overridden on the commandline
>>      with the "rcmd_type:host0"    syntax.
>>
>>
>>      -A      Target all nodes in genders  database.  The  -A  option
>>       will target every host listed    in genders -- if you want
>>       to omit some hosts by    default, see the -a option below.
>>
>>      -a      Target all nodes in genders database except those  with
>>       the  "pdsh_all_skip"    attribute.  This is shorthand for
>>       running "pdsh    -A -X pdsh_all_skip ..."
>>
>>      -g    attr[=val][,attr[=val],...]
>>       Target nodes that match any of  the  specified  genders
>>       attributes  (with  optional  values).    Conflicts with -a
>>       and -w options. This option targets the alternate host-
>>       names    in the genders database    by default. The    -i option
>>       provided by the genders module may be    used to    translate
>>       these     to  the  canonical  genders  hostnames.  If  the
>>       installed version of genders    supports  it,  attributes
>>       supplied  to    -g  may     also  take  the  form of genders
>>       queries. Genders queries will    query the  genders  data-
>>       base    for  the union,    intersection, difference, or com-
>>       plement of genders  attributes  and  values.     The  set
>>       operation  union  is    represented  by     two pipe symbols
>>       ('||'), intersection by two ampersand     symbols  ('&&'),
>>       difference  by two minus symbols ('--'), and complement
>>       by a tilde ('~').  Parentheses may be     used  to  change
>>       the  order  of  operations. See the nodeattr(1) manpage
>>       for examples of genders queries.
>>
>>
>>
>>
>> pdsh-2.18        Last change: solaris2.11            5
>>
>>
>>
>>
>>
>>
>> User Commands                          pdsh(1)
>>
>>
>>
>>      -X    attr[=val][,attr[=val],...]
>>       Exclude nodes    that match any of the  specified  genders
>>       attributes  (optionally  with    values).  This option may
>>       be used in combination  with    any  other  of    the  node
>>       selection  options  (e.g.  -w, -g, -a, -X may    also take
>>       the form of genders queries. Please  see  documentation
>>       for  the  genders  -g    option for more    information about
>>       genders queries.
>>
>>      -i      Request translation  between    canonical  and    alternate
>>       hostnames.
>>
>>      -F    filename
>>       Read genders information from    filename instead  of  the
>>       system default genders file.
>>
>>
>> nodeupdown module options
>>      -v      Eliminate target nodes that are  considered  "down"  by
>>       libnodeupdown.
>>
>>
>> slurm module options
>>      The slurm module  allows  pdsh  to     target     nodes    
>> based  on
>>      currently    running    SLURM jobs. The    slurm module is    
>> typically
>>      called after all other node selection options have    been pro-
>>      cessed,  and if no    nodes have been    selected, the module will
>>      attempt  to  read    a  running  jobid  from     the  SLURM_JOBID
>>      environment  variable  (which  is    set  when running under    a
>>      SLURM allocation).    If SLURM_JOBID references an invalid job,
>>      it    will be    silently ignored.
>>
>>      -j    jobid[,jobid,...]
>>       Target list of nodes allocated to the    SLURM job  jobid.
>>       This option may be used multiple times to target multi-
>>       ple SLURM jobs. The special argument "all" can be  used
>>       to target all    nodes running SLURM jobs, e.g.    -j all.
>>
>>
>> rms module options
>>      The rms module allows pdsh    to target nodes    based on  an  RMS
>>      resource. The rms module is typically called after    all other
>>      node selection options, and if no nodes have been    selected,
>>      the module    will examine the RMS_RESOURCEID    environment vari-
>>      able and attempt to set the target     list  of  hosts  to  the
>>      nodes  in    the  RMS  resource.  If     an  invalid  resource is
>>      denoted, the variable is silently ignored.
>>
>>
>> SDR module options
>>      The SDR module supports targeting hosts via the System  Data
>>      Repository    on IBM SPs.
>>
>>
>>
>> pdsh-2.18        Last change: solaris2.11            6
>>
>>
>>
>>
>>
>>
>> User Commands                          pdsh(1)
>>
>>
>>
>>      -a      Target all nodes in the SDR. The list    is generated from
>>       the "reliable    hostname" in the SDR by    default.
>>
>>      -i      Translate hostnames between reliable and initial in the
>>       SDR, when applicable.     If the    a target hostname matches
>>       either the initial or    reliable hostname in the SDR, the
>>       alternate name will be substitued. Thus a list composed
>>       of initial hostnames will instead be    replaced  with    a
>>       list    of  reliable  hostnames.   For example,    when used
>>       with -a above, all initial hostnames    in  the     SDR  are
>>       targeted.
>>
>>      -v      Do not target    nodes that are marked as  not  responding
>>       in  the  SDR    on the targeted    interface. (If a hostname
>>       does not appear in the SDR, then that    name will  remain
>>       in the target    hostlist.)
>>
>>      -G      In combination with -a, include all partitions.
>>
>>
>> nodeattr module    options
>>      The nodeattr module supports access to the    genders     database
>>      via  the  nodeattr(1) command. See    the genders section above
>>      for a list    of support options with    this module.  The  option
>>      usage  with  the  nodeattr     module     is  the same as genders,
>>      above, with the exception that the    -i  option  may     only  be
>>      used  with     -a  or    -g. NOTE: This module will only    work 
>> with
>>      very old releases of genders where    the  nodeattr(1)  command
>>      supports  the  -r    option,    and before the libgenders API was
>>      available.    Users running newer versions of    genders    will 
>> need
>>      to    use the    genders    module instead.
>>
>>
>> dshgroup module    options
>>      The dshgroup module allows    pdsh  to  use  dsh  (or     Dancer's
>>      shell)   style   group   files   from   /etc/dsh/group/   or
>>      ~/.dsh/group/.
>>
>>      -g    groupname,...
>>       Target nodes in dsh group  file  "groupname"    found  in
>>       either         ~/.dsh/group/groupname           or
>>       /etc/dsh/group/groupname.
>>
>>      -X    groupname,...
>>       Exclude nodes    in dsh group file "groupname."
>>
>>
>> netgroup module    options
>>      The netgroup module allows    pdsh  to  use  standard     netgroup
>>      entries  to  build     lists of target hosts.    (/etc/netgroup or
>>      NIS)
>>
>>
>>
>>
>> pdsh-2.18        Last change: solaris2.11            7
>>
>>
>>
>>
>>
>>
>> User Commands                          pdsh(1)
>>
>>
>>
>>      -g    groupname,...
>>       Target nodes in netgroup "groupname."
>>
>>      -X    groupname,...
>>       Exclude nodes    in netgroup "groupname."
>>
>>
>> ENVIRONMENT VARIABLES
>>      PDSH_RCMD_TYPE
>>       Equivalent to    the -R option, the value of this environ-
>>       ment    variable  will    be  used  to set the default rcmd
>>       module for pdsh to use (e.g. ssh, rsh).
>>
>>      PDSH_SSH_ARGS
>>       Override the standard    arguments that pdsh passes to the
>>       ssh(1) command ("-2 -a -x").
>>
>>      PDSH_SSH_ARGS_APPEND
>>       Append additional options to the ssh(1) command invoked
>>       by  pdsh.  For example, PDSH_SSH_ARGS_APPEND="-q" would
>>       run ssh in quiet mode, or "-v" would increase    the  ver-
>>       bosity of ssh.
>>
>>      WCOLL
>>       If no    other node selection option is    used,  the  WCOLL
>>       environment  variable     may  be  set  to a filename from
>>       which    a list of target hosts will  be     read.    The  file
>>       should  contain  a  list of hosts, one per line (though
>>       each line may    contain    a hostlist expression.    See HOST-
>>       LIST EXPRESSIONS section below).
>>
>>      DSHPATH
>>       If set, the path in DSHPATH will be used  as    the  PATH
>>       for the remote processes.
>>
>>      FANOUT
>>       Set the pdsh fanout (See description of -f above).
>>
>>
>> HOSTLIST EXPRESSIONS
>>      As    noted in sections above    pdsh accepts lists of  hosts  the
>>      general  form:  prefix[n-m,l-k,...],  where n < m and l < k,
>>      etc., as an alternative to    explicit  lists     of  hosts.  This
>>      form  should not be confused with regular expression charac-
>>      ter classes (also denoted by ``[]''). For    example,  foo[19]
>>      does  not represent an expression matching    foo1 or    foo9, but
>>      rather represents the degenerate hostlist:    foo19.
>>
>>      The hostlist syntax is meant only as a convenience    on  clus-
>>      ters  with    a "prefixNNN" naming convention    and specification
>>      of     ranges     should     not  be  considered  necessary     
>> --  this
>>      foo1,foo9    could  be  specified  as such, or by the hostlist
>>
>>
>>
>> pdsh-2.18        Last change: solaris2.11            8
>>
>>
>>
>>
>>
>>
>> User Commands                          pdsh(1)
>>
>>
>>
>>      foo[1,9].
>>
>>      Some examples of usage follow:
>>
>>
>>      Run command on foo01,foo02,...,foo05
>>      pdsh -w foo[01-05] command
>>
>>      Run command on foo7,foo9,foo10
>>      pdsh -w foo[7,9-10] command
>>
>>      Run command on foo0,foo4,foo5
>>      pdsh -w foo[0-5] -x foo[1-3] command
>>
>>
>>      A suffix on the hostname is also supported:
>>
>>
>>      Run command on foo0-eth0,foo1-eth0,foo2-eth0,foo3-eth0
>>     pdsh -w    foo[0-3]-eth0 command
>>
>>
>>      As    a reminder to the  reader,  some  shells  will    interpret
>>      brackets  ('['  and ']') for pattern matching.  Depending on
>>      your shell, it may    be  necessary  to  enclose  ranged  lists
>>      within  quotes.   For  example,  in  tcsh,    the first example
>>      above should be executed as:
>>
>>      pdsh -w "foo[01-05]" command
>>
>>
>> ORIGIN
>>      Originally     a  rewrite  of     IBM  dsh(1)   by   Jim      
>> Garlick
>>      <garlick@llnl.gov>     on  LLNL's ASCI Blue-Pacific IBM SP sys-
>>      tem. It is    now used on Linux clusters at LLNL.
>>
>>
>> LIMITATIONS
>>      When using    ssh for    remote execution, expect  the  stderr  of
>>      ssh  to  be  folded in with that of the remote command. When
>>      invoked by    pdsh, it is not    possible for ssh  to  prompt  for
>>      passwords    if  RSA/DSA  keys  are configured properly, etc..
>>      For ssh implementations  that  suppport  a     connect  timeout
>>      option,  pdsh  attempts  to  use  that option to enforce the
>>      timeout (e.g.  -oConnectTimeout=T    for  OpenSSH),    otherwise
>>      connect timeouts are not supported    when using ssh.     Finally,
>>      there is no reliable way for pdsh to ensure that remote com-
>>      mands  are    actually terminated when using a command timeout.
>>      Thus if -u    is used    with ssh commands may be left running  on
>>      remote  hosts  even  after     timeout  has  killed  local  ssh
>>      processes.
>>
>>
>>
>>
>> pdsh-2.18        Last change: solaris2.11            9
>>
>>
>>
>>
>>
>>
>> User Commands                          pdsh(1)
>>
>>
>>
>>      Output from multiple processes per    node may be  interspersed
>>      when using    qshell or mqshell rcmd modules.
>>
>>      The number    of nodes that  pdsh  can  simultaneously  execute
>>      remote  jobs  on is limited by the    maximum    number of threads
>>      that can be created concurrently, as well as the  availabil-
>>      ity of reserved ports in the rsh and qshell rcmd modules. On
>>      systems that implement Posix threads, the limit is    typically
>>      defined by    the constant PTHREADS_THREADS_MAX.
>>
>>
>> FILES
>> ATTRIBUTES
>>      See attributes(5) for descriptions    of the    following  attri-
>>      butes:
>>
>>
>>
>>      ____________________________________________________________
>>     |        ATTRIBUTE TYPE      |      ATTRIBUTE VALUE    |
>>     |_____________________________|_____________________________|
>>     | Availability          | SUNWpdsh            |
>>     |_____________________________|_____________________________|
>>     | Interface    Stability      | uncommitted            |
>>     |_____________________________|_____________________________|
>>
>>
>> SEE ALSO
>>      rsh(1),         ssh(1),          dshbak(1),      pdcp(1)
>>      http://sourceforge.net/projects/pdsh/
>>
>> NOTES
>>      Source for    pdsh is    available on http://opensolaris.org
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> pdsh-2.18        Last change: solaris2.11               10
>>
>>
>>   
>> ------------------------------------------------------------------------
>>
>> Template Version: @(#)sac_nextcase %I% %G% SMI This information is 
>> Copyright 2009 Sun Microsystems 1. Introduction
>>     1.1. Project/Component Working Name:
>>      pdsh Ver 2.18
>>     1.2. Name of Document Author/Supplier:
>>      Author:  Vivek R. Titarmare
>>     1.3  Date of This Document:
>>      3rd April, 2009
>>
>> 2. Project Summary
>>    2.1 Project Description
>>
>>     Parallel command execution for clusters
>>
>> 4. Technical Description:
>>
>>     Pdsh is a high-performance, parallel remote shell utility. It has 
>> built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and 
>> can call SSH externally (though with reduced performance). Pdsh uses 
>> a "sliding window" parallel algorithm to conserve socket resources on 
>> the initiating node and to allow progress to continue while timeouts 
>> occur on some connections.
>>     
>>     Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which 
>> runs commands on a single remote host, pdsh can run multiple remote 
>> commands in parallel. pdsh uses a "sliding window" (or fanout) of 
>> threads to conserve resources on the the initiating host while 
>> allowing some connections to time out.    
>>
>> 5. Interfaces
>>     The binary file "pdsh" contains following interface.
>>
>>    Exported interface                   Classification         
>> Interface type
>>    =============================        ==============         
>> ==============
>>        usr/bin/dshbak            Uncommitted        binary
>>        usr/bin/pdcp            Uncommitted        binary
>>        usr/bin/pdsh            Uncommitted        binary
>>        usr/bin/rpdcp            Uncommitted        binary
>>        usr/lib/pdsh/xrcmd.so        Uncommitted        shared library
>>        usr/lib/pdsh/xrcmd.la        Uncommitted        library tool
>>        usr/lib/pdsh/xrcmd.a        Uncommitted        static library
>>        usr/lib/pdsh/execcmd.so        Uncommitted        shared library
>>        usr/lib/pdsh/execcmd.la        Uncommitted        library tool
>>        usr/lib/pdsh/execcmd.a        Uncommitted        static library
>>       
>>     PDSH_RCMD_TYPE            Uncommitted        override standard 
>> argument
>>     PDSH_SSH_ARGS            Uncommitted        override standard 
>> argument
>>     PDSH_SSH_ARGS_APPEND        Uncommitted        override standard 
>> argument
>>     WCOLL                Uncommitted        override standard argument
>>     DSHPATH                Uncommitted        override standard argument
>>     FANOUT                Uncommitted        override standard argument
>>     QSHELL_REMOTE_LD_LIBRARY_PATH    Uncommitted        override 
>> standard argument
>>     QSHELL_REMOTE_LD_PREOPEN    Uncommitted        override standard 
>> argument
>>     
>>
>>    Imported interface        Classification   Comments
>>    =======================   ==============   
>> ===================================     None
>>
>>    The binary file would go in "usr/bin" and the libraries would go 
>> in "usr/lib"
>>
>>
>> 6. Resources and Schedule
>>     6.4. Steering Committee requested information
>>        6.4.1. Consolidation C-team Name:
>>         SFW
>>     6.5. ARC review type: FastTrack
>>     6.6. ARC Exposure: open
>> ------------------------------------------------------------------------
>>
>> FCL--FOSS Check List
>>
>> 1.0 Project Information
>> 1.1 Name of project/component
>>     pdsh  Ver 2.18
>>
>> 1.2 Author of document
>>     Vivek R. Titarmare
>>
>> 2.0 Project Summary
>>   2.1 Project Description
>>
>>     Pdsh is a high-performance, parallel remote shell utility. It has 
>> built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and 
>> can call SSH externally (though with reduced performance). Pdsh uses 
>> a "sliding window" parallel algorithm to conserve socket resources on 
>> the initiating node and to allow progress to continue while timeouts 
>> occur on some connections.
>>     
>>     Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which 
>> runs commands on a single remote host, pdsh can run multiple remote 
>> commands in parallel. pdsh uses a "sliding window" (or fanout) of 
>> threads to conserve resources on the the initiating host while 
>> allowing some connections to time out.    
>>
>>     Pdsh is a an efficient, multithreaded remote shell client which 
>> executes commands on multiple remote hosts in parallel. Pdsh 
>> implements dynamically loadable modules for extended functionality 
>> such as new remote shell services and remote host selection
>>
>>   2.2 Release binding
>>       What is is the release binding?
>>       (see 
>> http://opensolaris.org/os/community/arc/policies/release-taxonomy/)
>>       [ ] Major
>>       [X] Minor
>>       [ ] Patch or Micro
>>       [ ] Unknown -- ARC review required
>>
>>   2.3 Type of project
>>       Is this case a Linux Familiarity project?
>>       [X] Yes
>>       [ ] No
>>
>>   2.4 Originating Community
>>     2.4.1 Community Name
>>         PDSH (http://sourceforge.net/projects/pdsh/)
>>         2.4.2 Community Involvement
>>       Indicate Sun's involvement in the community
>>       [ ] Maintainer
>>       [ ] Contributor
>>       [X] Monitoring
>>             Will the project team work with the upstream community to 
>> resolve
>>       architectural issues of interest to Sun?
>>       [X] Yes       [ ] No - briefly explain
>>           
>>       Will we or are we forking from the community?
>>       [ ] Yes - ARC review required prior to forking
>>       [X] No
>>       3.0 Technical Description
>>   3.1 Installation & Sharable
>>     3.1.1S Solaris Installation - section only required for Solaris 
>> Software
>>       (see 
>> http://opensolaris.org/os/community/arc/policies/install-locations/ 
>> for details)
>>       Does this project follow the Install Locations best practice?
>>       [X] Yes       [ ] No - ARC review required
>>             Does this project install into /usr under 
>> [sbin|bin|lib|include|man|share]?
>>       [X] Yes
>>       [ ] No or N/A
>>             Does this project install into /opt?
>>       [ ] Yes - explain below
>>       [X] No or N/A
>>             Does this project install into a different directory 
>> structure?
>>       [ ] Yes - ARC review required
>>       [X] No or N/A
>>             Do any of the components of this project conflict with 
>> anything under /usr?
>>       (see http://opensolaris.org/os/community/arc/caselog/2007/047/ 
>> for details)
>>       [ ] Yes - explain below
>>       [X] No
>>             If conflicts exist then will this project install under 
>> /usr/gnu?
>>       [ ] Yes
>>       [ ] No - ARC review required
>>       [X] N/A
>>             Is this project installing into /usr/sfw?
>>       [ ] Yes - ARC review required
>>       [X] No
>>           3.1.1W Windows Installation - section only required for 
>> Windows Software
>>       (see http://sac.sfbay/WSARC/2002/494 for details)
>>       Does this project install software into a       <system 
>> drive>:\Program Files\Sun\<product> or <system drive>:\Sun\<product>
>>       directory?
>>       [ ] Yes
>>       [ ] No - ARC review required
>>             Does the project use the Windows registry?
>>       [ ] Yes
>>       [ ] No - ARC review required
>>             Does the project use       
>> HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\<product>\<version>
>>       for the registry key?
>>       [ ] Yes
>>       [ ] No - ARC review required
>>             Is the project's stored location
>>       HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\<product 
>> id>\<version id>\Path?
>>       [ ] Yes
>>       [ ] No - ARC review required
>>           3.1.2 Share and Sharable
>>       Does the module include any components that are used or shared 
>> by       other projects?
>>       [X] Yes
>>       [ ] No
>>           If yes are these components packaged to be shared with the 
>> other FOSS?
>>       [X] Yes
>>       [ ] No - ARC review required
>>       [ ] N/A
>>           Are these components already in the Solaris WOS?
>>       [X] Yes
>>       [ ] No - continue with next section (section 3.2)
>>           If yes are these newer versions being delivered?
>>       [X] Yes
>>       [ ] No - ARC review required
>>             If yes are the newer versions replacing the existing 
>> versions?
>>       [X] Yes
>>       [ ] No - ARC review required
>>
>>   3.2 Exported Libraries
>>       Are libraries being delivered by this project?
>>       [ ] Yes
>>       [X] No - continue with next section (section 3.3)
>>             Are 64-bit versions of the libraries being delivered?
>>       [ ] Yes
>>       [ ] No - ARC review required
>>           Are static versions of the libraries being delivered?
>>       [ ] Yes - ARC review required
>>       [ ] No         3.3 Services and the /etc Directory
>>       (see http://opensolaris.org/os/community/arc/policies/SMF-policy/)
>>       Does the project integrate anything into /etc/init.d or 
>> /etc/rc?.d?
>>       [ ] Yes - ARC review required
>>       [X] No
>>             Does the project integrate any new entries into 
>> /etc/inittab or
>>       /etc/inetd.conf?
>>       [ ] Yes - ARC review required
>>       [X] No
>>             Does the project integrate any private non-public files 
>> into /etc/default
>>       or /etc/ configuration files?
>>       [ ] Yes - ARC review required
>>       [X] No
>>             Does the service manifests method context grant rights 
>> above that
>>       of the noaccess user and basic privilege set?
>>       [ ] Yes - ARC review required
>>       [X] No
>>           3.4 Security
>>     3.4.1 Secure By Default       (see 
>> http://opensolaris.org/os/community/arc/policies/secure-by-default/ 
>> for details)
>>       (see 
>> http://www.opensolaris.org/os/community/arc/policies/NITS-policy/ for 
>> details)
>>       (see parts of 
>> http://opensolaris.org/os/community/arc/policies/SMF-policy/ for
>>        addtional details)
>>       Are there any network services provided by this project?
>>       [ ] Yes
>>       [X] No - continue with the next section (section 3.4.2)
>>             Are network services enabled by default?
>>       [ ] Yes - ARC review required
>>       [ ] No
>>       [X] N/A
>>             Are network services automatically enabled by the project 
>> during installation?
>>       [ ] Yes - ARC review required
>>       [ ] No
>>       [X] N/A
>>             Are inbound network communications denied by default?
>>       [ ] Yes
>>       [ ] No - ARC review required
>>       [X] N/A
>>             Is inbound data checked to prevent content-based attacks?
>>       [ ] Yes
>>       [ ] No - ARC review required
>>       [X] N/A
>>             Is the outbound receiver authenticated?
>>       [ ] Yes
>>       [ ] No - ARC review required
>>       [X] N/A
>>             Is the receiver authenticated prior to receiving any 
>> sensitive outbound communication?
>>       [ ] Yes
>>       [ ] No - ARC review required
>>       [X] N/A
>>           3.4.2 Authorization
>>       (see 
>> http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/ and
>>        
>> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/ and
>>        
>> http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/
>>            for details)
>>       Are there any setuid/setgid privileged binaries in the project?
>>       [ ] Yes - ARC review required
>>       [X] No - continue with next section (section 3.4.3)
>>             If yes then are the setuid/setgid privileges handled by 
>> the use of roles?
>>       [ ] Yes
>>       [ ] No - ARC review required
>>
>>     3.4.3 Auditing
>>       (see 
>> http://opensolaris.org/os/community/arc/policies/audit-policy/ for 
>> details)
>>       (see http://opensolaris.org/os/community/arc/caselog/2003/397 
>> for details)
>>       Does this component contain administrative or security 
>> enforcing software?
>>       [ ] Yes - ARC review required
>>       [X] No - continue to next section (section 3.4.4)
>>             (see 
>> http://opensolaris.org/os/community/arc/caselog/2003/397 for details)
>>       Do the components create audit logs detailing what took place 
>> including what event
>>       took place, who was involved, when the event took place?
>>       [ ] Yes - ARC contract and Audit project team review required
>>       [ ] No - ARC review required
>>                     3.4.4 Authentication
>>       (see http://opensolaris.org/os/community/arc/policies/PAM/)
>>       Do the components contain any authentication code?
>>       [ ] Yes
>>       [X] No - continue to next section (section 3.4.5)
>>             If yes do the components use PAM (plugable authentication 
>> modules) for authentication?
>>       [ ] Yes
>>       [ ] No - ARC review required
>>             If yes is a single PAM session maintained during 
>> authentication?
>>       [ ] Yes
>>       [ ] No - ARC review required
>>             If yes are the components sufficiently privileged to 
>> allow the requested       operations (authentication, password 
>> change, process credential manipulation,       audit state 
>> initialization)?
>>       [ ] Yes - briefly describe below
>>       [ ] No - ARC review required
>>           3.4.5 Passwords
>>       (see 
>> http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/ and
>>            
>> http://opensolaris.org/os/community/arc/bestpractices/passwords-files/ 
>> for details)
>>       Do any of the components for the project deal with passwords?
>>       [ ] Yes
>>       [X] No - continue to next section (section 3.4.6)
>>             If yes are these passwords entered via the CLI or 
>> environment?
>>       [ ] Yes - ARC review required
>>       [ ] No
>>             Are passwords stored within the file system for the 
>> component?
>>       [ ] Yes
>>       [ ] No - continue to next section (section 3.4.6)
>>             If yes are the permissions on the file such to protect 
>> exposing the password(s)?
>>       [ ] Yes
>>       [ ] No - ARC review required
>>           3.4.6 General Security Questions
>>       (see 
>> http://opensolaris.org/os/community/arc/bestpractices/security-questions/ 
>> for details)
>>       Are there any network protocols used by this project?
>>       [X] Yes
>>       [ ] No - continue with the next section (section 3.5)
>>             Do the components use standard network protocols?
>>       [X] Yes
>>       [ ] No - ARC review required
>>             Do network services for the project make decisions based 
>> upon user, host or       service identities?
>>       [X] Yes - explain below
>>       [ ] No
>>       [ ] N/A
>>                 pdsh makes decision on network services based upon 
>> service identities. pdsh is a variant of the rsh(1) command. The core 
>> functionality of pdsh may be supplemented by dynamically loadable 
>> modules. The modules may provide a new connection protocol (replacing 
>> the standard rcmd(3) protocol used by rsh(1)), filtering options 
>> (e.g. removing hosts that are "down" from the target list), and/or 
>> host selection options (e.g., -a selects all hosts from a 
>> configuration file.).Pdsh modules come in two flavors at this time: 
>> rcmd and miscellaneous.              
>>           The rcmd modules provide remote command functionality for 
>> pdsh. A list of rcmd modules currently distributed with pdsh follows. 
>>               rsh Uses an internal, thread-safe implementation of BSD 
>> rcmd(3) to run commands using the standard rsh(1) protocol. 
>>               ssh Uses a variant of popen(3) to run multiple copies 
>> of the ssh(1) command.               mrsh This module uses the 
>> mrsh(1) protocol to execute jobs on remote hosts. The mrsh protocol 
>> uses a credential based authentication, forgoing the need to allocate 
>> reserved ports. In other aspects, it acts just like rsh. Remote nodes 
>> must be running mrshd(8) in order for the mrsh module to work. 
>>                    qsh  Allows pdsh to execute MPI jobs over QsNet. 
>> Qshell propagates the current working directory, pdsh environment, 
>> and Elan capabilities to the remote process. The following 
>> environment variable are also appended to the environment: RMS_RANK, 
>> RMS_NODEID, RMS_PROCID, RMS_NNODES, and RMS_NPROCS.         Since 
>> pdsh needs to run setuid root for qshell support, qshell does not 
>> directly support propagation of LD_LIBRARY_PATH and LD_PREOPEN. 
>> Instead the QSHELL_REMOTE_LD_LIBRARY_PATH and 
>> QSHELL_REMOTE_LD_PREOPEN environment variables will may be used and 
>> will be remapped to LD_LIBRARY_PATH and LD_PREOPEN by the qshell 
>> daemon if set.                 mqsh Similar to qshell, but uses the 
>> mrsh protocol instead of the rsh protocol.                 krb4 The 
>> krb4 module allows users to execute remote commands after 
>> authenticating with kerberos. Of course, the remote rshd daemons must 
>> be kerberized.                 xcpu The xcpu module uses the xcpu 
>> service to execute remote commands
>>             Do the components make use of secret information during 
>> authentication and/or
>>       authorization?
>>       [ ] Yes - explain below
>>       [X] No
>>       [ ] N/A
>>     3.5 Networking
>>       Do the components access the network?
>>       [X] Yes
>>       [ ] No - continue with the next section (section 3.6)
>>             If yes do the components support IPv6?
>>       [X] Yes       [ ] No - ARC review required
>>             3.6 Core Solaris Components
>>       Do the components of this project compete with or duplicate 
>> core       Solaris components?
>>       [ ] Yes - ARC review required
>>       [X] No              4.0 Interfaces
>>   (see 
>> http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/ 
>> for details)
>>   4.1 Exported Interfaces
>>       The binary file "pdsh" contains following interface.
>>
>>     Interface Name            Classification              Comments
>>     ---------------------------     -------------------     
>> ---------------------------
>>        usr/bin/dshbak            Uncommitted        binary
>>        usr/bin/pdcp            Uncommitted        binary
>>        usr/bin/pdsh            Uncommitted        binary
>>        usr/bin/rpdcp            Uncommitted        binary
>>        usr/lib/pdsh/xrcmd.so        Uncommitted        shared library
>>        usr/lib/pdsh/xrcmd.la        Uncommitted        library tool
>>        usr/lib/pdsh/xrcmd.a        Uncommitted        static library
>>        usr/lib/pdsh/execcmd.so        Uncommitted        shared library
>>        usr/lib/pdsh/execcmd.la        Uncommitted        library tool
>>        usr/lib/pdsh/execcmd.a        Uncommitted        static library
>>       
>>     PDSH_RCMD_TYPE            Uncommitted        override standard 
>> argument
>>     PDSH_SSH_ARGS            Uncommitted        override standard 
>> argument
>>     PDSH_SSH_ARGS_APPEND        Uncommitted        override standard 
>> argument
>>     WCOLL                Uncommitted        override standard argument
>>     DSHPATH                Uncommitted        override standard argument
>>     FANOUT                Uncommitted        override standard argument
>>     QSHELL_REMOTE_LD_LIBRARY_PATH    Uncommitted        override 
>> standard argument
>>     QSHELL_REMOTE_LD_PREOPEN    Uncommitted        override standard 
>> argument
>>     
>>
>>   4.2 Imported Interfaces
>>     Interface Name        Classification       Comments
>>     --------------------------- -------------------- 
>> --------------------------
>>     None   
>> The binary file would go in "/usr/bin" and the libraries would go in 
>> "/usr/lib"
>>
>> Appendix B - Suggested case materials
>>   1. man pages
>>
>>      Attached are the man pages (pdsh.1, pdcp.1, dshbak.1)
>>
>>   2. SMF manifests
>>   3. links to contracts
>>   
>
> _______________________________________________
> opensolaris-arc mailing list
> opensolaris-arc@opensolaris.org

-- 
<http://www.sun.com> 	* Mark A. Carlson *
Sr. Architect

*Systems Group*
Phone x69559 / 303-223-6139
Email Mark.Carlson@Sun.COM
	



--Boundary_(ID_c23GdocVnywPtkpBCToWGw)
Content-type: text/html; charset=ISO-8859-1
Content-transfer-encoding: 7BIT

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>The case directory has been updated with new materials.<br>
<br>
Any last issues before I close this case?<br>
<br>
-- mark<br>
</tt><br>
Margot Miller wrote:
<blockquote cite="mid:49EF480E.4070106@sun.com" type="cite">Vivek,
  <br>
  <br>
Please add the package SUNWpdsh to the interface table.
  <br>
  <br>
In the pdsh man page, it has:
  <br>
  <br>
&nbsp;&nbsp;&nbsp; qsh&nbsp;&nbsp;&nbsp;&nbsp; Allows pdsh to execute MPI&nbsp;&nbsp;&nbsp; jobs over&nbsp; QsNet.&nbsp; Qshell
  <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; propagates&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the&nbsp; current&nbsp;&nbsp;&nbsp; working&nbsp;&nbsp;&nbsp;&nbsp; directory,&nbsp; pdsh
  <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; environment, and Elan&nbsp; capabilities&nbsp; to&nbsp; the&nbsp; remote
  <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; process. The following environment&nbsp;&nbsp;&nbsp; variable are also
  <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; appended to the environment:&nbsp; RMS_RANK,&nbsp; RMS_NODEID,
  <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; RMS_PROCID,&nbsp; RMS_NNODES,&nbsp; and RMS_NPROCS. Since pdsh
  <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; needs to run setuid root for qshell support,&nbsp; qshell
  <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; does&nbsp;&nbsp;&nbsp; not&nbsp;&nbsp;&nbsp; directly&nbsp;&nbsp; support&nbsp;&nbsp;&nbsp;&nbsp; propagation&nbsp;&nbsp; of
  <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LD_LIBRARY_PATH&nbsp;&nbsp; and&nbsp;&nbsp; LD_PREOPEN.&nbsp;&nbsp; Instead&nbsp;&nbsp;&nbsp; the
  <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; QSHELL_REMOTE_LD_LIBRARY_PATH&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and
  <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; QSHELL_REMOTE_LD_PREOPEN environment variables&nbsp; will
  <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; may&nbsp; be used and will be remapped to LD_LIBRARY_PATH
  <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and LD_PREOPEN by the qshell daemon if set.
  <br>
  <br>
Does this project support Qshell?&nbsp; <br>
Also, there is a section in one of the man pages about slurm
  <br>
module options.&nbsp; Per Danek in the below email, this is not
  <br>
relevant for Solaris.&nbsp; The documentation needs to be updated
  <br>
to reflect that this isn't supported on Solaris.
  <br>
  <br>
Please check through all the man pages to ensure that everything
  <br>
in the man pages is correct wrt Solaris and what is in the man pages
  <br>
is reflected in the interface table.
  <br>
  <br>
Also, please have your sponsor review all the materials
  <br>
before you resend the updated documents.
  <br>
  <br>
Thanks
  <br>
Margot
  <br>
  <br>
  <br>
  <br>
  <br>
Vivek Titarmare wrote:
  <br>
  <blockquote type="cite">Hi Danek and the team,
    <br>
    <br>
I have updated the Fasttrack and FOSS check list for pdsh. Major
changes in
    <br>
the interface tables would be seen. Actually a rework was done on this
    <br>
package and found that the interface table needed a change. <br>
Pl. ignore the previous Interface related conflicts.
    <br>
    <br>
Let me know if this looks good to go.
    <br>
    <br>
Pl. find attached all the files required for this ARC review.
    <br>
    <br>
Thanks,
    <br>
~Vivek R. Titarmare
    <br>
    <br>
    <br>
    <br>
-----Original Message-----
    <br>
From: Danek Duvall [<a class="moz-txt-link-freetext" href="mailto:Danek.Duvall@Sun.COM">mailto:Danek.Duvall@Sun.COM</a>] Sent: Tuesday, April
21, 2009 11:39 PM
    <br>
To: Vivek Titarmare
    <br>
Cc: 'Mark Carlson'; <a class="moz-txt-link-abbreviated" href="mailto:James.D.Carlson@Sun.COM">James.D.Carlson@Sun.COM</a>; <a class="moz-txt-link-abbreviated" href="mailto:Nicolas.Williams@Sun.COM">Nicolas.Williams@Sun.COM</a>;
    <br>
<a class="moz-txt-link-abbreviated" href="mailto:Manisha.Jha@Sun.COM">Manisha.Jha@Sun.COM</a>
    <br>
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout
04/20/2009]
    <br>
    <br>
[ Please use standard email quoting techniques -- a "&gt; " prefix to
every
    <br>
line that you're responding to, and not to your own; what you're doing
    <br>
makes your email responses incredibly difficult to read.&nbsp; Perhaps not
using
    <br>
Outlook would help.&nbsp; This is Sun, after all; you should be running
Solaris.
    <br>
]
    <br>
    <br>
On Tue, Apr 21, 2009 at 10:46:14PM +0530, Vivek Titarmare wrote:
    <br>
    <br>
&nbsp;
    <blockquote type="cite">
      <blockquote type="cite">No, I want you to not deliver those
interfaces.&nbsp; You can't ship
        <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </blockquote>
    </blockquote>
components
    <br>
&nbsp;
    <blockquote type="cite">
      <blockquote type="cite">that don't work.&nbsp; This is a commercial
OS, not a grad student project,
        <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </blockquote>
    </blockquote>
and
    <br>
&nbsp;
    <blockquote type="cite">
      <blockquote type="cite">it costs Sun tons of money to field calls
from customers complaining
        <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </blockquote>
    </blockquote>
about
    <br>
&nbsp;
    <blockquote type="cite">
      <blockquote type="cite">things that don't work.&nbsp; It's best not to
ship them at all if we know
        <br>
they're busted.&nbsp; Given how much of the man page is filled with text
        <br>
describing options and arguments that won't be useful on Solaris,
you'll
        <br>
need to remove this extraneous documentation before delivery, too.
        <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </blockquote>
[VIVEK] I am sorry, I think I confused you. All the components work,
for
      <br>
those components to work we need to override the environment variables
      <br>
&nbsp;&nbsp;&nbsp; </blockquote>
which
    <br>
&nbsp;
    <blockquote type="cite">I am adding those in the Interface table. I
this case, do we still need to
      <br>
remove the contents from the man pages. Pl. let me know.
      <br>
&nbsp;&nbsp;&nbsp; </blockquote>
    <br>
The components that are unavailable (libgenders, nodeattr, etc) will
cause
    <br>
portions of pdsh (pdsh-mod-genders, pdsh-mod-nodeattr, etc) not to
work,
    <br>
environment variables or not.&nbsp; There is no way that "pdsh-mod-slurm" is
    <br>
going to work unless slurm is installed, and since there is no slurm
    <br>
available for Solaris, then "pdsh-mod-slurm" is not going to work on
    <br>
Solaris.&nbsp; So don't ship it, and don't document it.
    <br>
    <br>
Danek
    <br>
------------------------------------------------------------------------
    <br>
    <br>
    <br>
    <br>
    <br>
DSHBAK&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DSHBAK(1)
    <br>
    <br>
    <br>
    <br>
NAME
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; dshbak - format output from pdsh command
    <br>
    <br>
SYNOPSIS
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; dshbak [-c]
    <br>
    <br>
DESCRIPTION
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; dshbak formats pdsh output&nbsp;&nbsp;&nbsp; for&nbsp; humans.&nbsp;&nbsp; Output&nbsp; from&nbsp; each
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; node&nbsp; is consolidated, the&nbsp;&nbsp;&nbsp; leading&nbsp;&nbsp;&nbsp; node: prefix is&nbsp;&nbsp;&nbsp;
stripped,
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; and a header block&nbsp;&nbsp;&nbsp; with the node name is added.&nbsp; If&nbsp; the&nbsp; -c
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; option&nbsp; is&nbsp;&nbsp;&nbsp;&nbsp; specified,&nbsp; nodes&nbsp; with identical output are not
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; displayed twice; instead, the header will contain a list&nbsp; of
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; nodes.&nbsp;&nbsp; The&nbsp; list&nbsp;&nbsp;&nbsp;&nbsp; of nodes is further compressed&nbsp;&nbsp;&nbsp; into node
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; ranges if the node&nbsp;&nbsp;&nbsp; names have a numeric suffix.
    <br>
    <br>
    <br>
ORIGIN
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; A rewrite of IBM dshbak(1)&nbsp;&nbsp;&nbsp; by Jim Garlick
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; <a class="moz-txt-link-rfc2396E" href="mailto:garlick@llnl.gov">&lt;garlick@llnl.gov&gt;</a>&nbsp;&nbsp;&nbsp; on LLNL's ASCI Blue-Pacific IBM&nbsp;&nbsp;&nbsp;&nbsp;
SP&nbsp; sys-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; tem.
    <br>
    <br>
    <br>
ATTRIBUTES
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; See attributes(5) for descriptions&nbsp;&nbsp;&nbsp; of the&nbsp;&nbsp;&nbsp; following&nbsp; attri-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; butes:
    <br>
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; ____________________________________________________________
    <br>
&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATTRIBUTE TYPE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATTRIBUTE VALUE&nbsp;&nbsp;&nbsp; |
    <br>
&nbsp;&nbsp;&nbsp; |_____________________________|_____________________________|
    <br>
&nbsp;&nbsp;&nbsp; | Availability&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | SUNWpdsh&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
    <br>
&nbsp;&nbsp;&nbsp; |_____________________________|_____________________________|
    <br>
&nbsp;&nbsp;&nbsp; | Interface&nbsp;&nbsp;&nbsp; Stability&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
    <br>
&nbsp;&nbsp;&nbsp; |_____________________________|_____________________________|
    <br>
    <br>
    <br>
SEE ALSO
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; pdsh(1)
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
LLNL&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last change: Release 1.3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1
    <br>
    <br>
    <br>
&nbsp;
------------------------------------------------------------------------
    <br>
    <br>
    <br>
    <br>
    <br>
User Commands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdsh(1)
    <br>
    <br>
    <br>
    <br>
NAME
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; pdcp - copy files to groups of hosts in parallel
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; rpdcp - (reverse pdcp) copy files from a group of&nbsp;&nbsp;&nbsp; hosts&nbsp; in
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; parallel
    <br>
    <br>
    <br>
SYNOPSIS
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; pdcp [options]... src [src2...] dest
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; rpdcp [options]...&nbsp;&nbsp;&nbsp; src [src2...] dir
    <br>
    <br>
    <br>
DESCRIPTION
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; pdcp is a variant of the&nbsp; rcp(1)&nbsp; command.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Unlike&nbsp; rcp(1),
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; which&nbsp; copies&nbsp; files&nbsp; to a&nbsp;&nbsp;&nbsp; single remote host, pdcp can copy
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; files to multiple remote hosts in parallel.&nbsp;&nbsp; However,&nbsp; pdcp
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; does not recognize&nbsp;&nbsp;&nbsp; files in the format ``rname@rhost:path,''
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; therefore all&nbsp; source&nbsp; files&nbsp; must&nbsp;&nbsp;&nbsp;&nbsp; be&nbsp; on&nbsp;&nbsp;&nbsp;&nbsp; the&nbsp; local&nbsp; host
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; machine.&nbsp;&nbsp;&nbsp; Destination nodes must be listed on the&nbsp;&nbsp;&nbsp; pdcp com-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; mand line using a suitable&nbsp;&nbsp;&nbsp; target nodelist&nbsp;&nbsp;&nbsp; option&nbsp;&nbsp;&nbsp; (See&nbsp;
the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; OPTIONS&nbsp; section&nbsp; below).&nbsp;&nbsp;&nbsp; Each destination node listed must
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; have pdcp installed for the copy to succeed.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; When pdcp receives&nbsp;&nbsp;&nbsp; SIGINT (ctrl-C), it lists the&nbsp; status&nbsp; of
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; current&nbsp; threads.&nbsp;&nbsp;&nbsp;&nbsp; A&nbsp; second&nbsp; SIGINT within one second ter-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; minates the program. Pending&nbsp; threads&nbsp; may&nbsp;&nbsp;&nbsp;&nbsp; be&nbsp; canceled&nbsp; by
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; issuing ctrl-Z within one second of ctrl-C.&nbsp; Pending threads
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; are those that have not yet been initiated, or are&nbsp;&nbsp;&nbsp; still&nbsp; in
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; the process of connecting to the remote host.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; Like pdsh(1), the functionality of&nbsp;&nbsp;&nbsp; pdcp may be&nbsp; supplemented
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; by&nbsp;&nbsp;&nbsp;&nbsp; dynamically&nbsp; loadable&nbsp;&nbsp;&nbsp; modules. In pdcp, the modules may
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; provide a&nbsp;&nbsp;&nbsp; new&nbsp; connect&nbsp; protocol&nbsp;&nbsp;&nbsp; (replacing&nbsp; the&nbsp;&nbsp;&nbsp;&nbsp;
standard
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; rsh(1)&nbsp; protocol),&nbsp;&nbsp;&nbsp;&nbsp; filtering&nbsp; options (e.g. excluding hosts
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; that are down),&nbsp; and/or&nbsp; host&nbsp; selection&nbsp; options&nbsp;&nbsp;&nbsp; (e.g.&nbsp; -a
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; selects&nbsp; all&nbsp; nodes&nbsp; from a local config file).&nbsp; By default,
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; pdcp requires at least one&nbsp;&nbsp;&nbsp; "rcmd" module to&nbsp; be&nbsp; loaded&nbsp; (to
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; provide the channel for remote copy).
    <br>
    <br>
    <br>
REVERSE&nbsp;&nbsp;&nbsp; PDCP
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; rpdcp performs a reverse parallel copy.&nbsp; Rather than copying
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; files to remote hosts, files are retrieved&nbsp;&nbsp;&nbsp; from remote hosts
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; and stored&nbsp;&nbsp;&nbsp; locally.&nbsp; All directories or files retrieved will
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; be&nbsp;&nbsp;&nbsp;&nbsp; stored&nbsp;&nbsp;&nbsp;&nbsp; with&nbsp; their&nbsp; remote&nbsp; hostname&nbsp;&nbsp;&nbsp; appended&nbsp; to&nbsp;
the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; filename.&nbsp;&nbsp;&nbsp; The destination&nbsp;&nbsp;&nbsp; file must&nbsp; be&nbsp; a&nbsp; directory&nbsp; when
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; this option is used.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; In&nbsp;&nbsp;&nbsp; other respects,&nbsp;&nbsp;&nbsp; rpdcp is exactly like pdcp,&nbsp; and&nbsp; further
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; statements&nbsp;&nbsp;&nbsp;&nbsp; regarding&nbsp; pdcp&nbsp; in&nbsp; this&nbsp; manual&nbsp; also apply to
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; rpdcp.
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
pdsh-2.18&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last change: solaris2.11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
User Commands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdsh(1)
    <br>
    <br>
    <br>
    <br>
RCMD MODULES
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; The method&nbsp;&nbsp;&nbsp; by which pdcp connects to&nbsp; remote&nbsp; hosts&nbsp; may&nbsp; be
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; selected at runtime using the -R option (See OPTIONS below).
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; This functionality&nbsp;&nbsp;&nbsp; is ultimately implemented via dynamically
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; loadable&nbsp; modules,&nbsp;&nbsp;&nbsp;&nbsp; and so&nbsp;&nbsp;&nbsp; the list of available options may
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; be&nbsp;&nbsp;&nbsp; different from installation to installation.&nbsp; A&nbsp;&nbsp;&nbsp;&nbsp; list&nbsp; of
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; currently&nbsp;&nbsp;&nbsp; available&nbsp; rcmd&nbsp;&nbsp;&nbsp; modules&nbsp;&nbsp;&nbsp; is printed when&nbsp;&nbsp;&nbsp;
using any
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; of&nbsp;&nbsp;&nbsp; the -h,&nbsp;&nbsp;&nbsp; -V, or -L options. The default rcmd&nbsp; module&nbsp; will
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; also be displayed with the&nbsp;&nbsp;&nbsp; -h and -V options.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; A list of rcmd modules currently distributed with pdcp&nbsp; fol-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; lows.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; rsh&nbsp;&nbsp;&nbsp;&nbsp; Uses an internal, thread-safe implementation of&nbsp; BSD
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; rcmd(3)&nbsp; to&nbsp; run&nbsp; commands&nbsp;&nbsp;&nbsp; using the standard rsh(1)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; protocol.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; ssh&nbsp;&nbsp;&nbsp;&nbsp; Uses a variant of popen(3)&nbsp;&nbsp;&nbsp; to run multiple&nbsp;&nbsp;&nbsp; copies of
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the ssh(1)&nbsp;&nbsp;&nbsp; command.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; mrsh&nbsp;&nbsp;&nbsp; This module uses the&nbsp; mrsh(1)&nbsp; protocol&nbsp; to&nbsp; execute
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; jobs&nbsp; on&nbsp; remote&nbsp; hosts.&nbsp;&nbsp;&nbsp; The&nbsp; mrsh protocol uses&nbsp;&nbsp;&nbsp; a
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; credential&nbsp;&nbsp;&nbsp; based authentication, forgoing&nbsp;&nbsp;&nbsp; the&nbsp; need
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to&nbsp;&nbsp;&nbsp;&nbsp; allocate&nbsp; reserved&nbsp; ports.&nbsp; In&nbsp;&nbsp;&nbsp; other aspects, it
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; acts just like rsh.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; krb4&nbsp;&nbsp;&nbsp; The krb4 module allows users to execute remote&nbsp; com-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mands after authenticating&nbsp;&nbsp;&nbsp; with kerberos. Of course,
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the remote&nbsp;&nbsp;&nbsp; rshd daemons must be kerberized.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; xcpu&nbsp;&nbsp;&nbsp; The xcpu module uses the&nbsp; xcpu&nbsp; service&nbsp; to&nbsp; execute
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; remote commands.
    <br>
    <br>
    <br>
OPTIONS
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; The list of available pdcp&nbsp;&nbsp;&nbsp; options&nbsp;&nbsp;&nbsp; is determined at&nbsp; runtime
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; by&nbsp;&nbsp;&nbsp;&nbsp; supplementing the list&nbsp;&nbsp;&nbsp; of standard pdcp options with any
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; options provided by loaded&nbsp;&nbsp;&nbsp; rcmd and misc modules.&nbsp;&nbsp;&nbsp;&nbsp; In&nbsp; some
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; cases,&nbsp; options&nbsp; provided&nbsp;&nbsp;&nbsp; by modules may conflict&nbsp;&nbsp;&nbsp; with each
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; other. In these cases, the&nbsp;&nbsp;&nbsp; modules&nbsp;&nbsp;&nbsp; are incompatible and&nbsp; the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; first module loaded wins.
    <br>
    <br>
    <br>
Standard target&nbsp;&nbsp;&nbsp; nodelist options
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -w&nbsp;&nbsp;&nbsp; host,host,...
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Target the specified list of hosts. Do not use with any
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; other&nbsp;&nbsp;&nbsp;&nbsp; node&nbsp; selection options (e.g. -a, -g if they are
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; available).&nbsp; No&nbsp; spaces&nbsp; are&nbsp;&nbsp;&nbsp; allowed&nbsp;&nbsp;&nbsp;&nbsp; in&nbsp; the&nbsp;&nbsp; comma-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; separated&nbsp; list.&nbsp;&nbsp; A&nbsp;&nbsp;&nbsp; list&nbsp; consisting&nbsp; of a single `-'
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; character causes the&nbsp;&nbsp;&nbsp; target&nbsp;&nbsp;&nbsp; hosts&nbsp; to&nbsp; be&nbsp; read&nbsp; from
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; stdin, one per line. The host&nbsp;&nbsp;&nbsp; list may contain hostlist
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; expressions&nbsp; of&nbsp; the&nbsp;&nbsp;&nbsp; form&nbsp; ``host[1-5,7]''.&nbsp;&nbsp;&nbsp; For&nbsp; more
    <br>
    <br>
    <br>
    <br>
pdsh-2.18&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last change: solaris2.11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
User Commands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdsh(1)
    <br>
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; information about the&nbsp;&nbsp;&nbsp; hostlist format, see the HOSTLIST
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; EXPRESSIONS section below.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -x&nbsp;&nbsp;&nbsp; host,host,...
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Exclude the specified&nbsp;&nbsp;&nbsp; hosts. May be specified&nbsp;&nbsp;&nbsp;&nbsp; in&nbsp; con-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; junction with&nbsp;&nbsp;&nbsp; other target node list options such as -a
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and -g (when available). Hostlists may also&nbsp; be&nbsp; speci-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; fied&nbsp;&nbsp;&nbsp; to the -x option (see HOSTLIST EXPRESSIONS secion
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; below).
    <br>
    <br>
    <br>
Standard pdcp options
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -h&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Output usage menu and&nbsp;&nbsp;&nbsp; quit. A&nbsp;&nbsp;&nbsp; list&nbsp; of&nbsp; available&nbsp;
rcmd
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; modules&nbsp; will&nbsp;&nbsp;&nbsp;&nbsp; be&nbsp; printed at&nbsp;&nbsp;&nbsp; the end&nbsp;&nbsp;&nbsp; of the usage mes-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; sage.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -q&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List option values and the&nbsp; target&nbsp; nodelist&nbsp;&nbsp;&nbsp; and&nbsp; exit
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; without action.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -b&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Disable ctrl-C status&nbsp;&nbsp;&nbsp; feature&nbsp;&nbsp;&nbsp; so that&nbsp;&nbsp;&nbsp; a&nbsp; single&nbsp;
ctrl-C
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; kills&nbsp;&nbsp;&nbsp; parallel copy. (Batch Mode)
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -r&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Copy directories recursively.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -p&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Preserve modification&nbsp;&nbsp;&nbsp; time and modes.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -e&nbsp;&nbsp;&nbsp; PATH
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Explicitly specify path to remote pdcp&nbsp; binary&nbsp; instead
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of using the locally executed&nbsp;&nbsp;&nbsp; path.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -l&nbsp;&nbsp;&nbsp; user
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This option may be used to copy files&nbsp;&nbsp;&nbsp; as another&nbsp; user,
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; subject&nbsp; to authorization. For BSD rcmd, this&nbsp;&nbsp;&nbsp; means the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; invoking user&nbsp;&nbsp;&nbsp; and system must&nbsp;&nbsp;&nbsp; be listed in&nbsp; the&nbsp; user's
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .rhosts file (even for root).
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -t&nbsp;&nbsp;&nbsp; seconds
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Set the connect timeout. Default is 10 seconds.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -f&nbsp;&nbsp;&nbsp; number
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Set the maximum number of simultaneous remote&nbsp;&nbsp;&nbsp; copies to
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; number.&nbsp; The default is 32.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -R&nbsp;&nbsp;&nbsp; name
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Set rcmd module to name. This&nbsp;&nbsp;&nbsp; option may&nbsp; also&nbsp; be&nbsp; set
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; via&nbsp; the PDSH_RCMD_TYPE environment variable.&nbsp;&nbsp;&nbsp; A list of
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; available rcmd modules may be&nbsp;&nbsp;&nbsp; obtained via&nbsp; either&nbsp; the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -h or&nbsp;&nbsp;&nbsp; -L options.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -R&nbsp;&nbsp;&nbsp; name
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Set rcmd module to name. This&nbsp;&nbsp;&nbsp; option may&nbsp; also&nbsp; be&nbsp; set
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; via&nbsp; the PDSH_RCMD_TYPE environment variable.&nbsp;&nbsp;&nbsp; A list of
    <br>
    <br>
    <br>
    <br>
pdsh-2.18&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last change: solaris2.11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
User Commands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdsh(1)
    <br>
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; available rcmd modules may be&nbsp;&nbsp;&nbsp; obtained via&nbsp; either&nbsp; the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -h or&nbsp;&nbsp;&nbsp; -L options.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -L&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List info on all loaded pdcp modules and quit.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -d&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Include more complete&nbsp;&nbsp;&nbsp;&nbsp; thread&nbsp;&nbsp;&nbsp;&nbsp; status&nbsp;&nbsp;&nbsp;&nbsp; when&nbsp;
SIGINT&nbsp; is
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; received,&nbsp; and display connect and command time statis-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tics on stderr when done.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -V&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Output pdcp version information,&nbsp; along&nbsp; with&nbsp;&nbsp;&nbsp;&nbsp; list&nbsp; of
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; currently loaded modules, and&nbsp;&nbsp;&nbsp; exit.
    <br>
    <br>
    <br>
    <br>
HOSTLIST EXPRESSIONS
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; As&nbsp;&nbsp;&nbsp; noted in sections above, pdcp accepts ranges of&nbsp;&nbsp;&nbsp; hostnames
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; in&nbsp;&nbsp;&nbsp;&nbsp; the general form: prefix[n-m,l-k,...],&nbsp;&nbsp;&nbsp; where n&nbsp;&nbsp;&nbsp; &lt; m
and&nbsp;&nbsp;&nbsp; l
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; &lt; k, etc.,&nbsp;&nbsp;&nbsp; as an alternative to&nbsp; explicit&nbsp;&nbsp;&nbsp; lists&nbsp; of&nbsp;
hosts.
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; This&nbsp; form&nbsp;&nbsp;&nbsp;&nbsp; should&nbsp;&nbsp;&nbsp;&nbsp; not&nbsp; be confused with regular expression
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; character classes (also denoted&nbsp; by&nbsp; ``[]'').&nbsp; For&nbsp;&nbsp;&nbsp;&nbsp; example,
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; foo[19]&nbsp;&nbsp; does&nbsp; not&nbsp; represent&nbsp; foo1&nbsp; or&nbsp; foo9,&nbsp; but&nbsp; rather
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; represents&nbsp;&nbsp;&nbsp; a degenerate range: foo19.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; This range&nbsp;&nbsp;&nbsp; syntax is meant&nbsp;&nbsp;&nbsp; only as&nbsp;&nbsp;&nbsp; a convenience on
clusters
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; with&nbsp; a&nbsp; prefixNN&nbsp;&nbsp;&nbsp; naming&nbsp;&nbsp;&nbsp; convention&nbsp; and&nbsp;&nbsp;&nbsp;&nbsp; specification
of
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; ranges should&nbsp; not&nbsp;&nbsp;&nbsp;&nbsp; be&nbsp; considered&nbsp;&nbsp;&nbsp;&nbsp; necessary&nbsp; --&nbsp;&nbsp;&nbsp; the&nbsp;
list
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; foo1,foo9&nbsp;&nbsp;&nbsp; could&nbsp; be&nbsp; specified&nbsp; as&nbsp; such,&nbsp;&nbsp;&nbsp;&nbsp; or&nbsp; by&nbsp;&nbsp;&nbsp; the
range
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; foo[1,9].
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; Some examples of range usage follow:
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; Copy /etc/hosts to&nbsp;&nbsp;&nbsp; foo01,foo02,...,foo05
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; pdcp -w foo[01-05] /etc/hosts /etc
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; Copy /etc/hosts to&nbsp;&nbsp;&nbsp; foo7,foo9,foo10
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; pdcp -w foo[7,9-10] /etc/hosts&nbsp;&nbsp;&nbsp; /etc
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; Copy /etc/hosts to&nbsp;&nbsp;&nbsp; foo0,foo4,foo5
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdcp -w foo[0-5] -x foo[1-3] /etc/hosts /etc
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; As&nbsp;&nbsp;&nbsp; a reminder to the&nbsp; reader,&nbsp; some&nbsp; shells&nbsp; will&nbsp;&nbsp;&nbsp; interpret
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; brackets&nbsp; ('['&nbsp; and ']') for pattern matching.&nbsp; Depending on
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; your shell, it may&nbsp;&nbsp;&nbsp; be&nbsp; necessary&nbsp; to&nbsp; enclose&nbsp; ranged&nbsp; lists
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; within&nbsp; quotes.&nbsp;&nbsp; For&nbsp; example,&nbsp; in&nbsp; tcsh,&nbsp;&nbsp;&nbsp; the first example
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; above should be executed as:
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; pdcp -w "foo[01-05]" /etc/hosts /etc
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
pdsh-2.18&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last change: solaris2.11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
User Commands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdsh(1)
    <br>
    <br>
    <br>
    <br>
ORIGIN
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; Pdsh/pdcp was originally a&nbsp;&nbsp;&nbsp; rewrite&nbsp;&nbsp;&nbsp; of IBM dsh(1) by Jim Gar-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; lick&nbsp; <a class="moz-txt-link-rfc2396E" href="mailto:garlick@llnl.gov">&lt;garlick@llnl.gov&gt;</a>&nbsp; on LLNL's ASCI Blue-Pacific IBM SP
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; system.&nbsp; It is now&nbsp;&nbsp;&nbsp; also used on Linux clusters at LLNL.
    <br>
    <br>
    <br>
LIMITATIONS
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; When using&nbsp;&nbsp;&nbsp; ssh for&nbsp;&nbsp;&nbsp; remote execution, stderr&nbsp; of&nbsp; ssh&nbsp; to&nbsp; be
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; folded&nbsp; in&nbsp;&nbsp;&nbsp; with that of the remote&nbsp;&nbsp;&nbsp; command.&nbsp; When invoked by
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; pdcp, it is not possible for ssh to prompt&nbsp;&nbsp;&nbsp; for&nbsp; confirmation
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; if&nbsp;&nbsp;&nbsp;&nbsp; a host&nbsp;&nbsp;&nbsp; key changes, prompt for&nbsp;&nbsp;&nbsp; passwords if RSA keys
are
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; not configured properly, etc..&nbsp; Finally, the connect timeout
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; is&nbsp;&nbsp;&nbsp;&nbsp; only&nbsp; adjustable with ssh when&nbsp;&nbsp;&nbsp; the underlying ssh imple-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; mentation supports&nbsp;&nbsp;&nbsp; it, and&nbsp;&nbsp;&nbsp; pdsh has been built&nbsp; to&nbsp;&nbsp;&nbsp;&nbsp; use&nbsp;
the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; correct option.
    <br>
    <br>
    <br>
ATTRIBUTES
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; See attributes(5) for descriptions&nbsp;&nbsp;&nbsp; of the&nbsp;&nbsp;&nbsp; following&nbsp; attri-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; butes:
    <br>
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; ____________________________________________________________
    <br>
&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATTRIBUTE TYPE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATTRIBUTE VALUE&nbsp;&nbsp;&nbsp; |
    <br>
&nbsp;&nbsp;&nbsp; |_____________________________|_____________________________|
    <br>
&nbsp;&nbsp;&nbsp; | Availability&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | SUNWpdsh&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
    <br>
&nbsp;&nbsp;&nbsp; |_____________________________|_____________________________|
    <br>
&nbsp;&nbsp;&nbsp; | Interface&nbsp;&nbsp;&nbsp; Stability&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
    <br>
&nbsp;&nbsp;&nbsp; |_____________________________|_____________________________|
    <br>
    <br>
    <br>
SEE ALSO
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; pdsh(1)
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
pdsh-2.18&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last change: solaris2.11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5
    <br>
    <br>
    <br>
&nbsp;
------------------------------------------------------------------------
    <br>
    <br>
    <br>
    <br>
    <br>
User Commands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdsh(1)
    <br>
    <br>
    <br>
    <br>
NAME
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; pdsh - issue commands to groups of&nbsp;&nbsp;&nbsp; hosts in parallel
    <br>
    <br>
    <br>
SYNOPSIS
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; pdsh [options]... command
    <br>
    <br>
    <br>
DESCRIPTION
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; pdsh is a variant of&nbsp; the&nbsp;&nbsp;&nbsp; rsh(1)&nbsp;&nbsp;&nbsp; command.&nbsp; Unlike&nbsp; rsh(1),
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; which&nbsp; runs&nbsp; commands&nbsp; on a single&nbsp;&nbsp;&nbsp; remote host, pdsh can run
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; multiple remote commands in parallel. pdsh&nbsp;&nbsp;&nbsp; uses&nbsp; a&nbsp;&nbsp;&nbsp;&nbsp; "sliding
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; window"&nbsp; (or fanout) of threads to&nbsp;&nbsp;&nbsp; conserve resources on the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; initiating&nbsp;&nbsp;&nbsp; host while allowing some connections to&nbsp;&nbsp;&nbsp; time out.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; When pdsh receives&nbsp;&nbsp;&nbsp; SIGINT (ctrl-C), it lists the&nbsp; status&nbsp; of
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; current&nbsp; threads.&nbsp;&nbsp;&nbsp; A&nbsp; second&nbsp; SIGINT&nbsp; within one second ter-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; minates the program. Pending&nbsp; threads&nbsp; may&nbsp;&nbsp;&nbsp;&nbsp; be&nbsp; canceled&nbsp; by
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; issuing ctrl-Z within one second of ctrl-C.&nbsp; Pending threads
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; are those that have not yet been initiated, or are&nbsp;&nbsp;&nbsp; still&nbsp; in
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; the process of connecting to the remote host.
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; If&nbsp;&nbsp;&nbsp; a remote command is not&nbsp;&nbsp;&nbsp; specified on&nbsp; the&nbsp; command&nbsp; line,
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; pdsh&nbsp; runs&nbsp;&nbsp;&nbsp; interactively, prompting for commands and execut-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; ing them when terminated with a carriage return. In interac-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; tive&nbsp; mode,&nbsp; target nodes that time out on&nbsp;&nbsp;&nbsp; the first command
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; are not contacted for subsequent commands,&nbsp;&nbsp;&nbsp; and commands pre-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; fixed&nbsp; with&nbsp; an&nbsp; exclamation&nbsp; point&nbsp; will be executed on the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; local system.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; The core functionality of pdsh may&nbsp;&nbsp;&nbsp; be supplemented&nbsp;&nbsp;&nbsp; by dynam-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; ically&nbsp; loadable modules. The modules may provide a new con-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; nection protocol (replacing the&nbsp; standard&nbsp;&nbsp;&nbsp; rcmd(3)&nbsp;&nbsp;&nbsp;&nbsp; protocol
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; used by rsh(1)), filtering&nbsp;&nbsp;&nbsp; options&nbsp;&nbsp;&nbsp; (e.g. removing hosts that
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; are "down"&nbsp;&nbsp;&nbsp; from the&nbsp; target&nbsp; list),&nbsp; and/or&nbsp; host&nbsp;&nbsp;&nbsp; selection
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; options&nbsp; (e.g.,&nbsp; -a&nbsp; selects&nbsp; all hosts from a configuration
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; file.). By&nbsp;&nbsp;&nbsp; default, pdsh&nbsp; must&nbsp; have&nbsp; at&nbsp; least&nbsp; one&nbsp; "rcmd"
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; module&nbsp; loaded. See the RCMD MODULES section for more infor-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; mation.
    <br>
    <br>
    <br>
RCMD MODULES
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; The method&nbsp;&nbsp;&nbsp; by which pdsh runs commands on remote&nbsp; hosts&nbsp; may
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; be&nbsp;&nbsp;&nbsp;&nbsp; selected&nbsp; at&nbsp; runtime&nbsp;&nbsp;&nbsp; using&nbsp; the -R option (See OPTIONS
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; below).&nbsp; This functionality is&nbsp; ultimately&nbsp;&nbsp;&nbsp;&nbsp; implemented&nbsp; via
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; dynamically&nbsp; loadable&nbsp; modules, and so the&nbsp;&nbsp;&nbsp; list of&nbsp;&nbsp;&nbsp; available
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; options may be different from installation&nbsp;&nbsp;&nbsp; to&nbsp; installation.
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; A&nbsp;&nbsp;&nbsp; list&nbsp; of currently available rcmd modules is printed when
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; using any of the -h, -V, or -L&nbsp; options.&nbsp; The&nbsp; default&nbsp; rcmd
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; module will also be displayed with&nbsp;&nbsp;&nbsp; the -h and -V options.
    <br>
    <br>
    <br>
    <br>
    <br>
pdsh-2.18&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last change: solaris2.11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
User Commands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdsh(1)
    <br>
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; A list of rcmd modules currently distributed with pdsh&nbsp; fol-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; lows.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; rsh&nbsp;&nbsp;&nbsp;&nbsp; Uses an internal, thread-safe implementation of&nbsp; BSD
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; rcmd(3)&nbsp; to&nbsp; run&nbsp; commands&nbsp;&nbsp;&nbsp; using the standard rsh(1)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; protocol.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; exec&nbsp;&nbsp;&nbsp; Executes an arbitrary command for each target&nbsp; host.
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The&nbsp; first&nbsp;&nbsp;&nbsp; of the pdsh remote arguments is&nbsp;&nbsp;&nbsp; the local
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; command to&nbsp;&nbsp;&nbsp; execute, followed by&nbsp; any&nbsp; further&nbsp; argu-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ments.&nbsp; Some simple parameters are&nbsp;&nbsp;&nbsp; substitued on the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; command line, including %h&nbsp;&nbsp;&nbsp; for the&nbsp;&nbsp;&nbsp; target&nbsp;&nbsp;&nbsp; hostname,
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; %u&nbsp;&nbsp;&nbsp;&nbsp; for&nbsp; the&nbsp; remote username, and&nbsp;&nbsp;&nbsp; %n for the remote
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; rank [0-n]&nbsp;&nbsp;&nbsp; (To get&nbsp;&nbsp;&nbsp; a literal % use&nbsp;&nbsp;&nbsp; %%).&nbsp;&nbsp; For&nbsp; exam-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ple,&nbsp; the&nbsp;&nbsp;&nbsp; following&nbsp; would&nbsp; duplicate using the ssh
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; module to run hostname(1) across&nbsp; the&nbsp; hosts&nbsp; foo[0-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10]:
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdsh -R&nbsp;&nbsp;&nbsp; exec -w&nbsp;&nbsp;&nbsp; foo[0-10] ssh -x -l %u %h hostname
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and this command line would run grep(1) in&nbsp;&nbsp;&nbsp;&nbsp; parallel
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; across the&nbsp;&nbsp;&nbsp; files console.foo[0-10]:
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdsh -R&nbsp;&nbsp;&nbsp; exec -w&nbsp;&nbsp;&nbsp; foo[0-10] grep BUG console.%h
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; ssh&nbsp;&nbsp;&nbsp;&nbsp; Uses a variant of popen(3)&nbsp;&nbsp;&nbsp; to run multiple&nbsp;&nbsp;&nbsp; copies of
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the ssh(1)&nbsp;&nbsp;&nbsp; command.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; mrsh&nbsp;&nbsp;&nbsp; This module uses the&nbsp; mrsh(1)&nbsp; protocol&nbsp; to&nbsp; execute
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; jobs&nbsp; on&nbsp; remote&nbsp; hosts.&nbsp;&nbsp;&nbsp; The&nbsp; mrsh protocol uses&nbsp;&nbsp;&nbsp; a
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; credential&nbsp;&nbsp;&nbsp; based authentication, forgoing&nbsp;&nbsp;&nbsp; the&nbsp; need
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to&nbsp;&nbsp;&nbsp;&nbsp; allocate&nbsp; reserved&nbsp; ports.&nbsp; In&nbsp;&nbsp;&nbsp; other aspects, it
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; acts just like rsh. Remote&nbsp;&nbsp;&nbsp;&nbsp; nodes&nbsp;&nbsp;&nbsp; must&nbsp; be&nbsp; running
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mrshd(8) in order for the mrsh module to work.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; qsh&nbsp;&nbsp;&nbsp;&nbsp; Allows pdsh to execute MPI&nbsp;&nbsp;&nbsp; jobs over&nbsp; QsNet.&nbsp; Qshell
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; propagates&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the&nbsp; current&nbsp;&nbsp;&nbsp; working&nbsp;&nbsp;&nbsp;&nbsp; directory,&nbsp; pdsh
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; environment, and Elan&nbsp; capabilities&nbsp; to&nbsp; the&nbsp; remote
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; process. The following environment&nbsp;&nbsp;&nbsp; variable are also
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; appended to the environment:&nbsp; RMS_RANK,&nbsp; RMS_NODEID,
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; RMS_PROCID,&nbsp; RMS_NNODES,&nbsp; and RMS_NPROCS. Since pdsh
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; needs to run setuid root for qshell support,&nbsp; qshell
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; does&nbsp;&nbsp;&nbsp; not&nbsp;&nbsp;&nbsp; directly&nbsp;&nbsp; support&nbsp;&nbsp;&nbsp;&nbsp; propagation&nbsp;&nbsp; of
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LD_LIBRARY_PATH&nbsp;&nbsp; and&nbsp;&nbsp; LD_PREOPEN.&nbsp;&nbsp; Instead&nbsp;&nbsp;&nbsp; the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; QSHELL_REMOTE_LD_LIBRARY_PATH&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; QSHELL_REMOTE_LD_PREOPEN environment variables&nbsp; will
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; may&nbsp; be used and will be remapped to LD_LIBRARY_PATH
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and LD_PREOPEN by the qshell daemon if set.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; mqsh&nbsp;&nbsp;&nbsp; Similar&nbsp; to&nbsp; qshell,&nbsp; but&nbsp;&nbsp;&nbsp; uses&nbsp; the&nbsp; mrsh&nbsp;&nbsp;&nbsp;&nbsp; protocol
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; instead of&nbsp;&nbsp;&nbsp; the rsh&nbsp;&nbsp;&nbsp; protocol.
    <br>
    <br>
    <br>
    <br>
pdsh-2.18&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last change: solaris2.11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
User Commands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdsh(1)
    <br>
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; krb4&nbsp;&nbsp;&nbsp; The krb4 module allows users to execute remote&nbsp; com-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mands after authenticating&nbsp;&nbsp;&nbsp; with kerberos. Of course,
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the remote&nbsp;&nbsp;&nbsp; rshd daemons must be kerberized.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; xcpu&nbsp;&nbsp;&nbsp; The xcpu module uses the&nbsp; xcpu&nbsp; service&nbsp; to&nbsp; execute
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; remote commands.
    <br>
    <br>
    <br>
OPTIONS
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; The list of available options is determined&nbsp; at&nbsp; runtime&nbsp; by
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; supplementing&nbsp; the&nbsp;&nbsp;&nbsp;&nbsp; list&nbsp; of&nbsp; standard pdsh options with any
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; options provided by loaded&nbsp;&nbsp;&nbsp; rcmd and misc modules.&nbsp;&nbsp;&nbsp;&nbsp; In&nbsp; some
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; cases,&nbsp; options&nbsp; provided&nbsp;&nbsp;&nbsp; by modules may conflict&nbsp;&nbsp;&nbsp; with each
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; other. In these cases, the&nbsp;&nbsp;&nbsp; modules&nbsp;&nbsp;&nbsp; are incompatible and&nbsp; the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; first module loaded wins.
    <br>
    <br>
    <br>
Standard target&nbsp;&nbsp;&nbsp; nodelist options
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -w&nbsp;&nbsp;&nbsp; [rcmd_type:][user@]host,host,...
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Target the specified list of hosts. Do not use with any
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; other&nbsp;&nbsp;&nbsp;&nbsp; node&nbsp; selection options (e.g. -a, -g if they are
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; available).&nbsp; No&nbsp; spaces&nbsp; are&nbsp;&nbsp;&nbsp; allowed&nbsp;&nbsp;&nbsp;&nbsp; in&nbsp; the&nbsp;&nbsp; comma-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; separated&nbsp; list.&nbsp;&nbsp; A&nbsp;&nbsp;&nbsp; list&nbsp; consisting&nbsp; of a single `-'
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; character causes the&nbsp;&nbsp;&nbsp; target&nbsp;&nbsp;&nbsp; hosts&nbsp; to&nbsp; be&nbsp; read&nbsp; from
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; stdin, one per line. The host&nbsp;&nbsp;&nbsp; list may contain hostlist
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; expressions&nbsp; of&nbsp; the&nbsp;&nbsp;&nbsp; form&nbsp; ``host[1-5,7]''.&nbsp;&nbsp;&nbsp; For&nbsp; more
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; information about the&nbsp;&nbsp;&nbsp; hostlist format, see the HOSTLIST
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; EXPRESSIONS section below. A list of hosts may also&nbsp; be
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; preceded&nbsp; by "user@" to specify a remote username other
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; than the default, or "rcmd_type:" to specify an&nbsp; alter-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; nate&nbsp;&nbsp;&nbsp; rcmd&nbsp; connection&nbsp; type for these hosts.&nbsp;&nbsp;&nbsp; When used
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; together, the&nbsp;&nbsp;&nbsp; rcmd type must be specified&nbsp; first,&nbsp; e.g.
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <a class="moz-txt-link-rfc2396E" href="ssh:user1@host0">"ssh:user1@host0"</a>&nbsp; would use ssh to connect to host0 as
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; user "user1."
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -x&nbsp;&nbsp;&nbsp; host,host,...
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Exclude the specified&nbsp;&nbsp;&nbsp; hosts. May be specified&nbsp;&nbsp;&nbsp;&nbsp; in&nbsp; con-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; junction with&nbsp;&nbsp;&nbsp; other target node list options such as -a
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and -g (when available). Hostlists may also&nbsp; be&nbsp; speci-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; fied&nbsp;&nbsp;&nbsp; to&nbsp; the&nbsp;&nbsp;&nbsp;&nbsp; -x&nbsp; option (see the HOSTLIST EXPRESSIONS
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; section below).
    <br>
    <br>
    <br>
Standard pdsh options
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -S&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Return the largest of&nbsp;&nbsp;&nbsp; the remote command return values.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -h&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Output usage menu and&nbsp;&nbsp;&nbsp; quit. A&nbsp;&nbsp;&nbsp; list&nbsp; of&nbsp; available&nbsp;
rcmd
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; modules&nbsp; will&nbsp;&nbsp;&nbsp;&nbsp; also&nbsp; be printed at the end of&nbsp;&nbsp;&nbsp; the usage
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; message.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -s&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Only on AIX, separate&nbsp;&nbsp;&nbsp; remote command stderr and&nbsp; stdout
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; into two sockets.
    <br>
    <br>
    <br>
    <br>
pdsh-2.18&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last change: solaris2.11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
User Commands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdsh(1)
    <br>
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -q&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List option values and the&nbsp; target&nbsp; nodelist&nbsp;&nbsp;&nbsp; and&nbsp; exit
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; without action.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -b&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Disable ctrl-C status&nbsp;&nbsp;&nbsp; feature&nbsp;&nbsp;&nbsp; so that&nbsp;&nbsp;&nbsp; a&nbsp; single&nbsp;
ctrl-C
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; kills&nbsp;&nbsp;&nbsp; parallel job. (Batch Mode)
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -l&nbsp;&nbsp;&nbsp; user
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This option may be&nbsp; used&nbsp; to&nbsp;&nbsp;&nbsp; run&nbsp; remote&nbsp; commands&nbsp; as
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; another&nbsp; user,&nbsp; subject to authorization. For&nbsp;&nbsp;&nbsp; BSD rcmd,
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; this means the invoking user and system must be&nbsp; listed
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in the user's&nbsp;&nbsp;&nbsp; .rhosts&nbsp;&nbsp;&nbsp; file (even for root).
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -t&nbsp;&nbsp;&nbsp; seconds
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Set the connect timeout. Default is 10 seconds.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -u&nbsp;&nbsp;&nbsp; seconds
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Set a&nbsp;&nbsp;&nbsp; limit on the amount of time a remote&nbsp; command&nbsp; is
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; allowed&nbsp; to&nbsp; execute.&nbsp;&nbsp;&nbsp;&nbsp; Default is no limit. See note in
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LIMITATIONS if using -u with ssh.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -f&nbsp;&nbsp;&nbsp; number
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Set the maximum number of simultaneous remote&nbsp;&nbsp;&nbsp;&nbsp; commands
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to number.&nbsp; The default is 32.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -R&nbsp;&nbsp;&nbsp; name
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Set rcmd module to name. This&nbsp;&nbsp;&nbsp; option may&nbsp; also&nbsp; be&nbsp; set
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; via&nbsp; the PDSH_RCMD_TYPE environment variable.&nbsp;&nbsp;&nbsp; A list of
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; available rcmd modules may be&nbsp;&nbsp;&nbsp; obtained via the -h,&nbsp; -V,
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; or&nbsp; -L&nbsp; options.&nbsp; The&nbsp;&nbsp;&nbsp; default&nbsp;&nbsp;&nbsp; will be&nbsp;&nbsp;&nbsp; listed with -h or
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -V.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -L&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; List info on all loaded pdsh modules and quit.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -N&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Disable hostname: prefix on lines of output.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -d&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Include more complete&nbsp;&nbsp;&nbsp;&nbsp; thread&nbsp;&nbsp;&nbsp;&nbsp; status&nbsp;&nbsp;&nbsp;&nbsp; when&nbsp;
SIGINT&nbsp; is
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; received,&nbsp; and display connect and command time statis-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tics on stderr when done.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -V&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Output pdsh version information,&nbsp; along&nbsp; with&nbsp;&nbsp;&nbsp;&nbsp; list&nbsp; of
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; currently loaded modules, and&nbsp;&nbsp;&nbsp; exit.
    <br>
    <br>
    <br>
qsh/mqsh module&nbsp;&nbsp;&nbsp; options
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -n&nbsp;&nbsp;&nbsp; tasks_per_node
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Set the number of tasks spawned per node. Default is 1.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -m&nbsp;&nbsp;&nbsp; block |&nbsp;&nbsp;&nbsp; cyclic
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Set block versus&nbsp; cyclic&nbsp; allocation&nbsp;&nbsp;&nbsp; of&nbsp; processes&nbsp; to
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; nodes. Default is block.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -r&nbsp;&nbsp;&nbsp; railmask
    <br>
    <br>
    <br>
    <br>
pdsh-2.18&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last change: solaris2.11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
User Commands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdsh(1)
    <br>
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Set the rail bitmask for a job on a&nbsp; multirail&nbsp; system.
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The&nbsp; default railmask&nbsp;&nbsp;&nbsp; is 1, which corresponds&nbsp;&nbsp;&nbsp; to rail&nbsp;&nbsp;&nbsp; 0
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; only.&nbsp;&nbsp;&nbsp; Each bit set in&nbsp;&nbsp;&nbsp; the argument to&nbsp;&nbsp;&nbsp; -r corresponds to
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a&nbsp; rail on the system, so a value of 2 would correspond
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to rail 1 only, and 3&nbsp;&nbsp;&nbsp; would indicate to use both rail&nbsp;&nbsp;&nbsp; 1
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and rail 0.
    <br>
    <br>
    <br>
machines module&nbsp;&nbsp;&nbsp; options
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -a&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Target all nodes from&nbsp;&nbsp;&nbsp; machines file.
    <br>
    <br>
    <br>
genders&nbsp;&nbsp;&nbsp; module options
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; In&nbsp;&nbsp;&nbsp; addition to the&nbsp;&nbsp;&nbsp;&nbsp; genders&nbsp; options&nbsp; presented&nbsp; below,&nbsp; the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; genders&nbsp; attribute&nbsp;&nbsp;&nbsp;&nbsp; pdsh_rcmd_type&nbsp;&nbsp;&nbsp;&nbsp; may&nbsp; also be used in the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; genders database to specify an alternate rcmd&nbsp; connect&nbsp; type
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; than the pdsh default in the genders file
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; host0 pdsh_rcmd_type=ssh
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; would cause pdsh to use ssh to connect to host0, even if rsh
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; were the default.&nbsp;&nbsp;&nbsp; This can be overridden on the commandline
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; with the "rcmd_type:host0"&nbsp;&nbsp;&nbsp; syntax.
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -A&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Target all nodes in genders&nbsp; database.&nbsp; The&nbsp; -A&nbsp; option
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; will target every host listed&nbsp;&nbsp;&nbsp; in genders -- if you want
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to omit some hosts by&nbsp;&nbsp;&nbsp; default, see the -a option below.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -a&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Target all nodes in genders database except those&nbsp; with
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the&nbsp; "pdsh_all_skip"&nbsp;&nbsp;&nbsp; attribute.&nbsp; This is shorthand for
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; running "pdsh&nbsp;&nbsp;&nbsp; -A -X pdsh_all_skip ..."
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -g&nbsp;&nbsp;&nbsp; attr[=val][,attr[=val],...]
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Target nodes that match any of&nbsp; the&nbsp; specified&nbsp; genders
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; attributes&nbsp; (with&nbsp; optional&nbsp; values).&nbsp;&nbsp;&nbsp; Conflicts with -a
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and -w options. This option targets the alternate host-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; names&nbsp;&nbsp;&nbsp; in the genders database&nbsp;&nbsp;&nbsp; by default. The&nbsp;&nbsp;&nbsp; -i option
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; provided by the genders module may be&nbsp;&nbsp;&nbsp; used to&nbsp;&nbsp;&nbsp; translate
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; these&nbsp;&nbsp;&nbsp;&nbsp; to&nbsp; the&nbsp; canonical&nbsp; genders&nbsp; hostnames.&nbsp; If&nbsp; the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; installed version of genders&nbsp;&nbsp;&nbsp; supports&nbsp; it,&nbsp; attributes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; supplied&nbsp; to&nbsp;&nbsp;&nbsp; -g&nbsp; may&nbsp;&nbsp;&nbsp;&nbsp; also&nbsp; take&nbsp; the&nbsp; form of genders
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; queries. Genders queries will&nbsp;&nbsp;&nbsp; query the&nbsp; genders&nbsp; data-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; base&nbsp;&nbsp;&nbsp; for&nbsp; the union,&nbsp;&nbsp;&nbsp; intersection, difference, or com-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; plement of genders&nbsp; attributes&nbsp; and&nbsp; values.&nbsp;&nbsp;&nbsp;&nbsp; The&nbsp; set
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; operation&nbsp; union&nbsp; is&nbsp;&nbsp;&nbsp; represented&nbsp; by&nbsp;&nbsp;&nbsp;&nbsp; two pipe symbols
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ('||'), intersection by two ampersand&nbsp;&nbsp;&nbsp;&nbsp; symbols&nbsp;
('&amp;&amp;'),
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; difference&nbsp; by two minus symbols ('--'), and complement
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; by a tilde ('~').&nbsp; Parentheses may be&nbsp;&nbsp;&nbsp;&nbsp; used&nbsp; to&nbsp; change
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the&nbsp; order&nbsp; of&nbsp; operations. See the nodeattr(1) manpage
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for examples of genders queries.
    <br>
    <br>
    <br>
    <br>
    <br>
pdsh-2.18&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last change: solaris2.11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 5
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
User Commands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdsh(1)
    <br>
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -X&nbsp;&nbsp;&nbsp; attr[=val][,attr[=val],...]
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Exclude nodes&nbsp;&nbsp;&nbsp; that match any of the&nbsp; specified&nbsp; genders
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; attributes&nbsp; (optionally&nbsp; with&nbsp;&nbsp;&nbsp; values).&nbsp; This option may
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; be used in combination&nbsp; with&nbsp;&nbsp;&nbsp; any&nbsp; other&nbsp; of&nbsp;&nbsp;&nbsp; the&nbsp; node
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; selection&nbsp; options&nbsp; (e.g.&nbsp; -w, -g, -a, -X may&nbsp;&nbsp;&nbsp; also take
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the form of genders queries. Please&nbsp; see&nbsp; documentation
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for&nbsp; the&nbsp; genders&nbsp; -g&nbsp;&nbsp;&nbsp; option for more&nbsp;&nbsp;&nbsp; information about
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; genders queries.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -i&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Request translation&nbsp; between&nbsp;&nbsp;&nbsp; canonical&nbsp; and&nbsp;&nbsp;&nbsp;
alternate
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; hostnames.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -F&nbsp;&nbsp;&nbsp; filename
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Read genders information from&nbsp;&nbsp;&nbsp; filename instead&nbsp; of&nbsp; the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; system default genders file.
    <br>
    <br>
    <br>
nodeupdown module options
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -v&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Eliminate target nodes that are&nbsp; considered&nbsp; "down"&nbsp; by
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; libnodeupdown.
    <br>
    <br>
    <br>
slurm module options
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; The slurm module&nbsp; allows&nbsp; pdsh&nbsp; to&nbsp;&nbsp;&nbsp;&nbsp; target&nbsp;&nbsp;&nbsp;&nbsp; nodes&nbsp;&nbsp;&nbsp; based&nbsp;
on
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; currently&nbsp;&nbsp;&nbsp; running&nbsp;&nbsp;&nbsp; SLURM jobs. The&nbsp;&nbsp;&nbsp; slurm module is&nbsp;&nbsp;&nbsp;
typically
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; called after all other node selection options have&nbsp;&nbsp;&nbsp; been pro-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; cessed,&nbsp; and if no&nbsp;&nbsp;&nbsp; nodes have been&nbsp;&nbsp;&nbsp; selected, the module will
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; attempt&nbsp; to&nbsp; read&nbsp;&nbsp;&nbsp; a&nbsp; running&nbsp; jobid&nbsp; from&nbsp;&nbsp;&nbsp;&nbsp; the&nbsp; SLURM_JOBID
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; environment&nbsp; variable&nbsp; (which&nbsp; is&nbsp;&nbsp;&nbsp; set&nbsp; when running under&nbsp;&nbsp;&nbsp; a
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; SLURM allocation).&nbsp;&nbsp;&nbsp; If SLURM_JOBID references an invalid job,
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; it&nbsp;&nbsp;&nbsp; will be&nbsp;&nbsp;&nbsp; silently ignored.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -j&nbsp;&nbsp;&nbsp; jobid[,jobid,...]
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Target list of nodes allocated to the&nbsp;&nbsp;&nbsp; SLURM job&nbsp; jobid.
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This option may be used multiple times to target multi-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ple SLURM jobs. The special argument "all" can be&nbsp; used
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to target all&nbsp;&nbsp;&nbsp; nodes running SLURM jobs, e.g.&nbsp;&nbsp;&nbsp; -j all.
    <br>
    <br>
    <br>
rms module options
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; The rms module allows pdsh&nbsp;&nbsp;&nbsp; to target nodes&nbsp;&nbsp;&nbsp; based on&nbsp; an&nbsp; RMS
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; resource. The rms module is typically called after&nbsp;&nbsp;&nbsp; all other
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; node selection options, and if no nodes have been&nbsp;&nbsp;&nbsp; selected,
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; the module&nbsp;&nbsp;&nbsp; will examine the RMS_RESOURCEID&nbsp;&nbsp;&nbsp; environment vari-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; able and attempt to set the target&nbsp;&nbsp;&nbsp;&nbsp; list&nbsp; of&nbsp; hosts&nbsp; to&nbsp; the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; nodes&nbsp; in&nbsp;&nbsp;&nbsp; the&nbsp; RMS&nbsp; resource.&nbsp; If&nbsp;&nbsp;&nbsp;&nbsp; an&nbsp; invalid&nbsp; resource is
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; denoted, the variable is silently ignored.
    <br>
    <br>
    <br>
SDR module options
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; The SDR module supports targeting hosts via the System&nbsp; Data
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; Repository&nbsp;&nbsp;&nbsp; on IBM SPs.
    <br>
    <br>
    <br>
    <br>
pdsh-2.18&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last change: solaris2.11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 6
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
User Commands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdsh(1)
    <br>
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -a&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Target all nodes in the SDR. The list&nbsp;&nbsp;&nbsp; is generated from
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the "reliable&nbsp;&nbsp;&nbsp; hostname" in the SDR by&nbsp;&nbsp;&nbsp; default.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -i&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Translate hostnames between reliable and initial in the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SDR, when applicable.&nbsp;&nbsp;&nbsp;&nbsp; If the&nbsp;&nbsp;&nbsp; a target hostname matches
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; either the initial or&nbsp;&nbsp;&nbsp; reliable hostname in the SDR, the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; alternate name will be substitued. Thus a list composed
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of initial hostnames will instead be&nbsp;&nbsp;&nbsp; replaced&nbsp; with&nbsp;&nbsp;&nbsp; a
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; list&nbsp;&nbsp;&nbsp; of&nbsp; reliable&nbsp; hostnames.&nbsp;&nbsp; For example,&nbsp;&nbsp;&nbsp; when used
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with -a above, all initial hostnames&nbsp;&nbsp;&nbsp; in&nbsp; the&nbsp;&nbsp;&nbsp;&nbsp; SDR&nbsp; are
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; targeted.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -v&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Do not target&nbsp;&nbsp;&nbsp; nodes that are marked as&nbsp; not&nbsp; responding
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in&nbsp; the&nbsp; SDR&nbsp;&nbsp;&nbsp; on the targeted&nbsp;&nbsp;&nbsp; interface. (If a hostname
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; does not appear in the SDR, then that&nbsp;&nbsp;&nbsp; name will&nbsp; remain
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in the target&nbsp;&nbsp;&nbsp; hostlist.)
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -G&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; In combination with -a, include all partitions.
    <br>
    <br>
    <br>
nodeattr module&nbsp;&nbsp;&nbsp; options
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; The nodeattr module supports access to the&nbsp;&nbsp;&nbsp; genders&nbsp;&nbsp;&nbsp;&nbsp; database
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; via&nbsp; the&nbsp; nodeattr(1) command. See&nbsp;&nbsp;&nbsp; the genders section above
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; for a list&nbsp;&nbsp;&nbsp; of support options with&nbsp;&nbsp;&nbsp; this module.&nbsp; The&nbsp; option
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; usage&nbsp; with&nbsp; the&nbsp; nodeattr&nbsp;&nbsp;&nbsp;&nbsp; module&nbsp;&nbsp;&nbsp;&nbsp; is&nbsp; the same as genders,
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; above, with the exception that the&nbsp;&nbsp;&nbsp; -i&nbsp; option&nbsp; may&nbsp;&nbsp;&nbsp;&nbsp; only&nbsp; be
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; used&nbsp; with&nbsp;&nbsp;&nbsp;&nbsp; -a&nbsp; or&nbsp;&nbsp;&nbsp; -g. NOTE: This module will only&nbsp;&nbsp;&nbsp; work
with
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; very old releases of genders where&nbsp;&nbsp;&nbsp; the&nbsp; nodeattr(1)&nbsp; command
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; supports&nbsp; the&nbsp; -r&nbsp;&nbsp;&nbsp; option,&nbsp;&nbsp;&nbsp; and before the libgenders API was
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; available.&nbsp;&nbsp;&nbsp; Users running newer versions of&nbsp;&nbsp;&nbsp; genders&nbsp;&nbsp;&nbsp; will
need
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; to&nbsp;&nbsp;&nbsp; use the&nbsp;&nbsp;&nbsp; genders&nbsp;&nbsp;&nbsp; module instead.
    <br>
    <br>
    <br>
dshgroup module&nbsp;&nbsp;&nbsp; options
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; The dshgroup module allows&nbsp;&nbsp;&nbsp; pdsh&nbsp; to&nbsp; use&nbsp; dsh&nbsp; (or&nbsp;&nbsp;&nbsp;&nbsp; Dancer's
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; shell)&nbsp;&nbsp; style&nbsp;&nbsp; group&nbsp;&nbsp; files&nbsp;&nbsp; from&nbsp;&nbsp; /etc/dsh/group/&nbsp;&nbsp; or
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; ~/.dsh/group/.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -g&nbsp;&nbsp;&nbsp; groupname,...
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Target nodes in dsh group&nbsp; file&nbsp; "groupname"&nbsp;&nbsp;&nbsp; found&nbsp; in
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; either&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ~/.dsh/group/groupname&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; or
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /etc/dsh/group/groupname.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -X&nbsp;&nbsp;&nbsp; groupname,...
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Exclude nodes&nbsp;&nbsp;&nbsp; in dsh group file "groupname."
    <br>
    <br>
    <br>
netgroup module&nbsp;&nbsp;&nbsp; options
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; The netgroup module allows&nbsp;&nbsp;&nbsp; pdsh&nbsp; to&nbsp; use&nbsp; standard&nbsp;&nbsp;&nbsp;&nbsp; netgroup
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; entries&nbsp; to&nbsp; build&nbsp;&nbsp;&nbsp;&nbsp; lists of target hosts.&nbsp;&nbsp;&nbsp; (/etc/netgroup or
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; NIS)
    <br>
    <br>
    <br>
    <br>
    <br>
pdsh-2.18&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last change: solaris2.11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 7
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
User Commands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdsh(1)
    <br>
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -g&nbsp;&nbsp;&nbsp; groupname,...
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Target nodes in netgroup "groupname."
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; -X&nbsp;&nbsp;&nbsp; groupname,...
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Exclude nodes&nbsp;&nbsp;&nbsp; in netgroup "groupname."
    <br>
    <br>
    <br>
ENVIRONMENT VARIABLES
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; PDSH_RCMD_TYPE
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Equivalent to&nbsp;&nbsp;&nbsp; the -R option, the value of this environ-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ment&nbsp;&nbsp;&nbsp; variable&nbsp; will&nbsp;&nbsp;&nbsp; be&nbsp; used&nbsp; to set the default rcmd
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; module for pdsh to use (e.g. ssh, rsh).
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; PDSH_SSH_ARGS
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Override the standard&nbsp;&nbsp;&nbsp; arguments that pdsh passes to the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ssh(1) command ("-2 -a -x").
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; PDSH_SSH_ARGS_APPEND
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Append additional options to the ssh(1) command invoked
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; by&nbsp; pdsh.&nbsp; For example, PDSH_SSH_ARGS_APPEND="-q" would
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; run ssh in quiet mode, or "-v" would increase&nbsp;&nbsp;&nbsp; the&nbsp; ver-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; bosity of ssh.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; WCOLL
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If no&nbsp;&nbsp;&nbsp; other node selection option is&nbsp;&nbsp;&nbsp; used,&nbsp; the&nbsp; WCOLL
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; environment&nbsp; variable&nbsp;&nbsp;&nbsp;&nbsp; may&nbsp; be&nbsp; set&nbsp; to a filename from
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; which&nbsp;&nbsp;&nbsp; a list of target hosts will&nbsp; be&nbsp;&nbsp;&nbsp;&nbsp; read.&nbsp;&nbsp;&nbsp; The&nbsp; file
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; should&nbsp; contain&nbsp; a&nbsp; list of hosts, one per line (though
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; each line may&nbsp;&nbsp;&nbsp; contain&nbsp;&nbsp;&nbsp; a hostlist expression.&nbsp;&nbsp;&nbsp; See HOST-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; LIST EXPRESSIONS section below).
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; DSHPATH
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If set, the path in DSHPATH will be used&nbsp; as&nbsp;&nbsp;&nbsp; the&nbsp; PATH
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the remote processes.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; FANOUT
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Set the pdsh fanout (See description of -f above).
    <br>
    <br>
    <br>
HOSTLIST EXPRESSIONS
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; As&nbsp;&nbsp;&nbsp; noted in sections above&nbsp;&nbsp;&nbsp; pdsh accepts lists of&nbsp; hosts&nbsp; the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; general&nbsp; form:&nbsp; prefix[n-m,l-k,...],&nbsp; where n &lt; m and l &lt; k,
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; etc., as an alternative to&nbsp;&nbsp;&nbsp; explicit&nbsp; lists&nbsp;&nbsp;&nbsp;&nbsp; of&nbsp; hosts.&nbsp; This
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; form&nbsp; should not be confused with regular expression charac-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; ter classes (also denoted by ``[]''). For&nbsp;&nbsp;&nbsp; example,&nbsp; foo[19]
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; does&nbsp; not represent an expression matching&nbsp;&nbsp;&nbsp; foo1 or&nbsp;&nbsp;&nbsp; foo9, but
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; rather represents the degenerate hostlist:&nbsp;&nbsp;&nbsp; foo19.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; The hostlist syntax is meant only as a convenience&nbsp;&nbsp;&nbsp; on&nbsp; clus-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; ters&nbsp; with&nbsp;&nbsp;&nbsp; a "prefixNNN" naming convention&nbsp;&nbsp;&nbsp; and specification
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; of&nbsp;&nbsp;&nbsp;&nbsp; ranges&nbsp;&nbsp;&nbsp;&nbsp; should&nbsp;&nbsp;&nbsp;&nbsp; not&nbsp; be&nbsp; considered&nbsp; necessary&nbsp;&nbsp;&nbsp;&nbsp;
--&nbsp; this
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; foo1,foo9&nbsp;&nbsp;&nbsp; could&nbsp; be&nbsp; specified&nbsp; as such, or by the hostlist
    <br>
    <br>
    <br>
    <br>
pdsh-2.18&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last change: solaris2.11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 8
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
User Commands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdsh(1)
    <br>
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; foo[1,9].
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; Some examples of usage follow:
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; Run command on foo01,foo02,...,foo05
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; pdsh -w foo[01-05] command
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; Run command on foo7,foo9,foo10
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; pdsh -w foo[7,9-10] command
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; Run command on foo0,foo4,foo5
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; pdsh -w foo[0-5] -x foo[1-3] command
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; A suffix on the hostname is also supported:
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; Run command on foo0-eth0,foo1-eth0,foo2-eth0,foo3-eth0
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;pdsh -w&nbsp;&nbsp;&nbsp; foo[0-3]-eth0 command
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; As&nbsp;&nbsp;&nbsp; a reminder to the&nbsp; reader,&nbsp; some&nbsp; shells&nbsp; will&nbsp;&nbsp;&nbsp; interpret
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; brackets&nbsp; ('['&nbsp; and ']') for pattern matching.&nbsp; Depending on
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; your shell, it may&nbsp;&nbsp;&nbsp; be&nbsp; necessary&nbsp; to&nbsp; enclose&nbsp; ranged&nbsp; lists
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; within&nbsp; quotes.&nbsp;&nbsp; For&nbsp; example,&nbsp; in&nbsp; tcsh,&nbsp;&nbsp;&nbsp; the first example
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; above should be executed as:
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; pdsh -w "foo[01-05]" command
    <br>
    <br>
    <br>
ORIGIN
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; Originally&nbsp;&nbsp;&nbsp;&nbsp; a&nbsp; rewrite&nbsp; of&nbsp;&nbsp;&nbsp;&nbsp; IBM&nbsp; dsh(1)&nbsp;&nbsp; by&nbsp;&nbsp; Jim&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Garlick
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; <a class="moz-txt-link-rfc2396E" href="mailto:garlick@llnl.gov">&lt;garlick@llnl.gov&gt;</a>&nbsp;&nbsp;&nbsp;&nbsp; on&nbsp; LLNL's ASCI Blue-Pacific IBM SP
sys-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; tem. It is&nbsp;&nbsp;&nbsp; now used on Linux clusters at LLNL.
    <br>
    <br>
    <br>
LIMITATIONS
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; When using&nbsp;&nbsp;&nbsp; ssh for&nbsp;&nbsp;&nbsp; remote execution, expect&nbsp; the&nbsp; stderr&nbsp; of
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; ssh&nbsp; to&nbsp; be&nbsp; folded in with that of the remote command. When
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; invoked by&nbsp;&nbsp;&nbsp; pdsh, it is not&nbsp;&nbsp;&nbsp; possible for ssh&nbsp; to&nbsp; prompt&nbsp; for
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; passwords&nbsp;&nbsp;&nbsp; if&nbsp; RSA/DSA&nbsp; keys&nbsp; are configured properly, etc..
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; For ssh implementations&nbsp; that&nbsp; suppport&nbsp; a&nbsp;&nbsp;&nbsp;&nbsp; connect&nbsp; timeout
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; option,&nbsp; pdsh&nbsp; attempts&nbsp; to&nbsp; use&nbsp; that option to enforce the
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; timeout (e.g.&nbsp; -oConnectTimeout=T&nbsp;&nbsp;&nbsp; for&nbsp; OpenSSH),&nbsp;&nbsp;&nbsp; otherwise
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; connect timeouts are not supported&nbsp;&nbsp;&nbsp; when using ssh.&nbsp;&nbsp;&nbsp;&nbsp; Finally,
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; there is no reliable way for pdsh to ensure that remote com-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; mands&nbsp; are&nbsp;&nbsp;&nbsp; actually terminated when using a command timeout.
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; Thus if -u&nbsp;&nbsp;&nbsp; is used&nbsp;&nbsp;&nbsp; with ssh commands may be left running&nbsp; on
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; remote&nbsp; hosts&nbsp; even&nbsp; after&nbsp;&nbsp;&nbsp;&nbsp; timeout&nbsp; has&nbsp; killed&nbsp; local&nbsp; ssh
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; processes.
    <br>
    <br>
    <br>
    <br>
    <br>
pdsh-2.18&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last change: solaris2.11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 9
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
User Commands&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdsh(1)
    <br>
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; Output from multiple processes per&nbsp;&nbsp;&nbsp; node may be&nbsp; interspersed
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; when using&nbsp;&nbsp;&nbsp; qshell or mqshell rcmd modules.
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; The number&nbsp;&nbsp;&nbsp; of nodes that&nbsp; pdsh&nbsp; can&nbsp; simultaneously&nbsp; execute
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; remote&nbsp; jobs&nbsp; on is limited by the&nbsp;&nbsp;&nbsp; maximum&nbsp;&nbsp;&nbsp; number of threads
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; that can be created concurrently, as well as the&nbsp; availabil-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; ity of reserved ports in the rsh and qshell rcmd modules. On
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; systems that implement Posix threads, the limit is&nbsp;&nbsp;&nbsp; typically
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; defined by&nbsp;&nbsp;&nbsp; the constant PTHREADS_THREADS_MAX.
    <br>
    <br>
    <br>
FILES
    <br>
ATTRIBUTES
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; See attributes(5) for descriptions&nbsp;&nbsp;&nbsp; of the&nbsp;&nbsp;&nbsp; following&nbsp; attri-
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; butes:
    <br>
    <br>
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; ____________________________________________________________
    <br>
&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATTRIBUTE TYPE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ATTRIBUTE VALUE&nbsp;&nbsp;&nbsp; |
    <br>
&nbsp;&nbsp;&nbsp; |_____________________________|_____________________________|
    <br>
&nbsp;&nbsp;&nbsp; | Availability&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | SUNWpdsh&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
    <br>
&nbsp;&nbsp;&nbsp; |_____________________________|_____________________________|
    <br>
&nbsp;&nbsp;&nbsp; | Interface&nbsp;&nbsp;&nbsp; Stability&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
    <br>
&nbsp;&nbsp;&nbsp; |_____________________________|_____________________________|
    <br>
    <br>
    <br>
SEE ALSO
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; rsh(1),&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ssh(1),&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dshbak(1),&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdcp(1)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; <a class="moz-txt-link-freetext" href="http://sourceforge.net/projects/pdsh/">http://sourceforge.net/projects/pdsh/</a>
    <br>
    <br>
NOTES
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; Source for&nbsp;&nbsp;&nbsp; pdsh is&nbsp;&nbsp;&nbsp; available on <a class="moz-txt-link-freetext" href="http://opensolaris.org">http://opensolaris.org</a>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
    <br>
pdsh-2.18&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Last change: solaris2.11&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10
    <br>
    <br>
    <br>
&nbsp;
------------------------------------------------------------------------
    <br>
    <br>
Template Version: @(#)sac_nextcase %I% %G% SMI This information is
Copyright 2009 Sun Microsystems 1. Introduction
    <br>
&nbsp;&nbsp;&nbsp; 1.1. Project/Component Working Name:
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; pdsh Ver 2.18
    <br>
&nbsp;&nbsp;&nbsp; 1.2. Name of Document Author/Supplier:
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; Author:&nbsp; Vivek R. Titarmare
    <br>
&nbsp;&nbsp;&nbsp; 1.3&nbsp; Date of This Document:
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; 3rd April, 2009
    <br>
    <br>
2. Project Summary
    <br>
&nbsp;&nbsp; 2.1 Project Description
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;Parallel command execution for clusters
    <br>
    <br>
4. Technical Description:
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;Pdsh is a high-performance, parallel remote shell utility. It has
built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and can
call SSH externally (though with reduced performance). Pdsh uses a
"sliding window" parallel algorithm to conserve socket resources on the
initiating node and to allow progress to continue while timeouts occur
on some connections.
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which runs
commands on a single remote host, pdsh can run multiple remote commands
in parallel. pdsh uses a "sliding window" (or fanout) of threads to
conserve resources on the the initiating host while allowing some
connections to time out.&nbsp;&nbsp;&nbsp;&nbsp; <br>
    <br>
5. Interfaces <br>
&nbsp;&nbsp;&nbsp;&nbsp;The binary file "pdsh" contains following interface.
    <br>
    <br>
&nbsp;&nbsp; Exported interface&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Classification&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Interface type
    <br>
&nbsp;&nbsp; =============================&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ==============&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
==============
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/bin/dshbak&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; binary
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/bin/pdcp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; binary
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/bin/pdsh&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; binary
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/bin/rpdcp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; binary
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/lib/pdsh/xrcmd.so&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; shared library
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/lib/pdsh/xrcmd.la&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; library tool
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/lib/pdsh/xrcmd.a&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; static library
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/lib/pdsh/execcmd.so&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; shared library
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/lib/pdsh/execcmd.la&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; library tool
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/lib/pdsh/execcmd.a&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; static library
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp;&nbsp;&nbsp;PDSH_RCMD_TYPE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; override standard
argument
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;PDSH_SSH_ARGS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; override standard
argument
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;PDSH_SSH_ARGS_APPEND&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; override standard
argument
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;WCOLL&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; override standard argument
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;DSHPATH&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; override standard
argument
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;FANOUT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; override standard argument
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;QSHELL_REMOTE_LD_LIBRARY_PATH&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; override
standard argument
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;QSHELL_REMOTE_LD_PREOPEN&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; override standard
argument
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;
    <br>
    <br>
&nbsp;&nbsp; Imported interface&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Classification&nbsp;&nbsp; Comments
    <br>
&nbsp;&nbsp; =======================&nbsp;&nbsp; ==============&nbsp;&nbsp;
=================================== &nbsp;&nbsp;&nbsp;&nbsp;None
    <br>
    <br>
&nbsp;&nbsp; The binary file would go in "usr/bin" and the libraries would go in
"usr/lib"
    <br>
    <br>
    <br>
6. Resources and Schedule
    <br>
&nbsp;&nbsp;&nbsp; 6.4. Steering Committee requested information
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 6.4.1. Consolidation C-team Name:
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; SFW
    <br>
&nbsp;&nbsp;&nbsp; 6.5. ARC review type: FastTrack
    <br>
&nbsp;&nbsp;&nbsp; 6.6. ARC Exposure: open
    <br>
------------------------------------------------------------------------
    <br>
    <br>
FCL--FOSS Check List
    <br>
    <br>
1.0 Project Information
    <br>
1.1 Name of project/component
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;pdsh&nbsp; Ver 2.18
    <br>
    <br>
1.2 Author of document
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;Vivek R. Titarmare
    <br>
    <br>
2.0 Project Summary
    <br>
&nbsp; 2.1 Project Description
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;Pdsh is a high-performance, parallel remote shell utility. It has
built-in, thread-safe clients for Berkeley and Kerberos V4 rsh and can
call SSH externally (though with reduced performance). Pdsh uses a
"sliding window" parallel algorithm to conserve socket resources on the
initiating node and to allow progress to continue while timeouts occur
on some connections.
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;Pdsh is a variant of the rsh(1) command. Unlike rsh(1), which runs
commands on a single remote host, pdsh can run multiple remote commands
in parallel. pdsh uses a "sliding window" (or fanout) of threads to
conserve resources on the the initiating host while allowing some
connections to time out.&nbsp;&nbsp;&nbsp;&nbsp; <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;Pdsh is a an efficient, multithreaded remote shell client which
executes commands on multiple remote hosts in parallel. Pdsh implements
dynamically loadable modules for extended functionality such as new
remote shell services and remote host selection
    <br>
    <br>
&nbsp; 2.2 Release binding
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; What is is the release binding?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (see
<a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/release-taxonomy/">http://opensolaris.org/os/community/arc/policies/release-taxonomy/</a>)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Major
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] Minor
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Patch or Micro
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Unknown -- ARC review required
    <br>
    <br>
&nbsp; 2.3 Type of project
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Is this case a Linux Familiarity project?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No
    <br>
    <br>
&nbsp; 2.4 Originating Community
    <br>
&nbsp;&nbsp;&nbsp; 2.4.1 Community Name
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; PDSH (<a class="moz-txt-link-freetext" href="http://sourceforge.net/projects/pdsh/">http://sourceforge.net/projects/pdsh/</a>)
    <br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 2.4.2 Community Involvement
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Indicate Sun's involvement in the community
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Maintainer
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Contributor
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] Monitoring
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Will the project team work with the upstream community to
resolve
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; architectural issues of interest to Sun?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] Yes &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - briefly explain
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Will we or are we forking from the community?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes - ARC review required prior to forking
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] No
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 3.0 Technical Description
    <br>
&nbsp; 3.1 Installation &amp; Sharable
    <br>
&nbsp;&nbsp;&nbsp; 3.1.1S Solaris Installation - section only required for Solaris
Software
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (see
<a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/install-locations/">http://opensolaris.org/os/community/arc/policies/install-locations/</a> for
details)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Does this project follow the Install Locations best practice?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] Yes &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Does this project install into /usr under
[sbin|bin|lib|include|man|share]?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No or N/A
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Does this project install into /opt?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes - explain below
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] No or N/A
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Does this project install into a different directory
structure?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] No or N/A
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Do any of the components of this project conflict with
anything under /usr?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (see <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/caselog/2007/047/">http://opensolaris.org/os/community/arc/caselog/2007/047/</a>
for details)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes - explain below
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] No
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If conflicts exist then will this project install under
/usr/gnu?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] N/A
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Is this project installing into /usr/sfw?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] No
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 3.1.1W Windows Installation - section only required for
Windows Software
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (see <a class="moz-txt-link-freetext" href="http://sac.sfbay/WSARC/2002/494">http://sac.sfbay/WSARC/2002/494</a> for details)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Does this project install software into a &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;system
drive&gt;:\Program Files\Sun\&lt;product&gt; or &lt;system
drive&gt;:\Sun\&lt;product&gt;
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; directory?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Does the project use the Windows registry?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Does the project use &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; HKEY_LOCAL_MACHINE\SOFTWARE\Sun
Microsystems\&lt;product&gt;\&lt;version&gt;
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for the registry key?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Is the project's stored location
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\&lt;product
id&gt;\&lt;version id&gt;\Path?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 3.1.2 Share and Sharable
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Does the module include any components that are used or shared by
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; other projects?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No
    <br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If yes are these components packaged to be shared with the
other FOSS?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] N/A
    <br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Are these components already in the Solaris WOS?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - continue with next section (section 3.2)
    <br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If yes are these newer versions being delivered?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If yes are the newer versions replacing the existing
versions?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
    <br>
&nbsp; 3.2 Exported Libraries
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Are libraries being delivered by this project?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] No - continue with next section (section 3.3)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Are 64-bit versions of the libraries being delivered?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Are static versions of the libraries being delivered?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; 3.3 Services and the /etc Directory
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (see
<a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/SMF-policy/">http://opensolaris.org/os/community/arc/policies/SMF-policy/</a>)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Does the project integrate anything into /etc/init.d or
/etc/rc?.d?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] No
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Does the project integrate any new entries into
/etc/inittab or
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /etc/inetd.conf?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] No
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Does the project integrate any private non-public files
into /etc/default
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; or /etc/ configuration files?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] No
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Does the service manifests method context grant rights
above that
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of the noaccess user and basic privilege set?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] No
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; 3.4 Security
    <br>
&nbsp;&nbsp;&nbsp; 3.4.1 Secure By Default &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (see
<a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/secure-by-default/">http://opensolaris.org/os/community/arc/policies/secure-by-default/</a> for
details)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (see
<a class="moz-txt-link-freetext" href="http://www.opensolaris.org/os/community/arc/policies/NITS-policy/">http://www.opensolaris.org/os/community/arc/policies/NITS-policy/</a> for
details)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (see parts of
<a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/SMF-policy/">http://opensolaris.org/os/community/arc/policies/SMF-policy/</a> for
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; addtional details)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Are there any network services provided by this project?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] No - continue with the next section (section 3.4.2)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Are network services enabled by default?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] N/A
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Are network services automatically enabled by the project
during installation?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] N/A
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Are inbound network communications denied by default?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] N/A
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Is inbound data checked to prevent content-based attacks?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] N/A
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Is the outbound receiver authenticated?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] N/A
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Is the receiver authenticated prior to receiving any
sensitive outbound communication?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] N/A
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 3.4.2 Authorization
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (see
<a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/">http://opensolaris.org/os/community/arc/bestpractices/rbac-intro/</a> and
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/">http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/</a>
and
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/">http://opensolaris.org/os/community/arc/bestpractices/rbac-profiles/</a>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for details)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Are there any setuid/setgid privileged binaries in the project?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] No - continue with next section (section 3.4.3)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If yes then are the setuid/setgid privileges handled by the
use of roles?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
    <br>
&nbsp;&nbsp;&nbsp; 3.4.3 Auditing
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (see
<a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/audit-policy/">http://opensolaris.org/os/community/arc/policies/audit-policy/</a> for
details)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (see <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/caselog/2003/397">http://opensolaris.org/os/community/arc/caselog/2003/397</a> for
details)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Does this component contain administrative or security enforcing
software?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] No - continue to next section (section 3.4.4)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (see
<a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/caselog/2003/397">http://opensolaris.org/os/community/arc/caselog/2003/397</a> for details)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Do the components create audit logs detailing what took place
including what event
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; took place, who was involved, when the event took place?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes - ARC contract and Audit project team review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 3.4.4 Authentication
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (see <a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/policies/PAM/">http://opensolaris.org/os/community/arc/policies/PAM/</a>)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Do the components contain any authentication code?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] No - continue to next section (section 3.4.5)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If yes do the components use PAM (plugable authentication
modules) for authentication?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If yes is a single PAM session maintained during
authentication?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If yes are the components sufficiently privileged to allow
the requested &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; operations (authentication, password change,
process credential manipulation, &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; audit state initialization)?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes - briefly describe below
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 3.4.5 Passwords
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (see
<a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/">http://opensolaris.org/os/community/arc/bestpractices/passwords-cli/</a>
and
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/bestpractices/passwords-files/">http://opensolaris.org/os/community/arc/bestpractices/passwords-files/</a>
for details)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Do any of the components for the project deal with passwords?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] No - continue to next section (section 3.4.6)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If yes are these passwords entered via the CLI or
environment?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Are passwords stored within the file system for the
component?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - continue to next section (section 3.4.6)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If yes are the permissions on the file such to protect
exposing the password(s)?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; 3.4.6 General Security Questions
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (see
<a class="moz-txt-link-freetext" href="http://opensolaris.org/os/community/arc/bestpractices/security-questions/">http://opensolaris.org/os/community/arc/bestpractices/security-questions/</a>
for details)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Are there any network protocols used by this project?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - continue with the next section (section 3.5)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Do the components use standard network protocols?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Do network services for the project make decisions based
upon user, host or &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; service identities?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] Yes - explain below
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] N/A
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; pdsh makes decision on network services based upon
service identities. pdsh is a variant of the rsh(1) command. The core
functionality of pdsh may be supplemented by dynamically loadable
modules. The modules may provide a new connection protocol (replacing
the standard rcmd(3) protocol used by rsh(1)), filtering options (e.g.
removing hosts that are "down" from the target list), and/or host
selection options (e.g., -a selects all hosts from a configuration
file.).Pdsh modules come in two flavors at this time: rcmd and
miscellaneous. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The rcmd modules provide remote command functionality for
pdsh. A list of rcmd modules currently distributed with pdsh follows.
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; rsh Uses an internal, thread-safe implementation of BSD
rcmd(3) to run commands using the standard rsh(1) protocol.
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ssh Uses a variant of popen(3) to run multiple copies of
the ssh(1) command. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mrsh This module uses the mrsh(1)
protocol to execute jobs on remote hosts. The mrsh protocol uses a
credential based authentication, forgoing the need to allocate reserved
ports. In other aspects, it acts just like rsh. Remote nodes must be
running mrshd(8) in order for the mrsh module to work.
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; qsh&nbsp; Allows pdsh to execute MPI jobs over QsNet.
Qshell propagates the current working directory, pdsh environment, and
Elan capabilities to the remote process. The following environment
variable are also appended to the environment: RMS_RANK, RMS_NODEID,
RMS_PROCID, RMS_NNODES, and RMS_NPROCS. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Since pdsh needs to run
setuid root for qshell support, qshell does not directly support
propagation of LD_LIBRARY_PATH and LD_PREOPEN. Instead the
QSHELL_REMOTE_LD_LIBRARY_PATH and QSHELL_REMOTE_LD_PREOPEN environment
variables will may be used and will be remapped to LD_LIBRARY_PATH and
LD_PREOPEN by the qshell daemon if set. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mqsh Similar to
qshell, but uses the mrsh protocol instead of the rsh protocol.
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; krb4 The krb4 module allows users to execute remote
commands after authenticating with kerberos. Of course, the remote rshd
daemons must be kerberized. &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; xcpu The xcpu module uses
the xcpu service to execute remote commands
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Do the components make use of secret information during
authentication and/or
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; authorization?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes - explain below
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] No
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] N/A
    <br>
&nbsp; &nbsp; 3.5 Networking
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Do the components access the network?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] Yes
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - continue with the next section (section 3.6)
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If yes do the components support IPv6?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] Yes &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] No - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; 3.6 Core Solaris Components
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Do the components of this project compete with or duplicate core
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Solaris components?
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [ ] Yes - ARC review required
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; [X] No &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 4.0 Interfaces
    <br>
&nbsp; (see
<a class="moz-txt-link-freetext" href="http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/">http://www.opensolaris.org/os/community/arc/policies/interface-taxonomy/</a>
for details)
    <br>
&nbsp; 4.1 Exported Interfaces
    <br>
&nbsp; &nbsp;&nbsp;&nbsp; The binary file "pdsh" contains following interface.
    <br>
    <br>
&nbsp;&nbsp;&nbsp; Interface Name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Classification&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Comments
    <br>
&nbsp;&nbsp;&nbsp; ---------------------------&nbsp;&nbsp;&nbsp;&nbsp; -------------------&nbsp;&nbsp;&nbsp;&nbsp;
---------------------------
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/bin/dshbak&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; binary
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/bin/pdcp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; binary
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/bin/pdsh&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; binary
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/bin/rpdcp&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; binary
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/lib/pdsh/xrcmd.so&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; shared library
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/lib/pdsh/xrcmd.la&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; library tool
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/lib/pdsh/xrcmd.a&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; static library
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/lib/pdsh/execcmd.so&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; shared library
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/lib/pdsh/execcmd.la&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; library tool
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; usr/lib/pdsh/execcmd.a&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; static library
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp;&nbsp;&nbsp;PDSH_RCMD_TYPE&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; override standard
argument
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;PDSH_SSH_ARGS&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; override standard
argument
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;PDSH_SSH_ARGS_APPEND&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; override standard
argument
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;WCOLL&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; override standard argument
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;DSHPATH&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; override standard
argument
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;FANOUT&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; override standard argument
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;QSHELL_REMOTE_LD_LIBRARY_PATH&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; override
standard argument
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;QSHELL_REMOTE_LD_PREOPEN&nbsp;&nbsp;&nbsp; Uncommitted&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; override standard
argument
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;
    <br>
    <br>
&nbsp; 4.2 Imported Interfaces
    <br>
&nbsp;&nbsp;&nbsp; Interface Name&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Classification&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Comments
    <br>
&nbsp;&nbsp;&nbsp; --------------------------- --------------------
--------------------------
    <br>
&nbsp;&nbsp;&nbsp;&nbsp;None&nbsp;&nbsp;&nbsp; <br>
The binary file would go in "/usr/bin" and the libraries would go in
"/usr/lib"
    <br>
    <br>
Appendix B - Suggested case materials
    <br>
&nbsp; 1. man pages
    <br>
    <br>
&nbsp;&nbsp;&nbsp;&nbsp; Attached are the man pages (pdsh.1, pdcp.1, dshbak.1)
    <br>
    <br>
&nbsp; 2. SMF manifests
    <br>
&nbsp; 3. links to contracts
    <br>
&nbsp; </blockquote>
  <br>
_______________________________________________
  <br>
opensolaris-arc mailing list
  <br>
<a class="moz-txt-link-abbreviated" href="mailto:opensolaris-arc@opensolaris.org">opensolaris-arc@opensolaris.org</a>
  <br>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<title></title>
<table border="0" cellpadding="0" cellspacing="0" width="519">
  <tbody>
    <tr valign="top">
      <td height="121" width="98"><a moz-do-not-send="true"
 href="http://www.sun.com"><img moz-do-not-send="true"
 src="http://www.sun.com/emrkt/sigs/6h_top.gif" border="0" height="92"
 width="98"></a></td>
      <td style="font-family: Arial; font-size: 10px;" height="121"
 width="249"><b> Mark A. Carlson </b><br>
Sr. Architect<br>
      <br>
      <b>Systems Group</b><br>
Phone x69559 / 303-223-6139<br>
Email <a moz-do-not-send="true" class="moz-txt-link-abbreviated"
 href="mailto:Mark.Carlson@Sun.COM">Mark.Carlson@Sun.COM</a><br>
      </td>
      <td style="font-family: Arial; font-size: 10px;" width="172"><img
 moz-do-not-send="true" src="http://www.sun.com/emrkt/sigs/q12.gif"
 height="118" width="172"></td>
    </tr>
  </tbody>
</table>
<div class="moz-signature"><br>
</div>
</div>
</body>
</html>

--Boundary_(ID_c23GdocVnywPtkpBCToWGw)--

From Mark.Carlson@sun.com Thu Apr 30 05:14:09 2009
Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165])
	by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n3UCE7eL012119
	for <LSARC-ext@sac.sfbay.sun.com>; Thu, 30 Apr 2009 05:14:07 -0700 (PDT)
Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6])
	by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n3UCE10b028625
	for <@sunmail2sca.sfbay.sun.com:LSARC-ext@sun.com>; Thu, 30 Apr 2009 13:14:06 +0100 (BST)
Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by
 nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 id <0KIW0042PXZHPV00@nwk-avmta-2.sfbay.sun.com> for LSARC-ext@sun.com
 (ORCPT LSARC-ext@Sun.COM); Thu, 30 Apr 2009 05:14:05 -0700 (PDT)
Received: from brmea-mail-2.sun.com ([192.18.98.43])
 by nwk-avmta-2.sfbay.sun.com
 (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005))
 with ESMTP id <0KIW00D8LXZGR9F0@nwk-avmta-2.sfbay.sun.com> for
 LSARC-ext@sun.com (ORCPT LSARC-ext@Sun.COM); Thu,
 30 Apr 2009 05:14:04 -0700 (PDT)
Received: from fe-amer-10.sun.com ([192.18.109.80])
	by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n3UCE47t029710	for
 <LSARC-ext@Sun.COM>; Thu, 30 Apr 2009 12:14:04 +0000 (GMT)
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 id <0KIW00M00XZ7A100@mail-amer.sun.com> for LSARC-ext@Sun.COM
 (ORCPT LSARC-ext@Sun.COM); Thu, 30 Apr 2009 06:14:04 -0600 (MDT)
Received: from Macintosh-335.local ([unknown] [129.150.35.46])
 by mail-amer.sun.com
 (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009))
 with ESMTPSA id <0KIW00738XZA4OE0@mail-amer.sun.com>; Thu,
 30 Apr 2009 06:13:58 -0600 (MDT)
Date: Thu, 30 Apr 2009 06:13:58 -0600
From: "Mark A. Carlson" <Mark.Carlson@sun.com>
Subject: Re: pdsh Ver 2.18 [LSARC/2009/238 FastTrack timeout 04/20/2009]
In-reply-to: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
Sender: Mark.Carlson@sun.com
To: Mark Carlson <markcarl@sac.sfbay.sun.com>
Cc: LSARC-ext@sun.com, Vivek.Titarmare@sun.com
Message-id: <49F99606.9050302@sun.com>
MIME-version: 1.0
Content-type: text/plain; format=flowed; charset=ISO-8859-1
Content-transfer-encoding: 7BIT
X-PMX-Version: 5.4.1.325704
References: <200904132041.n3DKfDgk025507@sac.sfbay.sun.com>
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
Status: RO
Content-Length: 99

Updated materials are in the case directory. This case was approved at 
LSARC this week.

-- mark