[30432] in Perl-Users-Digest
Perl-Users Digest, Issue: 1675 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Jun 27 06:09:44 2008
Date: Fri, 27 Jun 2008 03: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 Fri, 27 Jun 2008 Volume: 11 Number: 1675
Today's topics:
Re: 'nobody' using sudo -- scary! <ben@morrow.me.uk>
new CPAN modules on Fri Jun 27 2008 (Randal Schwartz)
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Redirecting STDOUT under ActivePerl on Windows XP <kst-u@mib.org>
Re: Redirecting STDOUT under ActivePerl on Windows XP <brian.helterline@hp.com>
Re: Redirecting STDOUT under ActivePerl on Windows XP <kst-u@mib.org>
Re: run application from perl nonblocking? <szrRE@szromanMO.comVE>
Re: Simplest way (or module) to tweak query in CGI serv jerrykrinock@gmail.com
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 26 Jun 2008 22:43:05 +0100
From: Ben Morrow <ben@morrow.me.uk>
Subject: Re: 'nobody' using sudo -- scary!
Message-Id: <94fdj5-6mc2.ln1@osiris.mauzo.dyndns.org>
Quoth Johnny <schafer.dave@gmail.com>:
>
> Given a perl based web application, running as 'nobody' with a need to
> execute some privileged command, what approach is recommended?
Stick the details of what to do in a file somewhere, and run a program
out of root's crontab to check the list and perform the commands.
*Obviously* you will need extremely careful checking of the contents of
that list; you will want to write the root command in Perl, and use
taint mode.
Ben
--
Razors pain you / Rivers are damp
Acids stain you / And drugs cause cramp. [Dorothy Parker]
Guns aren't lawful / Nooses give
Gas smells awful / You might as well live. ben@morrow.me.uk
------------------------------
Date: Fri, 27 Jun 2008 04:42:21 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Fri Jun 27 2008
Message-Id: <K33uEL.CC9@zorch.sf-bay.org>
The following modules have recently been added to or updated in the
Comprehensive Perl Archive Network (CPAN). You can install them using the
instructions in the 'perlmodinstall' page included with your Perl
distribution.
Apache2-ModProxyPerlHtml-2.4
http://search.cpan.org/~darold/Apache2-ModProxyPerlHtml-2.4/
----
B-Generate-1.12_07
http://search.cpan.org/~gruber/B-Generate-1.12_07/
Create your own op trees.
----
B-Generate-1.12_08
http://search.cpan.org/~rurban/B-Generate-1.12_08/
Create your own op trees.
----
CGI-Application-Bouquet-Rose-1.00
http://search.cpan.org/~rsavage/CGI-Application-Bouquet-Rose-1.00/
Generate a set of CGI::Application-based classes
----
Cache-Cascade-0.04
http://search.cpan.org/~nuffin/Cache-Cascade-0.04/
Get/set values to/from a group of caches, with some advanced semantics.
----
Cache-FastMmap-1.28
http://search.cpan.org/~robm/Cache-FastMmap-1.28/
Uses an mmap'ed file to act as a shared memory interprocess cache
----
Catalyst-Plugin-DebugCookie-0.999001
http://search.cpan.org/~jgoulah/Catalyst-Plugin-DebugCookie-0.999001/
Catalyst plugin to turn on debug when a secure cookie and a query param are set
----
Catalyst-Plugin-ForwardChained-0.02
http://search.cpan.org/~ukautz/Catalyst-Plugin-ForwardChained-0.02/
Forwarding to "Chain"-Actions in Catalyst
----
Catalyst-Plugin-ForwardChained-0.03
http://search.cpan.org/~ukautz/Catalyst-Plugin-ForwardChained-0.03/
Forwarding to "Chain"-Actions in Catalyst
----
Const-0.01
http://search.cpan.org/~dankogai/Const-0.01/
Facility for creating read-only variables
----
Crypt-EAX-0.03
http://search.cpan.org/~nuffin/Crypt-EAX-0.03/
Encrypt and authenticate data in EAX mode
----
Crypt-Util-0.08
http://search.cpan.org/~nuffin/Crypt-Util-0.08/
A lightweight Crypt/Digest convenience API
----
DBIx-Class-SingletonRows-0.11
http://search.cpan.org/~dcantrell/DBIx-Class-SingletonRows-0.11/
make database rows returned by DBIx::Class into singletons
----
DBIx-Perlish-0.42
http://search.cpan.org/~gruber/DBIx-Perlish-0.42/
a perlish interface to SQL databases
----
Devel-INC-Sorted-0.02
http://search.cpan.org/~nuffin/Devel-INC-Sorted-0.02/
Keep your hooks in the begining of @INC
----
Fey-0.07
http://search.cpan.org/~drolsky/Fey-0.07/
Better SQL Generation Through Perl
----
Filter-SQL-0.06
http://search.cpan.org/~kazuho/Filter-SQL-0.06/
embedded SQL for perl
----
Getopt-Param-0.0.5
http://search.cpan.org/~dmuey/Getopt-Param-0.0.5/
param() style opt handling
----
Getopt-Param-Tiny-0.5
http://search.cpan.org/~dmuey/Getopt-Param-Tiny-0.5/
Subset of Getopt::Param functionality with smaller memory footprint
----
Git-FastExport-0.01
http://search.cpan.org/~book/Git-FastExport-0.01/
A module to parse the output of git-fast-export
----
Imager-QRCode-0.02
http://search.cpan.org/~kurihara/Imager-QRCode-0.02/
Generate QR Code with Imager using libqrencode
----
Imager-QRCode-0.03
http://search.cpan.org/~kurihara/Imager-QRCode-0.03/
Generate QR Code with Imager using libqrencode
----
Jifty-Plugin-WyzzEditor-0.01
http://search.cpan.org/~yvesago/Jifty-Plugin-WyzzEditor-0.01/
Simple WYSIWYG online editor for Jifty textarea
----
LEOCHARRE-Database-1.16
http://search.cpan.org/~leocharre/LEOCHARRE-Database-1.16/
common database methods for oo
----
LWP-Protocol-sftp-0.03
http://search.cpan.org/~salva/LWP-Protocol-sftp-0.03/
adds support for SFTP uris to LWP package
----
Math-BaseCalc-1.012
http://search.cpan.org/~kwilliams/Math-BaseCalc-1.012/
Convert numbers between various bases
----
MooseX-Types-Set-Object-0.02
http://search.cpan.org/~nuffin/MooseX-Types-Set-Object-0.02/
Set::Object type with coercions and stuff.
----
Net-SNMP-Mixin-IfInfo-0.05
http://search.cpan.org/~gaissmai/Net-SNMP-Mixin-IfInfo-0.05/
mixin class for interface related infos
----
POE-1.0003
http://search.cpan.org/~rcaputo/POE-1.0003/
portable multitasking and networking framework for Perl
----
POE-Component-IRC-5.84
http://search.cpan.org/~bingos/POE-Component-IRC-5.84/
a fully event-driven IRC client module.
----
POE-Component-Pluggable-1.10
http://search.cpan.org/~bingos/POE-Component-Pluggable-1.10/
A base class for creating plugin enabled POE Components.
----
POE-Component-Server-Bayeux-0.02
http://search.cpan.org/~ewaters/POE-Component-Server-Bayeux-0.02/
Bayeux/cometd server implementation in POE
----
Parse-Eyapp-1.111
http://search.cpan.org/~casiano/Parse-Eyapp-1.111/
Extensions for Parse::Yapp
----
Pg-Pcurse-0.20
http://search.cpan.org/~ioannis/Pg-Pcurse-0.20/
Monitors a Postgres cluster
----
Proc-Simple-1.23
http://search.cpan.org/~mschilli/Proc-Simple-1.23/
launch and control background processes
----
RDF-Trine-0.108_02
http://search.cpan.org/~gwilliams/RDF-Trine-0.108_02/
An RDF Framework for Perl.
----
Rose-DBx-Bouquet-1.00
http://search.cpan.org/~rsavage/Rose-DBx-Bouquet-1.00/
Use a database schema to generate Rose-based source code
----
Script-Toolbox-0.22
http://search.cpan.org/~eckardt/Script-Toolbox-0.22/
Framework for the daily business scripts
----
SmartMatch-Sugar-0.02
http://search.cpan.org/~nuffin/SmartMatch-Sugar-0.02/
Smart match friendly tests.
----
Sort-Packed-0.05
http://search.cpan.org/~salva/Sort-Packed-0.05/
Sort records packed in a vector
----
Statistics-ANOVA-0.04
http://search.cpan.org/~rgarton/Statistics-ANOVA-0.04/
Perform oneway analyses of variance
----
Statistics-ANOVA-0.05
http://search.cpan.org/~rgarton/Statistics-ANOVA-0.05/
Perform oneway analyses of variance
----
Statistics-FisherPitman-0.01
http://search.cpan.org/~rgarton/Statistics-FisherPitman-0.01/
Randomization-based alternative to one-way independent groups ANOVA; unequal variances okay
----
Statistics-Sequences-0.02
http://search.cpan.org/~rgarton/Statistics-Sequences-0.02/
Tests of sequential structure in the form of runs, joins, bunches, etc.
----
Statistics-Zed-0.01
http://search.cpan.org/~rgarton/Statistics-Zed-0.01/
Basic ztest/zscore, Fisher's r-to-z, z-to-r, et al.
----
Sys-Info-0.52_9
http://search.cpan.org/~burak/Sys-Info-0.52_9/
Fetch information from the host system
----
Text-FakeXML-0.01
http://search.cpan.org/~jv/Text-FakeXML-0.01/
Creating text with <things>.
----
WWW-Comic-Plugin-LeastICouldDo-0.01
http://search.cpan.org/~bigpresh/WWW-Comic-Plugin-LeastICouldDo-0.01/
WWW::Comic plugin to fetch LeastICouldDo comic
----
Win32-0.37
http://search.cpan.org/~jdb/Win32-0.37/
Interfaces to some Win32 API Functions
----
XML-RSS-PicLens-0.01
http://search.cpan.org/~andya/XML-RSS-PicLens-0.01/
Create a PicLens compatible RSS feed
----
Xen-Control-0.04
http://search.cpan.org/~jkutej/Xen-Control-0.04/
control and fetch information about xen domains
----
sapnwrfc-0.17
http://search.cpan.org/~piers/sapnwrfc-0.17/
SAP Netweaver RFC support for Perl
If you're an author of one of these modules, please submit a detailed
announcement to comp.lang.perl.announce, and we'll pass it along.
This message was generated by a Perl program described in my Linux
Magazine column, which can be found on-line (along with more than
200 other freely available past column articles) at
http://www.stonehenge.com/merlyn/LinuxMag/col82.html
print "Just another Perl hacker," # the original
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
------------------------------
Date: Fri, 27 Jun 2008 06:14:31 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <bz%8k.8212$89.1563@nlpi069.nbdc.sbc.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.8 $)
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_group_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.noitatibaher\100cmdat/"
------------------------------
Date: 26 Jun 2008 14:33:23 -0700
From: Keith Thompson <kst-u@mib.org>
Subject: Redirecting STDOUT under ActivePerl on Windows XP
Message-Id: <lzbq1nzxss.fsf@stalkings.ghoti.net>
I want to redirect STDOUT to a file, and have the redirection apply to
any programs that I invoke. Here's a brief outline of what I'm doing
(full sources to follow):
open SAVE_STDOUT, '>&STDOUT' or die "SAVE_STDOUT: $!\n";
open STDOUT, '>', 'log.txt';
system "some_command";
close STDOUT;
open STDOUT, '>&SAVE_STDOUT' or die "Restoring STDOUT: $!\n";
The invoked command itself invokes another command. I want to collect
the standard output of both commands in a single file. (I also want
to redirect stderr, but I'm leaving that out for now.)
Under Cygwin (Perl 5.8.8) and Linux (Perl 5.8.0), it works fine.
Under Windows XP (ActiveState Perl 5.6.1), the output of the invoked
command is properly redirected to the file, but the output of the
inner command is just lost, though I've confirmed that it is executed.
Any suggestions? (Upgrading ActiveState Perl is not currently an
option, but it would be nice to know if a newer version fixes this.)
I'm using 3 Perl programs, called "outer.pl", "middle.pl", and
"inner.pl" (the ".pl" suffix is needed to make Windows recognize that
these are Perl scripts).
===== outer.pl =====
#!/usr/bin/perl
use strict;
use warnings;
print "Running on $^O\n";
my $prefix;
if ($^O =~ /^mswin/i) {
$prefix = '.\\';
}
else {
$prefix = './';
}
print "Begin outer\n";
open SAVE_STDOUT, '>&STDOUT' or die "SAVE_STDOUT: $!\n";
print SAVE_STDOUT if 0; # avoid "used only once" warning
open STDOUT, '>', 'log.txt';
print "outer calling middle\n";
system "${prefix}middle.pl";
print "outer after middle\n";
close STDOUT;
open STDOUT, '>&SAVE_STDOUT' or die "Restoring STDOUT: $!\n";
print "End outer\n";
open my $OUTER_LOG, '>', 'outer.log';
print $OUTER_LOG "outer, pid=$$\n";
close $OUTER_LOG;
===== end outer.pl =====
===== middle.pl =====
#!/usr/bin/perl
use strict;
use warnings;
my $prefix;
if ($^O =~ /^mswin/i) {
$prefix = '.\\';
}
else {
$prefix = './';
}
print "Begin middle\n";
system "${prefix}inner.pl";
print "End middle\n";
open my $MIDDLE_LOG, '>', 'middle.log';
print $MIDDLE_LOG "middle, pid=$$\n";
close $MIDDLE_LOG;
===== end middle.pl =====
===== inner.pl =====
#!/usr/bin/perl
use strict;
use warnings;
print "In inner\n";
open my $INNER_LOG, '>', 'inner.log';
print $INNER_LOG "inner, pid=$$\n";
close $INNER_LOG;
===== end inner.pl =====
On Cygwin or Linux, log.txt contains:
==========
outer calling middle
Begin middle
In inner
End middle
outer after middle
==========
On Windows (executing outer.pl from a CMD window), log.txt contains:
==========
outer calling middle
Begin middle
In inner
End middle
outer after middle
==========
--
Keith Thompson (The_Other_Keith) kst-u@mib.org <http://www.ghoti.net/~kst>
Nokia
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"
------------------------------
Date: Thu, 26 Jun 2008 16:53:39 -0700
From: Brian Helterlilne <brian.helterline@hp.com>
Subject: Re: Redirecting STDOUT under ActivePerl on Windows XP
Message-Id: <g41a64$rn4$1@usenet01.boi.hp.com>
Keith Thompson wrote:
> I want to redirect STDOUT to a file, and have the redirection apply to
> any programs that I invoke. Here's a brief outline of what I'm doing
> (full sources to follow):
>
> open SAVE_STDOUT, '>&STDOUT' or die "SAVE_STDOUT: $!\n";
> open STDOUT, '>', 'log.txt';
> system "some_command";
> close STDOUT;
> open STDOUT, '>&SAVE_STDOUT' or die "Restoring STDOUT: $!\n";
>
> The invoked command itself invokes another command. I want to collect
> the standard output of both commands in a single file. (I also want
> to redirect stderr, but I'm leaving that out for now.)
>
> Under Cygwin (Perl 5.8.8) and Linux (Perl 5.8.0), it works fine.
>
> Under Windows XP (ActiveState Perl 5.6.1), the output of the invoked
> command is properly redirected to the file, but the output of the
> inner command is just lost, though I've confirmed that it is executed.
>
> Any suggestions? (Upgrading ActiveState Perl is not currently an
> option, but it would be nice to know if a newer version fixes this.)
>
> I'm using 3 Perl programs, called "outer.pl", "middle.pl", and
> "inner.pl" (the ".pl" suffix is needed to make Windows recognize that
> these are Perl scripts).
>
> ===== outer.pl =====
> #!/usr/bin/perl
>
> use strict;
> use warnings;
>
> print "Running on $^O\n";
>
> my $prefix;
> if ($^O =~ /^mswin/i) {
> $prefix = '.\\';
$prefix = 'perl .\\';
> }
> else {
> $prefix = './';
> }
>
> print "Begin outer\n";
>
> open SAVE_STDOUT, '>&STDOUT' or die "SAVE_STDOUT: $!\n";
> print SAVE_STDOUT if 0; # avoid "used only once" warning
>
> open STDOUT, '>', 'log.txt';
>
> print "outer calling middle\n";
> system "${prefix}middle.pl";
> print "outer after middle\n";
>
> close STDOUT;
> open STDOUT, '>&SAVE_STDOUT' or die "Restoring STDOUT: $!\n";
>
> print "End outer\n";
>
> open my $OUTER_LOG, '>', 'outer.log';
> print $OUTER_LOG "outer, pid=$$\n";
> close $OUTER_LOG;
> ===== end outer.pl =====
>
> ===== middle.pl =====
> #!/usr/bin/perl
>
> use strict;
> use warnings;
>
> my $prefix;
> if ($^O =~ /^mswin/i) {
> $prefix = '.\\';
$prefix = 'perl .\\';
> }
> else {
> $prefix = './';
> }
> print "Begin middle\n";
>
> system "${prefix}inner.pl";
>
> print "End middle\n";
>
> open my $MIDDLE_LOG, '>', 'middle.log';
> print $MIDDLE_LOG "middle, pid=$$\n";
> close $MIDDLE_LOG;
> ===== end middle.pl =====
>
> ===== inner.pl =====
> #!/usr/bin/perl
>
> use strict;
> use warnings;
>
> print "In inner\n";
>
> open my $INNER_LOG, '>', 'inner.log';
> print $INNER_LOG "inner, pid=$$\n";
> close $INNER_LOG;
> ===== end inner.pl =====
>
> On Cygwin or Linux, log.txt contains:
> ==========
> outer calling middle
> Begin middle
> In inner
> End middle
> outer after middle
> ==========
>
> On Windows (executing outer.pl from a CMD window), log.txt contains:
> ==========
> outer calling middle
> Begin middle
> In inner
If this were true, you wouldn't have a problem. I suspect a cut and
paste error. 'In inner' should be missing.
> End middle
> outer after middle
> ==========
>
I'm running perl 5.8.8 and got the same behavior you did. I've had
trouble with letting DOS do the file association (running ./outer.pl vs.
perl outer.pl)
--
-brian
------------------------------
Date: 26 Jun 2008 17:54:34 -0700
From: Keith Thompson <kst-u@mib.org>
Subject: Re: Redirecting STDOUT under ActivePerl on Windows XP
Message-Id: <lzy74ry9x1.fsf@stalkings.ghoti.net>
Brian Helterlilne <brian.helterline@hp.com> writes:
> Keith Thompson wrote:
> > I want to redirect STDOUT to a file, and have the redirection apply to
> > any programs that I invoke. Here's a brief outline of what I'm doing
> > (full sources to follow):
> > open SAVE_STDOUT, '>&STDOUT' or die "SAVE_STDOUT: $!\n";
> > open STDOUT, '>', 'log.txt';
> > system "some_command";
> > close STDOUT;
> > open STDOUT, '>&SAVE_STDOUT' or die "Restoring STDOUT: $!\n";
[...]
> > if ($^O =~ /^mswin/i) {
> > $prefix = '.\\';
>
> $prefix = 'perl .\\';
> > }
> > else {
> > $prefix = './';
> > }
[...]
> > On Cygwin or Linux, log.txt contains:
> > ==========
> > outer calling middle
> > Begin middle
> > In inner
> > End middle
> > outer after middle
> > ==========
> > On Windows (executing outer.pl from a CMD window), log.txt contains:
> > ==========
> > outer calling middle
> > Begin middle
> > In inner
>
> If this were true, you wouldn't have a problem. I suspect a cut and
> paste error. 'In inner' should be missing.
>
> > End middle
> > outer after middle
> > ==========
Right on both counts. The "In inner" is missing, and yes, it was a
copy-and-paste error.
> I'm running perl 5.8.8 and got the same behavior you did. I've had
> trouble with letting DOS do the file association (running ./outer.pl
> vs. perl outer.pl)
Running .\outer.pl works for me, but yes, "perl outer.pl" should work
as well.
--
Keith Thompson (The_Other_Keith) kst-u@mib.org <http://www.ghoti.net/~kst>
Nokia
"We must do something. This is something. Therefore, we must do this."
-- Antony Jay and Jonathan Lynn, "Yes Minister"
------------------------------
Date: Thu, 26 Jun 2008 11:15:03 -0700
From: "szr" <szrRE@szromanMO.comVE>
Subject: Re: run application from perl nonblocking?
Message-Id: <g40mb501hci@news4.newsguy.com>
Jürgen Exner wrote:
> "szr" <szrRE@szromanMO.comVE> wrote:
>> Jim Gibson wrote:
>>> You should be aware that many of the most helpful regulars here (not
>>> me!) do not use Google Groups to read Usenet articles.
>>
>> That's fine, but there are people who do use it.
>
> Their choice. If they are happy with a slow, cumbersome interface in a
> tool that provides no functionality to speak of, then so be it. But
> even OE has tons more functionality than that crappy web page.
Agreed.
>> What does that change?
>
> It changes the perception. Usenet is not a division of Google as some
> people seem to believe and the way you see articles organized in
> Google is _not_ the typical way people read Usenet.
Also agreed.
> Typical example:
> "But I wrote 3 articles above...." Dude, how would you know which
> article is 3 articles above in _MY_ sorting order at _THIS_ point in
> time.
Again, agreed; some people who read news groups via Google Groups end up
thinking it is some glorified web forum.
>>> Other newsreaders do not present the entire thread to you (and this
>>> is a good thing!)
>>
>> How is that possibly a good thing?
>
> Why would I possibly want to wade through and reread a large pile of
> old articles in search of new contributions?
I was talking about a list in which you visibily see the structure of
the thread. You select which article you want to read, but it's nice to
know where you are in the thread.
For example:
First Post | by Foo | date
+ Reply to First | by Bar | date
| + Reply to Reply to First | by Foo | date
+ 2nd Reply to First | by Baz | date
...
How ever it's displayed, any real reader should have some way of showing
you what the thread looks like.
>> Why would one not want to at least
>> have the option of seeing the thread tree? IMHO, any news reader that
>> cannot show the tree (so that one may see the thread structure) is
>> incomplete.
>
> Option to expand the thread including old articles yes.
Yes, this is what I'm talking about.
> As default view absolutely no way.
Yes, by default threads should be collapsed. You expand the thread you
want to read.
> Besides, even expanding the old thread tree works only as long as
> articles have not expired, are still available on the server, have not
> been filtered, etc., etc.
This should be a non issue if your reader has proper caching
configuration, allowing you to keep downloaded messages.
--
szr
------------------------------
Date: Thu, 26 Jun 2008 14:21:17 -0700 (PDT)
From: jerrykrinock@gmail.com
Subject: Re: Simplest way (or module) to tweak query in CGI server-side validation
Message-Id: <300ff559-7247-4bd3-a0c5-6a488d1b1c32@l64g2000hse.googlegroups.com>
On Jun 12, 7:37=A0pm, Gunnar Hjalmarsson <nore...@gunnar.cc> wrote:
> Sounds like you don't want to just redirect, after all, but rather
> submit a new query. The libwww-perl family of modules can do that; see
> for instance LWP::UserAgent.
Thank you, Gunnar. After playing with this for a couple weeks (not
full-time), I decided that I ^really^do^ want a redirect, not to
submit a new query. The reason is that I need the user to get a
response from the site that I redirected to, not my redirecting/
tweaking script. I could not find any function in LWP::UserAgent to
do a redirect, so I used CGI.
I have uploaded two "bonehead" scripts:
"Redirector.pl" redirects to "QueryHandler.pl", using CGI's
"redirect" function.
"QueryHandler.pl echoes the query back to the user, using CGI's
"Dump()" function.
Result of Experiments:
If you "go direct", entering into your web browser something like:
http://sheepsystems.com/cgi-test/sales/QueryHandler.pl?name=3DJerry&colo=
r=3Dblue
you get your query echoed back to you as expected.
But if you try and do that through my redirect, entering
http://sheepsystems.com/cgi-test/sales/Redirector.pl?name=3DJerry&color=
=3Dblue
it gets redirected OK but you don't get your query pairs echoed back.
This is because QueryHandler.pl does not get the query pairs. (I have
also confirmed this by writing to a log file.)
Is there any way to pass a query through a redirecting script, or am I
expecting something that is fundamentally impossible? (Recall that in
my actual application, the redirecting script will tweak some of the
values in the query.)
Thanks again,
Jerry
******** Redirector.pl *****************
#!/usr/bin/perl
use strict ;
use warnings ;
use CGI ;
my $httpQuery =3D new CGI;
my $redirectURL =3D "http://sheepsystems.com/cgi-test/sales/
QueryHandler.pl" ;
print $httpQuery->redirect($redirectURL) ;
exit() ;
******** QueryHandler.pl *****************
#!/usr/bin/perl
use strict ;
use warnings ;
use CGI ;
my $httpQuery =3D new CGI ;
my $returnBody .=3D "<p>Module CGI got query list:</p>" ;
my $cgiDump =3D $httpQuery->Dump() ;
if (defined($cgiDump)) {
$returnBody .=3D $cgiDump ;
}
# Output to client application
print "Content-type: text/html\n";
print "Status: ", 200, " \n\n";
print "<html>$returnBody</html>" ;
exit() ;
------------------------------
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:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#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 1675
***************************************
