A quick demo of how to wrap the SSH::Expect object in a class of your own (seems to be what you were doing). You were missing the constructor so I added one, you called the LoginFirst routine with no object, whereas you depend on $self existing in it and you forgot to login
Last edited by Skrynesaver; 07-18-2011 at 08:02 AM..
Reason: spelling and details
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)
All,
Is it possible to call a subroutine from the perl expect module after logging to a system that is within the same program. My situation is I need to run a logic inside a machine that I'm logging in using the expect module, the logic is also available in the same expect program.
Thanks,... (5 Replies)
Okay I have a 1TB drive that is almost completely full with vids. I am in the process of converting them to mp4. I have two scripts right now. One is a shell script to convert them with Handbrake. The other is a script to get a sort of progress report. To make things easier to understand, I will... (0 Replies)
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)
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)
Hello All,
I have 2 perl sub-routines.
my $myDir = myDir_path;
my $file;
sub convert(){
system ("./$myConvertScript >> $myDir/$file_CONV" );
$file2 = $myDir/$file_CONV;
}
sub addDB(){
open(CONF, $config)
or die "Cannot Open $config for reading. ";
while(<CONF>){... (1 Reply)
Hi all,
I'm not even sure a person can do this in perl, seems like you should be able to though.
Here's the error
IO::Socket::INET: connect: Operation now in progress at server_search.pl line 256, <DATA> line 466.
Here's the perl code...
sub ldap_new{
$nl = Net::LDAP->new( "$_" ) or... (3 Replies)
Hi all, I have this code #This program read the triplets from file named "data" into
#an array of array.
use strict;
use warnings;
use Data::Dumper;
use Graph;
use Graph::Subgraph;
my @S;
while (<>) {
push @S, ;
}
print "-----TRIPLETS-------\n";
print Dumper \@S;
#Make... (6 Replies)
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)
HI ,
I am running a program on hpux in perl.
I am encountering a strange issue where when i print a variable in the sub which is returning it , it prints a different value but when i call it and store value in a variable it gives a different o/p.
the sub is
sub CheckConfigFilePattern ... (4 Replies)
Discussion started by: Jcpratap
4 Replies
LEARN ABOUT DEBIAN
devel::nytprof::core
Devel::NYTProf::Core(3pm) User Contributed Perl Documentation Devel::NYTProf::Core(3pm)NAME
Devel::NYTProf::Core - load internals of Devel::NYTProf
DESCRIPTION
This module is not meant to be used directly. See Devel::NYTProf, Devel::NYTProf::Data, and Devel::NYTProf::Reader.
While it's not meant to be used directly, it is a handy place to document some internals.
SUBROUTINE PROFILER
The subroutine profiler intercepts the "entersub" opcode which perl uses to invoke a subroutine, both XS subs (henceforth xsubs) and pure
perl subs.
The following sections outline the way the subroutine profiler works:
Before the subroutine call
The profiler records the current time, the current value of cumulative_subr_secs (as initial_subr_secs), and the current
cumulative_overhead_ticks (as initial_overhead_ticks).
The statement profiler measures time at the start and end of processing for each statement (so time spent in the profiler, writing to the
file for example, is excluded.) It accumulates the measured overhead into the cumulative_overhead_ticks variable.
In a similar way, the subroutine profiler measures the exclusive time spent in subroutines and accumulates it into the cumulative_subr_secs
global.
Make the subroutine call
The call is made by executing the original perl internal code for the "entersub" opcode.
Calling a perl subroutine
If the sub being called is a perl sub then when the entersub opcode returns, back into the subroutine profiler, the subroutine has been
'entered' but the first opcode of the subroutine hasn't been executed yet. Crucially though, a new scope has been entered by the entersub
opcode.
The subroutine profiler then pushes a destructor onto the context stack. The destructor is effectively just inside the sub, like a
"local", and so will be triggered when the subroutine exits by any means. Also, because it was the first thing push onto the context stack,
it will be triggered after any activity caused by the subroutines scope exiting.
When the destructor is invoked it calls a function which completes the measurement of the time spent in the sub (see below).
In this way the profiling of perl subroutines is very accurate and robust.
Calling an xsub
If the sub being called is an xsub, then control doesn't return from the entersub opcode until the xsub has returned. The profiler detects
this and calls the function which completes the measurement of the time spent in the xsub.
So far so good, but there's a problem. What if the xsub doesn't return normally but throws an exception instead?
In that case (currently) the profiler acts as if the xsub was never called. Time spent inside the xsub will be allocated to the calling
sub.
Completing the measurement
The function which completes the timing of a subroutine call does the following:
It calculates the time spent in the statement profiler:
overhead_ticks = cumulative_overhead_ticks - initial_overhead_ticks
and subtracts that from the total time spent 'inside' the subroutine:
incl_subr_sec = (time now - time call was made) - overhead_ticks
That gives us an accurate inclusive time. To get the exclusive time it calculates the time spent in subroutines called from the subroutine
call we're measuring:
called_sub_secs = cumulative_subr_secs - initial_subr_secs
and subtracts that from the incl_subr_sec:
excl_subr_sec = incl_subr_sec - called_sub_secs
To make that easier to follow, consider a call to a sub that calls no others. In that case cumulative_subr_secs remains unchanged during
the call, so called_sub_secs is zero, and excl_subr_sec is the same as incl_subr_sec.
Finally, it adds the exclusive time to the cumulative exclusive time:
cumulative_subr_secs += excl_subr_sec
AUTHOR
Tim Bunce, <http://www.tim.bunce.name> and <http://blog.timbunce.org>
COPYRIGHT AND LICENSE
Copyright (C) 2008, 2009 by Tim Bunce.
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself, either Perl version 5.8.8 or,
at your option, any later version of Perl 5 you may have available.
perl v5.14.2 2010-11-19 Devel::NYTProf::Core(3pm)