01-10-2011
PERL draws input from the keyboard, a file, or a library references in a file, but it is all pretty much the same to PERL. Whatever PERL commands you want to run, that code can all be sent down the pipe as keyboard input to a remote PERL invocation, or you can send files down the pipe to /tmp and get PERL to take input from them. If you are using PERL libraries, it is a bit messy figuring how to turn them into one stream, and they may call additional libraries. Maybe PERL has a facility like CC -E or cpp, where all the includes are turned into one file.
Of course, it what you want to achieve on the far end an be reduced to the minimum, it makes it simpler. You can solicit a flow of data from the remote system using a few commands to a simple shell or PERL invocation there, and process it on the original system in the driving PERL script there. It is a classic choice of function shipping or data shipping. If there is too much remote data, then function shipping makes sense.
The perl expect script is just a media in place of something more script friendly like rcp/scp/scp2rsh/ssh/ssh2 passwordless access. What it runs on the far end is a completely divorced discussion, as well as what it feeds locally. There is not normally any expectation that a PERL expect script calls PERL modules. Trying to achieve more than access may just complicate the expect function. Usually, it is better to write something else to run locally and remotely to solve the problem, and the perl expect is just a building block to get the remote access necessary for the other local and remote code to solve the problem.
This User Gave Thanks to DGPickett For This Post:
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Problem: I have a shell script that will be called by a Perl module that will connect to a db and delete rows. The Perl module will be called by CRON. I am using a Perl module to call a shell script because I need to get the db connection from Perl.
Here is the Perl pseudocode:
... (4 Replies)
Discussion started by: mh53j_fe
4 Replies
2. Shell Programming and Scripting
I want to replace a Perl module name in all my Perl Scripts in the cgi-bin directory. How is it possible?
I have the following statement in my scripts
use myUtil;
I want to change it to
use myUtil777;
Regards,
Rahul (2 Replies)
Discussion started by: rahulrathod
2 Replies
3. Shell Programming and Scripting
I call a EXPECT script from my perl script with machine IP and a FIle. The script logins to the machine and exports the value. The values to be exported or stored in a file.
I have close to 10 machines and I have created 10 files and pass the corresponding files in command line, Now I could like... (4 Replies)
Discussion started by: ramkriz
4 Replies
4. Shell Programming and Scripting
Hi,
I can't get this script ot work and I wa wondering if anyone could help?
I need to open a file and use a subroutine to search each line for a regular expression. If it matches then I need to return a match from the subroutine and print the result?
Any help would be greatly... (11 Replies)
Discussion started by: jmd2004
11 Replies
5. Shell Programming and Scripting
Hi All,
I have a doubt whether expect module in perl will work in SQL prompt or its applicable only for shell prompt ?
Thanks,
Arun V (2 Replies)
Discussion started by: arun_maffy
2 Replies
6. Shell Programming and Scripting
The following subroutine prints 1 instead of the content of the Equipment variable. Can someone tell me why?
#!c:/perl/bin/perl.exe
#
use strict 'vars';
my $Equipments = "data/equips.txt";
unless (open(EQUIP_FH, "$Equipments")) {
print "errors: $Equipments\n"; # This line prints... (1 Reply)
Discussion started by: tqlam
1 Replies
7. Shell Programming and Scripting
Hi,
ive a perl script, where it has a subroutine clear() in it, and i've one shell script which runs in background, from that shell script i wanted to call subroutine which is in perl script, that's perl script is not module, just simple script.
Eg:
perl script <test>
#!... (4 Replies)
Discussion started by: asarunkumar
4 Replies
8. Programming
Hi everyone,
I have given up finally trying to find a way to do this.
I have a subroutine called LoginFirst where I am starting a new SSH session.
I have bunch of subroutines, each one of them uses a (or I have to create
a new SSH constructor everytime) ssh connection to get some value so ... (2 Replies)
Discussion started by: dummy_code
2 Replies
9. Shell Programming and Scripting
Hello All,
I am in the process of learning perl.I have a perl script and based on the arguments passed it would the appropriate subroutine that is defined in the script.
Now, I need to check a value that is defined in the Environment variables and should call the subroutine only if the... (1 Reply)
Discussion started by: filter
1 Replies
10. Shell Programming and Scripting
Hi,
I am an occasional PERL user. I am trying to call a sub routine (passing parameters) in perl module from a driver .pl file. I have been "tinkering" for a while now and have confused myself.
Could someone please look at the code below and spot where I am going wrong.
testPerl.pl
... (0 Replies)
Discussion started by: chris01010
0 Replies
LEARN ABOUT DEBIAN
test::autoloader
AutoLoader(3pm) User Contributed Perl Documentation AutoLoader(3pm)
NAME
Test::AutoLoader - a testing utility for autosplit/autoloaded modules.
SYNOPSIS
use Test::AutoLoader;
use Test::More tests => 3;
use_ok("My::Module"); # from Test::More
autoload_ok("My::Module","mysub","sub_two); # test only the listed subs
autoload_ok("My::Module"); # tests all '.al' files found for the module
DESCRIPTION
This single-purpose module attempts to eliminate uncaught syntax errors or other obvious goofs in subroutines that are autosplit, and hence
not looked at by "perl -c Module.pm". Ideally, this module will become unnecessary as you reach full coverage of those subroutines in your
unit tests. Until that happy day, however, this should provide a quick and dirty backstop for embarrassing typos.
Test::AutoLoader is built on Test::Builder, and should interoperate smoothly with other such modules (e.g. Test::Simple, Test::More).
EXPORT
autoload_ok
Very much like the 'use_ok' subroutine (see Test::More). If passed only a module name, it will find all subroutine definitions in the
"auto" directory and attempt to compile them. If passed a list of subroutine names, it will look for and attempt to compile those (and
only those). Any files that cannot be found (if specified directly), read, and compiled will be listed in the diagnostic output for the
failed test.
AUTHOR
Ben Warfield (ben_warfield@nrgn.com)
COPYRIGHT AND LICENSE
This module is copyright (c) 2005 Neurogen Corporation, Branford, Connecticut, USA. It may be distributed under the terms of the GNU
General Public License.
SEE ALSO
perl, Test::More, AutoLoader.
perl v5.10.1 2005-07-22 AutoLoader(3pm)