[31652] in Perl-Users-Digest
Perl-Users Digest, Issue: 2915 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Apr 20 16:09:25 2010
Date: Tue, 20 Apr 2010 13:09:06 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Tue, 20 Apr 2010 Volume: 11 Number: 2915
Today's topics:
Best way to extract content of SVN target/revision for <davidmichaelkarr@gmail.com>
Re: FAQ 5.35 How do I close a file descriptor by number <vilmos@soti.ca>
Re: FAQ 5.35 How do I close a file descriptor by number <jurgenex@hotmail.com>
Re: perl/PHP sessioning <lskatz@gmail.com>
Re: Pod errors: Unterminated S<...> sequence <paduille.4061.mumia.w+nospam@earthlink.net>
Re: Pod errors: Unterminated S<...> sequence <smallpond@juno.com>
Re: Pod errors: Unterminated S<...> sequence <paduille.4061.mumia.w+nospam@earthlink.net>
Re: Pod errors: Unterminated S<...> sequence <smallpond@juno.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: Problems with "show tech" using the Net::Telnet Mod <m@rtij.nl.invlalid>
Threads and Directory Handles <usenet05@drabble.me.uk>
Re: Threads and Directory Handles <usenet05@drabble.me.uk>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 20 Apr 2010 08:51:24 -0700 (PDT)
From: "david.karr" <davidmichaelkarr@gmail.com>
Subject: Best way to extract content of SVN target/revision for searching?
Message-Id: <f1737d17-7e52-4025-abac-f63b66feec29@22g2000vbg.googlegroups.com>
I'm writing a script that will (among other things) search the content
of a target element at a revision for a particular substring. In fact,
it will iterate through the available revisions for an element,
searching for the substring.
In looking at the numerous SVN Perl packages, I started with
"SVN::Client". This gives me a convenient interface to get the
revision numbers available for a target element.
Next, I have to be able to get the text content of the target element
at each of those revisions, in order to search for a substring. The
only obvious interface in SVN::Client that gives me access to the
element content is the "cat()" method, which writes the content to a
file descriptor. I suppose I could get this to work, but this seems
pretty indirect.
Assuming I'm not missing a different way to do this with SVN::Client,
among the numerous other SVN Perl packages, is there another one that
would give me convenient access to the content of an element at a
revision?
------------------------------
Date: 20 Apr 2010 09:12:55 -0700
From: Vilmos Soti <vilmos@soti.ca>
Subject: Re: FAQ 5.35 How do I close a file descriptor by number?
Message-Id: <lqwrw2ayrc.fsf@glia.msmri.medicine.ubc.ca>
PerlFAQ Server <brian@theperlreview.com> writes:
> 5.35: How do I close a file descriptor by number?
>
> If, for some reason, you have a file descriptor instead of a filehandle
> (perhaps you used "POSIX::open"), you can use the "close()" function
> from the "POSIX" module:
I have a related question:
How do I find all the open file descriptors so I can close them?
I have a program which basically does this (runs on Unix):
$ ./perl-program
sub bye () {
umount /mnt/cdrom;
eject cd;
}
$SIG{INT} = bye;
close cd tray;
mount /mnt/cdrom;
cp -r /mnt/cdrom/ /destdir/;
bye;
$
The problem is that if the user hits Ctrl-C in the middle of the copy,
the open file descriptors on /mnt/cdrom will prevent umounting and
ejecting.
Thanks, Vilmos
------------------------------
Date: Tue, 20 Apr 2010 09:49:09 -0700
From: Jürgen Exner <jurgenex@hotmail.com>
Subject: Re: FAQ 5.35 How do I close a file descriptor by number?
Message-Id: <mgmrs5h8u622vefgqrn7du280qnmjrjr55@4ax.com>
Vilmos Soti <vilmos@soti.ca> wrote:
>How do I find all the open file descriptors so I can close them?
>
>I have a program which basically does this (runs on Unix):
>
>$ ./perl-program
> sub bye () {
> umount /mnt/cdrom;
> eject cd;
> }
>
> $SIG{INT} = bye;
>
> close cd tray;
> mount /mnt/cdrom;
> cp -r /mnt/cdrom/ /destdir/;
> bye;
>$
You must have a different Perl than I. My Perl knows neither cp nor
mount or umount and the syntax for close looks rather strange, too.
>The problem is that if the user hits Ctrl-C in the middle of the copy,
>the open file descriptors on /mnt/cdrom will prevent umounting and
>ejecting.
AFAIR file descriptors are closed automatically when they go out of
scope. So scope them correctly and you shouldn't have any problems.
jue
------------------------------
Date: Tue, 20 Apr 2010 11:54:29 -0700 (PDT)
From: Lee <lskatz@gmail.com>
Subject: Re: perl/PHP sessioning
Message-Id: <f664b939-3467-46ea-a261-0fe9c804795f@c27g2000vbb.googlegroups.com>
Cookies was exactly right, thank you. Here is the solution that
worked.
use strict;
use warnings;
use Data::Dumper;
use HTTP::Cookies;
use SOAP::Lite;# on_debug => sub{print@_};
my($response,$value);
my $cookieFile="./cookie.txt";
my $cookie=HTTP::Cookies->new(ignore_discard=>1,file=>
$cookieFile,autosave=>1);
my $soap = SOAP::Lite
-> uri('http://mgip2.biology.gatech.edu')
-> proxy('http://mgip2.biology.gatech.edu/api/apiServer4.php')
;
$soap->transport->cookie_jar($cookie);
------------------------------
Date: Mon, 19 Apr 2010 14:45:50 -0500
From: "Mumia W." <paduille.4061.mumia.w+nospam@earthlink.net>
Subject: Re: Pod errors: Unterminated S<...> sequence
Message-Id: <I8OdnYpXlObb3lDWnZ2dnUVZ_hudnZ2d@earthlink.com>
On 04/19/2010 07:31 AM, Steve C wrote:
> Mumia W. wrote:
>> I have a problem with the POD docs on my system.
>>
>> Most of the time when I try to get documentation on a
>> perl-tk widget or function, the POD has errors that cause
>> the example code to be missing, e.g.
>>
>> Whenever "S< >" is used, the entire line containing it
>> is removed from the output, and an error message appears
>> at the bottom of the rendered file:
>>
>> Unterminated S<...> sequence
>>
>> Obviously, this is not how POD is supposed to work; how can
>> I get the S sequences to display properly. I'm using Debian Lenny
>> with Perl 5.10.0 and perldoc 3.14.02.
>>
>
> Most likely not a perl issue, but...
> What specific command fails?
perldoc Tk::Scrolled
> What do you have LANG set to?
en_US.UTF-8
> What shell are you using?
bash
> What type of window are you in? (eg. xterm, text console, emacs shell,
> etc.)
>
urxvt
Thanks for any help you can give me.
------------------------------
Date: Tue, 20 Apr 2010 10:01:42 -0400
From: Steve C <smallpond@juno.com>
Subject: Re: Pod errors: Unterminated S<...> sequence
Message-Id: <hqkc4f$5qd$1@news.eternal-september.org>
Mumia W. wrote:
> On 04/19/2010 07:31 AM, Steve C wrote:
>> Mumia W. wrote:
>>> I have a problem with the POD docs on my system.
>>>
>>> Most of the time when I try to get documentation on a
>>> perl-tk widget or function, the POD has errors that cause
>>> the example code to be missing, e.g.
>>>
>>> Whenever "S< >" is used, the entire line containing it
>>> is removed from the output, and an error message appears
>>> at the bottom of the rendered file:
>>>
>>> Unterminated S<...> sequence
>>>
>>> Obviously, this is not how POD is supposed to work; how can
>>> I get the S sequences to display properly. I'm using Debian Lenny
>>> with Perl 5.10.0 and perldoc 3.14.02.
>>>
>>
>> Most likely not a perl issue, but...
>> What specific command fails?
>
> perldoc Tk::Scrolled
ok
>
>> What do you have LANG set to?
>
> en_US.UTF-8
ok
>
>> What shell are you using?
>
> bash
ok
>
>> What type of window are you in? (eg. xterm, text console, emacs shell,
>> etc.)
>>
>
> urxvt
eh?
perldoc Tk::Scrolled works fine on perl 5.10.0 in a Kconsole window
with LANG either en_US or en_US.utf8
So sounds like a TERM / termcap / emulation problem with urxvt to me.
------------------------------
Date: Tue, 20 Apr 2010 12:51:48 -0500
From: "Mumia W." <paduille.4061.mumia.w+nospam@earthlink.net>
Subject: Re: Pod errors: Unterminated S<...> sequence
Message-Id: <upidnSL5_ZnGd1DWnZ2dnUVZ_t-dnZ2d@earthlink.com>
On 04/20/2010 09:01 AM, Steve C wrote:
>>> What type of window are you in? (eg. xterm, text console, emacs
>>> shell, etc.)
>>>
>>
>> urxvt
>
> eh?
>
> perldoc Tk::Scrolled works fine on perl 5.10.0 in a Kconsole window
> with LANG either en_US or en_US.utf8
>
> So sounds like a TERM / termcap / emulation problem with urxvt to me.
I don't know. I seems to be deeper than that.
Here is the Scrolled.pod on my system:
http://home.earthlink.net/~mumia.w.18.spam/docs/Scrolled.pod
And here is the output of "perldoc ./Scrolled.pod > Scrolled.txt":
http://home.earthlink.net/~mumia.w.18.spam/docs/Scrolled.txt
I tried it using a simpler POD file of my own:
http://home.earthlink.net/~mumia.w.18.spam/docs/mine.pod
Here is the output:
http://home.earthlink.net/~mumia.w.18.spam/docs/mine.txt
As you see, the normal "S" construct usage is fine, but the one where
there is empty space between the angle brackets generates an error, and
no output is shown for that line. Many of the PODs on my system have the
"S" construct as seen in the Scrolled.pod that I posted above.
I get the same error with gnome-terminal and at a virtual terminal (VT).
BTW, what O/S are you using?
------------------------------
Date: Tue, 20 Apr 2010 14:34:13 -0400
From: Steve C <smallpond@juno.com>
Subject: Re: Pod errors: Unterminated S<...> sequence
Message-Id: <hqks3k$2cj$1@news.eternal-september.org>
Mumia W. wrote:
> On 04/20/2010 09:01 AM, Steve C wrote:
>>>> What type of window are you in? (eg. xterm, text console, emacs
>>>> shell, etc.)
>>>>
>>>
>>> urxvt
>>
>> eh?
>>
>> perldoc Tk::Scrolled works fine on perl 5.10.0 in a Kconsole window
>> with LANG either en_US or en_US.utf8
>>
>> So sounds like a TERM / termcap / emulation problem with urxvt to me.
>
> I don't know. I seems to be deeper than that.
>
> Here is the Scrolled.pod on my system:
> http://home.earthlink.net/~mumia.w.18.spam/docs/Scrolled.pod
>
> And here is the output of "perldoc ./Scrolled.pod > Scrolled.txt":
> http://home.earthlink.net/~mumia.w.18.spam/docs/Scrolled.txt
>
> I tried it using a simpler POD file of my own:
> http://home.earthlink.net/~mumia.w.18.spam/docs/mine.pod
>
> Here is the output:
> http://home.earthlink.net/~mumia.w.18.spam/docs/mine.txt
>
> As you see, the normal "S" construct usage is fine, but the one where
> there is empty space between the angle brackets generates an error, and
> no output is shown for that line. Many of the PODs on my system have the
> "S" construct as seen in the Scrolled.pod that I posted above.
>
> I get the same error with gnome-terminal and at a virtual terminal (VT).
> BTW, what O/S are you using?
On this system I'm running
Linux 2.6.27.38-170.2.113.fc10.i686 #1 SMP Wed Nov 4 17:55:39 EST 2009 i686 athlon i386 GNU/Linux
hmmm. Looks like it's time to update.
Most likely then it is the formatter perldoc uses: nroff troff groff or whatever.
I have groff-1.18.1.4-16.fc10.i386
------------------------------
Date: Tue, 20 Apr 2010 02:14:21 -0500
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <VfadnRaGrtnQyVDWnZ2dnUVZ_rqdnZ2d@giganews.com>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://www.rehabitation.com/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.liamg\100cm.j.dat/"
The above message is a Usenet post.
I don't recall having given anyone permission to use it on a Web site.
------------------------------
Date: Tue, 20 Apr 2010 08:29:26 +0200
From: Martijn Lievaart <m@rtij.nl.invlalid>
Subject: Re: Problems with "show tech" using the Net::Telnet Module
Message-Id: <67uv97-41p.ln1@news.rtij.nl>
On Mon, 19 Apr 2010 10:49:37 -0700, Asterix wrote:
> I've made a little script to capture the output of networking devices.
> Everything works fine, until I use the "show tech" command in an Cisco
> device.
> The script does not save anything form the "show tech", but I can see
> that the TELNET Session gets back some output. But I can't figure out
> how to save this output from "show tech" into a file.
> There is no problem with commands which produce smaller output. I don't
> want to use the "Net::Telnet:Cisco" Module:
There may be a completely other solution. Have a look at rancid and it's
clogin command. Maybe rancid already does what you are trying to do.
HTH,
M4
------------------------------
Date: Tue, 20 Apr 2010 19:17:16 +0100
From: Graham Drabble <usenet05@drabble.me.uk>
Subject: Threads and Directory Handles
Message-Id: <Xns9D60C4353D3D8grahamdrabblelineone@drabble.me.uk>
Hi,
I've just finished debugging a problem with one of my modules and
whilst I've now got it fixed I don't really understand why it broke.
I've reproduced a simplified version below.
My original module was:
---BEGIN---
package Me::File;
use strict;
use warnings;
BEGIN {
use Exporter ();
our ($VERSION, @ISA, @EXPORT, @EXPORT_OK, %EXPORT_TAGS);
$VERSION = 1.00;
@ISA = qw(Exporter);
@EXPORT_OK = qw(file_stats);
}
our @EXPORT_OK;
sub file_stats{
my $dir = shift;
opendir (DIR,$dir) or warn "Can't open $dir: $!";
my %files;
while (my $file = readdir(DIR)){
$files{$file}{'x'} = -x "$dir/$file";
$files{$file}{'e'} = -e "$dir/$file";
# Lots of other tests go here
}
return \%files;
}
1
---END---
Which worked as expected in a non-threaded program.
---BEGIN---
use strict;
use warnings;
use Me::File qw(file_stats);
my $files = file_stats('LOGS');
foreach my $file (keys %$files){
print "MAIN\t$file\n";
}
---END---
Outputs:
C:\Perl\script>perl threadtest.pl
MAIN 20100419.log
MAIN ..
MAIN .
however if you have a threaded program if fails.
---BEGIN---
use strict;
use warnings;
use Me::File qw(file_stats);
use threads;
my $files = file_stats('LOGS');
foreach my $file (keys %$files){
print "MAIN\t$file\n";
}
my $thr = threads->create('new_thread');
sleep(1);
print "Pre\n";
$thr->join;
print "Post\n";
sub new_thread{
my $files = file_stats('LOGS');
foreach my $file (keys %$files){
print threads->tid()."\t$file\n";
}
}
---END---
Outputs
C:\Perl\script>perl logtest.pl
MAIN 20100419.log
MAIN ..
MAIN .
Free to wrong pool 17b9a48 not 1963e58 at Me/File.pm line 23.
Pre
and perl crashes.
There are two fixes for this.
One is to add a close(DIR) before the return() in file_stats(). The
second is to change file_stats() to
---BEGIN---
sub file_stats{
my $dir = shift;
opendir (my $dirh,$dir) or warn "Can't open $dir: $!";
my %files;
while (my $file = readdir($dirh)){
$files{$file}{'x'} = -x "$dir/$file";
$files{$file}{'e'} = -e "$dir/$file";
# Lots of other tests go here
}
return \%files;
}
---END---
It looks as though the problem is that then open DIRHANDLE breaks
when the new thread is created but I don't really understand why. Any
ideas?
If it helps:
C:\Perl\script>perl -v
This is perl, v5.10.0 built for MSWin32-x86-multi-thread
(with 5 registered patches, see perl -V for more detail)
running under Windows Vista.
--
Graham Drabble
http://www.drabble.me.uk/
------------------------------
Date: Tue, 20 Apr 2010 20:12:36 +0100
From: Graham Drabble <usenet05@drabble.me.uk>
Subject: Re: Threads and Directory Handles
Message-Id: <Xns9D60CD964303grahamdrabblelineone@drabble.me.uk>
On 20 Apr 2010 Graham Drabble <usenet05@drabble.me.uk> wrote in
news:Xns9D60C4353D3D8grahamdrabblelineone@drabble.me.uk:
> There are two fixes for this.
>
> One is to add a close(DIR) before the return() in file_stats(). The
> second is to change file_stats() to
I do, of course, mean closedir(DIR), in the above.
--
Graham Drabble
http://www.drabble.me.uk/
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 2915
***************************************
