[22538] in Perl-Users-Digest
Perl-Users Digest, Issue: 4759 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Mar 25 06:10:38 2003
Date: Tue, 25 Mar 2003 03:10:10 -0800 (PST)
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, 25 Mar 2003 Volume: 10 Number: 4759
Today's topics:
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: Problem with Getopt::Std and getopts().... <bik.mido@tiscalinet.it>
Problem with LWP::UserAgent <bol@adv.magwien.gv.at>
Re: Simple, but I can't figure it out. <tore@aursand.no>
Re: Simple, but I can't figure it out. <tassilo.parseval@rwth-aachen.de>
Re: sort by columns (Randal L. Schwartz)
Re: sort by columns <grazz@nyc.rr.com>
Re: sort by columns <tore@aursand.no>
Re: update value in flat file (Helgi Briem)
Re: update value in flat file (Anno Siegel)
Re: why heredoc? was: Re: print here-documents question (Tad McClellan)
Win32 process ID & status given process (program) name (Anand Ramamurthy)
Re: WWW::Mechanize newbie question <bigj@kamelfreund.de>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 25 Mar 2003 02:22:17 -0600
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <Mw6dnTEWdJYkjB2jXTWcrg@august.net>
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.4 $)
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.
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://mail.augustmail.com/~tadmc/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
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
"Jeopardy" (because the answer comes before the question), or
"TOFU".
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 <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Tue, 25 Mar 2003 09:37:24 +0100
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: Problem with Getopt::Std and getopts()....
Message-Id: <82508v4q9oiclotovkrta0p7csvrkbq97j@4ax.com>
On Mon, 24 Mar 2003 14:46:54 GMT, "Jürgen Exner"
<jurgenex@hotmail.com> wrote:
>I'm not sure if a plain 16-bit DOS version of perl even exists (I highly
>doubt it).
This is irrelevant to the matter being discussed...
>So for all practical purposes we are talking about the 32-bit Windows-based
>cmd.exe command line interpreter, not the 16-bit command.com original DOS
>shell.
You're _partly_ right: cmd.exe is actually Windows NT OS family
command processor, but other 32-bit Windows versions (widely available
and used) still use command.com.
I was aware of _some_ advantages of cmd.exe over the old shell (and I
thought to myself "wow, it's becoming more *sh-ish!!" when I
discovered them), but not this particular one...
Michele
--
>It's because the universe was programmed in C++.
No, no, it was programmed in Forth. See Genesis 1:12:
"And the earth brought Forth ..."
- Robert Israel on sci.math, thread "Why numbers?"
------------------------------
Date: Tue, 25 Mar 2003 11:03:17 +0100
From: "Ferry Bolhar" <bol@adv.magwien.gv.at>
Subject: Problem with LWP::UserAgent
Message-Id: <1048586622.156714@mozart.adv.magwien.gv.at>
Hi to all,
I use LWP::UserAgent to poll a WEB application (IIS). Seems to run without
problems, but sometimes, the call
$ans = $ua -> request($anf);
returns in $ans->status_line:
500 Can't locate object method "configure" via package "Net::HTTP" (perhaps
you forgot to load "Net::HTTP" ?).
Doesn't look like an answer from IIS, doesn't it?
This status line even comes when I do a use 'Net::HTTP'; !
I should mention that this never comes when running the script
interactively, only when started from a crontab job. And yes, I have checked
@INC, it's the same in my interactive environment and in the environment of
the crontab job.
What's wrong here?
BTW: this is Red Hat Linux V7.2 and Perl V5.6.1.
MTIA and best greetings, Ferry
--
Ing. Ferry Bolhar
Municipality of Vienna, Department 14
A-1010 Vienna / AUSTRIA
E-mail: bol@adv.magwien.gv.at
------------------------------
Date: Tue, 25 Mar 2003 09:25:16 +0100
From: "Tore Aursand" <tore@aursand.no>
Subject: Re: Simple, but I can't figure it out.
Message-Id: <pan.2003.03.25.00.17.23.114631@aursand.no>
On Mon, 24 Mar 2003 22:36:54 +0000, Bigus wrote:
> open(TMP,">news.txt");
> print TMP "24\n";
> for($i = 0;$i <=1;$i++){
> print TMP "$lines[$i]\n";
> }
> close(TMP);
Use splice() instead;
open( TMP, ">news.txt" ) || die "Couldn't open file: $!\n";
print TMP splice( @lines, 0, 20 );
close( TMP );
The for() loop you mentions above is something from the evil C/C++ planet.
:)
--
Tore Aursand
------------------------------
Date: 25 Mar 2003 08:43:46 GMT
From: "Tassilo v. Parseval" <tassilo.parseval@rwth-aachen.de>
Subject: Re: Simple, but I can't figure it out.
Message-Id: <b5p4s2$ilj$1@nets3.rz.RWTH-Aachen.DE>
Also sprach Tore Aursand:
> On Mon, 24 Mar 2003 22:36:54 +0000, Bigus wrote:
>> open(TMP,">news.txt");
>> print TMP "24\n";
>> for($i = 0;$i <=1;$i++){
>> print TMP "$lines[$i]\n";
>> }
>> close(TMP);
>
> Use splice() instead;
>
> open( TMP, ">news.txt" ) || die "Couldn't open file: $!\n";
> print TMP splice( @lines, 0, 20 );
> close( TMP );
The above will remove elements 0 to 20 from the array and is thus
destructive.
Why not just a list-slice?
open TMP, ">news.txt" or die $!;
print TMP $_, "\n" for @lines[0 .. 20];
close TMP;
Tassilo
--
$_=q#",}])!JAPH!qq(tsuJ[{@"tnirp}3..0}_$;//::niam/s~=)]3[))_$-3(rellac(=_$({
pam{rekcahbus})(rekcah{lrePbus})(lreP{rehtonabus})!JAPH!qq(rehtona{tsuJbus#;
$_=reverse,s+(?<=sub).+q#q!'"qq.\t$&."'!#+sexisexiixesixeseg;y~\n~~dddd;eval
------------------------------
Date: Tue, 25 Mar 2003 05:52:45 GMT
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Gilles <gproulx@tva.ca>
Subject: Re: sort by columns
Message-Id: <84da023c57e5c7024ea67bc4bdcf5171@news.teranews.com>
>>>>> "Gilles" == Gilles <gproulx@tva.ca> writes:
Gilles> I need to sort a file that contain 13 columns in the following format :
You might want to look at Sort::Fields in the CPAN then.
(And someone else in this thread will probably attach something with
my namesake in it... :)
print "Just another Perl hacker,"
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
------------------------------
Date: Tue, 25 Mar 2003 06:56:29 GMT
From: Steve Grazzini <grazz@nyc.rr.com>
Subject: Re: sort by columns
Message-Id: <x4Tfa.13265$pi.2523209@twister.nyc.rr.com>
Gilles <gproulx@tva.ca> wrote:
> I need to sort a file that contain 13 columns in the following format :
Please don't multi-post.
<56Qfa.3045$062.355771@news20.bellglobal.com> comp.lang.perl
<S6Qfa.3046$062.355691@news20.bellglobal.com> comp.lang.perl.misc
<p4Qfa.3042$062.355255@news20.bellglobal.com> comp.unix.programmer
<J3Qfa.3041$062.355019@news20.bellglobal.com> comp.lang.tcl
<f3Qfa.3040$062.353258@news20.bellglobal.com> comp.unix.shell
<B5Qfa.3043$062.355646@news20.bellglobal.com> alt.perl
--
Steve
------------------------------
Date: Tue, 25 Mar 2003 10:07:32 +0100
From: "Tore Aursand" <tore@aursand.no>
Subject: Re: sort by columns
Message-Id: <pan.2003.03.25.09.02.37.707010@aursand.no>
On Mon, 24 Mar 2003 22:34:07 -0500, Gilles wrote:
> I need to sort a file that contain 13 columns [...]
Use the excellent Sort::Fields module available from CPAN;
my @sorted = fieldsort [ '4n', '5n', '6n',
'7n', '1', '8n' ], @lines;
These parameters should work for your data. Haven't tested it, though, so
stick with 'perldoc Sort::Fields' if you encounter problems.
--
Tore Aursand
------------------------------
Date: Tue, 25 Mar 2003 10:17:34 GMT
From: helgi@decode.is (Helgi Briem)
Subject: Re: update value in flat file
Message-Id: <3e802c82.3969071613@news.cis.dfn.de>
On Mon, 24 Mar 2003 23:10:28 +0100, Gunnar Hjalmarsson
<noreply@gunnar.cc> wrote:
>Oh, "reinvent the wheel" you mean? Sure, I agree that it's wise to get
>a basic understanding about changing a line before using such a nifty
>module.
>
>Btw, would you agree that that approach is advisable also when it
>comes to CGI? In other words, that just "use CGI;" isn't necessarily
>the best answer to every CGI related question? ;-)
Sure, if you have a few months to waste on what is
essentially a rather trivial interface/wrapper issue.
Me, I have better things to do.
--
Regards, Helgi Briem
helgi DOT briem AT decode DOT is
------------------------------
Date: 25 Mar 2003 10:17:59 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: update value in flat file
Message-Id: <b5pacn$sft$1@mamenchi.zrz.TU-Berlin.DE>
Gunnar Hjalmarsson <noreply@gunnar.cc> wrote in comp.lang.perl.misc:
> Anno Siegel wrote:
> > Gunnar Hjalmarsson <noreply@gunnar.cc> wrote in comp.lang.perl.misc:
> >>If OP is using 5.6.1 or previous, he won't get the
> >>Tie::File recommendation by checking the FAQ.
> >
> > Oh, I see. Yes, apparently it should run with older perls.
>
> Yes, 5.005 and above.
>
> > Though I'd often prefer people who ask this question did it the old
> > way and *learn*, on that occasion, what's involved in "changing a line
> > in a file". Then let them tie their files.
>
> Oh, "reinvent the wheel" you mean? Sure, I agree that it's wise to get
> a basic understanding about changing a line before using such a nifty
> module.
Well, the idea that a scalar read from a file magically stays connected
with the line it came from is rather common, perhaps because editors
*seem* to work this way. One possible reaction to this is to explain
that it is no so and show how a file update is really done. This is
what the old FAQ did. Another reaction is to say, okay, if people
expect it to work that way then let's make it work that way. That is
what the FAQ does now.
I guess it's a bit like automatic transmission. The old-timers say
it costs a lot of power, and you'll never learn to drive properly with
one of those, and anyway, where's the fun in driving without a gear
shift. Others just use it. They're both right :)
> Btw, would you agree that that approach is advisable also when it
> comes to CGI? In other words, that just "use CGI;" isn't necessarily
> the best answer to every CGI related question? ;-)
I have little experience with CGI.pm, though the few times I used
it (for nothing time-critical) were completely satisfactory.
One difference between Tie::File and CGI is that what Tie::File hides
is a single, basically simple procedure. CGI incorporates (and hides)
a lot of different, rather complex and often interdependent procedures.
I do understand that with the 6695-line CGI.pm people are asking for
a more lightweight alternative, one that covers only the essentials.
However, if you were to ask 10 or 20 people for their essentials, form
the union and implement that, I'm afraid the result wouldn't save much
over CGI.pm.
Anno
------------------------------
Date: Mon, 24 Mar 2003 18:59:41 -0600
From: tadmc@augustmail.com (Tad McClellan)
Subject: Re: why heredoc? was: Re: print here-documents question
Message-Id: <slrnb7vaft.5l4.tadmc@magna.augustmail.com>
Matija Papec <mpapec@yahoo.com> wrote:
> Bernard <bht@actrix.gen.nz> wrote:
>>print <<"EOF"
>><HTML>
>><SCRIPT>
>>var newLine = unescape("%0A");
>>alert("The correct email format is : " + newLine +
>>"username\@domain.extension");
>></SCRIPT>
>></HTML>
>>EOF
>
> IMO, it looks terribly ugly;
That depends on what is in the string that you are quoting.
I think this is harder to read than the above:
print "var newLine = unescape(\"%0A\")";
print "alert(\"The correct email format is : \" + newLine + \"username\@domain.extension\")";
Here docs are WYSIWYGish.
> is there any reason why Perl manuals still use
> it like an example of printing multiple lines?
What example are you referring to?
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: 24 Mar 2003 22:40:14 -0800
From: anand_ramamurthy@yahoo.com (Anand Ramamurthy)
Subject: Win32 process ID & status given process (program) name
Message-Id: <761041e6.0303242240.20459eb5@posting.google.com>
How do I get process id and status (alive, sleep, exited etc)
given a process name in Win32?
In UNIX we can do ps -ef | program name | cut -f .....
How do i get pid & more importantly status of the process?
Win32::Process functions give me status and id of the current
process. I need to get the id of child of this parent.
The Win32::Process PERL script starts a process whose id & status
I can check. This this process (using a Win32 executable: xxx.exe) starts
another process yyy.exe, how do I find the status and PID of yyy.exe
------------------------------
Date: Tue, 25 Mar 2003 11:00:52 +0100
From: "Janek Schleicher" <bigj@kamelfreund.de>
Subject: Re: WWW::Mechanize newbie question
Message-Id: <pan.2003.03.25.09.35.41.493426@kamelfreund.de>
Kelly Greer wrote at Tue, 25 Mar 2003 04:48:51 +0000:
> What do you have to do to be able to use the WWW::Mechanize Perl module on a
> windows machine? The current version from www.activestate.com doesn't seem
> to support this. Will this work on windows? Where do I get the code?
I can't answer whether it will work on Win* systems,
but you'll find the code in CPAN.
Either you search for it under http://search.cpan.org,
or you go directly to it under
http://search.cpan.org/author/PETDANCE/WWW-Mechanize-0.38/
Also under windows,
there should be the normal installation way
(unpack the .tar.gz file, perl Makefile.PL, make, make test, make
install). I looked a bit in the source code and it seems to be pure
Perlish, so it shouldn't be a real problem.
Best Wishes,
Janek
PS: Don't post to comp.lang.perl - This (nowadays dead) newsgroup had been
splitted some years ago in several ones. Just post to comp.lang.perl.misc
------------------------------
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.
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 V10 Issue 4759
***************************************
