Meta::Baseline::Rsh - library to do correct rsh execution on machines.

Copyright (C) 2001, 2002 Mark Veltzer; All rights reserved.

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111, USA.

	MANIFEST: Rsh.pm
	PROJECT: meta
	VERSION: 0.32

	package foo;
	use Meta::Baseline::Rsh qw();
	my($resu)=Meta::Baseline::Rsh::rsh($demo,$verbose,$target,$host,$command);

This package can do correct rsh execution, both on pcs and on unices (current host included...). This is supposed to handle the following cases: 0. the remote machine is the current machine (dont rsh). 1. the remote machine is the a unix machine (do rsh with a unix wrapper so you'll get the right return code...). 2. the remote machine is an NT machine (do rsh with an NT wrapper so you'll get the right return code...).

	rsh($$$$$)
	cook_rsh($$$$)
	TEST($)

rsh($$$$$)

This is the baseline version of rsh. Why is there such a version ? because when you issue a command from rsh and you built the command on some host there is no gurantee that this command will look exactly the same and execute properly on all other hosts that work with the baseline. This is especialy true if the command involved is doing development builds...:) Return value for this function is 1 for success and 0 for failure.

cook_rsh($$$$)

This does a cook simulation of an rsh. Cook is not treating rsh right cause it thinks that rsh is not a good enough software. But since we are writing the rsh wrapper and our wrapper is good we want to avoid rsh'ing when the host to rsh is the current host etc... Therefore we get the weird cook executiong lines, analyze them, and execute them as if we were just a regular dumb rsh. We ofcourse call our own version of rsh which is implemented in this modules to handle current, linux and pc hosts correctly.

TEST($)

Test suite for this module. The way it does it is just to run the routine for a couple of random host names.

None.

None.

	Name: Mark Veltzer
	Email: mailto:veltzer@cpan.org
	WWW: http://www.veltzer.org
	CPAN id: VELTZER

	0.00 MV initial code brought in
	0.01 MV this time really make the databases work
	0.02 MV make quality checks on perl code
	0.03 MV more perl checks
	0.04 MV make Meta::Utils::Opts object oriented
	0.05 MV check that all uses have qw
	0.06 MV fix todo items look in pod documentation
	0.07 MV more on tests/more checks to perl
	0.08 MV put ALL tests back and light the tree
	0.09 MV fix up the cook module
	0.10 MV correct die usage
	0.11 MV perl code quality
	0.12 MV more perl quality
	0.13 MV more perl quality
	0.14 MV get basic Simul up and running
	0.15 MV perl documentation
	0.16 MV more perl quality
	0.17 MV perl qulity code
	0.18 MV more perl code quality
	0.19 MV revision change
	0.20 MV languages.pl test online
	0.21 MV perl packaging
	0.22 MV md5 project
	0.23 MV database
	0.24 MV perl module versions in files
	0.25 MV movies and small fixes
	0.26 MV thumbnail user interface
	0.27 MV more thumbnail issues
	0.28 MV website construction
	0.29 MV web site automation
	0.30 MV SEE ALSO section fix
	0.31 MV teachers project
	0.32 MV md5 issues

Meta::Utils::Chdir(3), Meta::Utils::File::Prop(3), Meta::Utils::File::Remove(3), Meta::Utils::Net::Hostname(3), Meta::Utils::Output(3), Meta::Utils::Pc(3), Meta::Utils::Utils(3), strict(3)

-stop getting the targets in cook_rsh through the chmod part of the command line.

-fix this module a lot since cook has changed a lot.