[25941] in Perl-Users-Digest
Perl-Users Digest, Issue: 8160 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Thu Jun 9 21:05:17 2005
Date: Thu, 9 Jun 2005 18:05:05 -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 Thu, 9 Jun 2005 Volume: 10 Number: 8160
Today's topics:
Re: Answering Machine/callerID & perl email script <billb@buchnaland.net>
Re: Answering Machine/callerID & perl email script <1usa@llenroc.ude.invalid>
chown recursively <timodonovan@localhost.com>
Re: chown recursively <eighner@io.com>
Re: chown recursively <timodonovan@localhost.com>
Re: chown recursively <apeiron+usenet@coitusmentis.info>
Re: chown recursively <dont@mail.me>
Re: chown recursively <tim@vegeta.ath.cx>
Re: chown recursively <tim@vegeta.ath.cx>
Re: increase performance <joe@inwap.com>
Re: increase performance <someone@example.com>
Re: LWP::Useragent problem with https usenet@isbd.co.uk
Re: LWP::Useragent problem with https usenet@isbd.co.uk
Re: LWP::Useragent problem with https <mothra@nowhereatall.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: summarize bytes <joe@inwap.com>
Switches for configuring email sending <rbutcher.nospam@hotmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 09 Jun 2005 19:06:53 GMT
From: Mr Bill <billb@buchnaland.net>
Subject: Re: Answering Machine/callerID & perl email script
Message-Id: <hr0qe.10716$mZ3.8651@newssvr31.news.prodigy.com>
Brian Wakem wrote:
> Mr Bill wrote:
>
>> Brian Wakem wrote:
>>
>>> Mr Bill wrote:
>>>
>>>> Hello,
>>>> I'm running Linux MDK 10.1 and using the system as an answering machine
>>>> amongst other things. I don't even begin to understand perl scripting
>>>> so I
>>>> could use some assistance please. The machine is set up to answer
>>>> incoming
>>>> voice calls using vgetty. The voice message is then emailed to me in
>>>> .wav
>>>> format using the voice module on webmin. I'd like to be able to pass
>>>> the caller ID and caller name information as text to the email. The
>>>> logfile contains this information (at least I figured out how to
>>>> capture that
>>>> info). Revelent perl script (/usr/libexec/webmin/vgetty/email.pl) and
>>>> a
>>>> snip of the vgetty.ttySx logfile are below. I think this might also be
>>>> useful of others. Thanks.
>>>> Bill
>>>>
>>> <snip>
>>>
>>>
>>> I would rewrite email.pl to scan the log file and extract the data you
>>> need.
>>>
>>> Sending a wav by email is a bit cumbersome. I'd convert it to mp3
>>> first.
>>>
>>>
>> That would be very helpful...mp3 works too if that's more convenient.
>> Logfile location is /var/log/vgetty.ttyS0. I assume the extract of the
>> logfile would look for the last appropriate entry for name= and caller= ?
>> I greatly appreciate your willingness to assist. Thanks.
>>
>> Bill
>
>
> I'm not going to write it for you. If you need help with anything
> specific I may be able to oblige.
>
>
Teach a man to fish? LOL I'll give it a shot and let you know if I need
help sorting it out. I haven't touched any programming since PL/1,
Fortran, Cobol since college days. Don't imagine it'd be more than a half
dozen lines of code even for me. Google> perl script> tutorital here I
come. Thanks.
Bill
------------------------------
Date: Thu, 09 Jun 2005 20:14:00 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Answering Machine/callerID & perl email script
Message-Id: <Xns9670A4E36D6DAasu1cornelledu@127.0.0.1>
Mr Bill <billb@buchnaland.net> wrote in
news:hr0qe.10716$mZ3.8651@newssvr31.news.prodigy.com:
> Brian Wakem wrote:
>> I'm not going to write it for you. If you need help with anything
>> specific I may be able to oblige.
>>
>>
>
> Teach a man to fish? LOL I'll give it a shot and let you know if I
> need help sorting it out. I haven't touched any programming since
> PL/1, Fortran, Cobol since college days. Don't imagine it'd be more
> than a half dozen lines of code even for me. Google> perl script>
> tutorital here I come. Thanks.
You might benefit from reading the posting guidelines for this group.
They contain valuable information on how to help yourself and help
others help you.
See also:
<URL: http://learn.perl.org/>
<URL: http://theoryx5.uwinnipeg.ca/CPAN/perl/pod/perlfaq.html>
Sinan
--
A. Sinan Unur <1usa@llenroc.ude.invalid>
(reverse each component and remove .invalid for email address)
comp.lang.perl.misc guidelines on the WWW:
http://mail.augustmail.com/~tadmc/clpmisc/clpmisc_guidelines.html
------------------------------
Date: Thu, 9 Jun 2005 20:12:24 +0000 (UTC)
From: Tim O'Donovan <timodonovan@localhost.com>
Subject: chown recursively
Message-Id: <d8a7r8$6u$1@nwrdmz01.dmz.ncs.ea.ibs-infra.bt.com>
Quick newbie question! Could someone please point out how to use chown()
on directories recursively.
But mostly I'd like to know if there are actually any benefits over using:
system("chown -R $uid:$gid $dir");
Thanks very much!
Tim
------------------------------
Date: Thu, 09 Jun 2005 15:16:28 -0500
From: Lars Eighner <eighner@io.com>
Subject: Re: chown recursively
Message-Id: <slrndah8qk.mkt.eighner@goodwill.io.com>
In our last episode,
<d8a7r8$6u$1@nwrdmz01.dmz.ncs.ea.ibs-infra.bt.com>,
the lovely and talented Tim O'Donovan
broadcast on comp.lang.perl.misc:
> Quick newbie question! Could someone please point out how to use chown()
> on directories recursively.
> But mostly I'd like to know if there are actually any benefits over using:
> system("chown -R $uid:$gid $dir");
This is really a unix question, not a perl question. A word of
warning, though: beware of -R and .* -- it will recurse upward
because .. matches .* .
--
Lars Eighner eighner@io.com http://www.larseighner.com/
War on Terrorism: The Difference Between Us and Them
"We should invade their countries, kill their leaders and
convert them to Christianity." -- Ann Coulter
------------------------------
Date: Thu, 9 Jun 2005 20:27:06 +0000 (UTC)
From: Tim O'Donovan <timodonovan@localhost.com>
Subject: Re: chown recursively
Message-Id: <d8a8mq$212$1@nwrdmz02.dmz.ncs.ea.ibs-infra.bt.com>
Well my question was actually concerning whether using a Perl function
such as chown() had any benefits over using an equivalent system()
function to achieve the same the results.
Tim
Lars Eighner wrote:
> In our last episode,
> <d8a7r8$6u$1@nwrdmz01.dmz.ncs.ea.ibs-infra.bt.com>,
> the lovely and talented Tim O'Donovan
> broadcast on comp.lang.perl.misc:
>
>
>>Quick newbie question! Could someone please point out how to use chown()
>>on directories recursively.
>
>
>>But mostly I'd like to know if there are actually any benefits over using:
>
>
>>system("chown -R $uid:$gid $dir");
>
>
> This is really a unix question, not a perl question. A word of
> warning, though: beware of -R and .* -- it will recurse upward
> because .. matches .* .
>
------------------------------
Date: 09 Jun 2005 23:31:54 GMT
From: Christopher Nehren <apeiron+usenet@coitusmentis.info>
Subject: Re: chown recursively
Message-Id: <slrndahkba.18m.apeiron+usenet@prophecy.dyndns.org>
On 2005-06-09, Tim O'Donovan scribbled these
curious markings:
> Quick newbie question! Could someone please point out how to use chown()
> on directories recursively.
Perhaps a bit of File::Find?
> But mostly I'd like to know if there are actually any benefits over using:
>
> system("chown -R $uid:$gid $dir");
Who says chown exists on the target system? Who says it's in your path?
It's generally a bad idea to "shell out" to external programs when you
can do what you need to do with Perl.
Best Regards,
Christopher Nehren
--
I abhor a system designed for the "user", if that word is a coded
pejorative meaning "stupid and unsophisticated". -- Ken Thompson
If you ask the wrong people questions, you get "Joel on Software".
Unix is user friendly. However, it isn't idiot friendly.
------------------------------
Date: Fri, 10 Jun 2005 02:20:23 +0200
From: "Kjetil Skotheim" <dont@mail.me>
Subject: Re: chown recursively
Message-Id: <op.sr4oj9eq3z78ff@edelweiss.upc.no>
On Fri, 10 Jun 2005 01:31:54 +0200, Christopher Nehren
<apeiron+usenet@coitusmentis.info> wrote:
> On 2005-06-09, Tim O'Donovan scribbled these
> curious markings:
>> Quick newbie question! Could someone please point out how to use chown()
>> on directories recursively.
>
> Perhaps a bit of File::Find?
>
>> But mostly I'd like to know if there are actually any benefits over
>> using:
>>
>> system("chown -R $uid:$gid $dir");
>
> Who says chown exists on the target system? Who says it's in your path?
> It's generally a bad idea to "shell out" to external programs when you
> can do what you need to do with Perl.
I agree that GENERALLY this is a bad idea. But since chmod in itself
is very unix'ish, isn't it?, I think system should be permitted here.
...or if not permitted, I'd do a chmod to permit it...(uh)
>
> Best Regards,
> Christopher Nehren
--
Kjetil Skotheim
------------------------------
Date: Fri, 10 Jun 2005 00:21:36 GMT
From: Tim Hammerquist <tim@vegeta.ath.cx>
Subject: Re: chown recursively
Message-Id: <slrndahn7h.mt.tim@vegeta.saiyix>
Tim O'Donovan <timodonovan@localhost.com> wrote:
> Quick newbie question! Could someone please point out how to use
> chown() on directories recursively.
>
> But mostly I'd like to know if there are actually any benefits over
> using:
>
> system("chown -R $uid:$gid $dir");
The chown() perl function is a direct interface to the system call.
There is significantly less overhead using this method, as opposed to
the one you describe above, which calls the OS to start a separate shell
session, then having the shell session open a process for the chown(1)
utility, which then makes a call to the same system function perl's own
chown() calls.
As mentioned elsewhere, chown() may not be available on some platforms.
Also heed the superuser note under chown() in perlfunc.
HTH,
another Tim
--
...the word "hack" is used as a verb to indicate
a massive amount of nerd-like effort.
-- Harley Hahn, "A Student's Guide to Unix"
------------------------------
Date: Fri, 10 Jun 2005 00:27:20 GMT
From: Tim Hammerquist <tim@vegeta.ath.cx>
Subject: Re: chown recursively
Message-Id: <slrndahnia.mt.tim@vegeta.saiyix>
Lars Eighner <eighner@io.com> wrote:
> This is really a unix question, not a perl question. A word of
> warning, though: beware of -R and .* -- it will recurse upward because
> .. matches .* .
# chown -R 000 .*
What? I don't see anything wronD?-^\^N???~D?????Rv^U??>^LP
%?~D#^][tf^???G?^@^G~G~O^Y~OD?^]?մ?V,?~E?U^WS+?|%0y?=/x7?]v?^WE?|?~Gu`[?ΩK~
%GpoQZ e??C?S^C4?GN?~E[?^Cb?aR?~@?=?^UQn??~T?^V?~K^D???^DM~_'?o??~Y^_?^V^L1
%^B^Y^V??~[3m?~WN ¢~T-?^K?\z?oln^M?~E4?ud?R|R?'3h~Pz?ĺ??
????/Zd???R?'~A?j9?
CARRIER LOST
Tim Hammerquist
--
$ echo espresso > /dev/coffee
------------------------------
Date: Thu, 09 Jun 2005 12:06:10 -0700
From: Joe Smith <joe@inwap.com>
Subject: Re: increase performance
Message-Id: <mb-dnVBCkbuzDjXfRVn-qg@comcast.com>
John W. Krahn wrote:
> my $date = './date.txt';
Why did you write that instead of
my $date = 'date.txt';
?
-Joe
------------------------------
Date: Thu, 09 Jun 2005 20:03:44 GMT
From: "John W. Krahn" <someone@example.com>
Subject: Re: increase performance
Message-Id: <Ag1qe.43962$on1.40530@clgrps13>
Joe Smith wrote:
> John W. Krahn wrote:
>
>> my $date = './date.txt';
>
> Why did you write that instead of
> my $date = 'date.txt';
> ?
That is the way the OP wrote it and they both refer to the same file so I
didn't change it.
John
--
use Perl;
program
fulfillment
------------------------------
Date: 9 Jun 2005 19:20:06 GMT
From: usenet@isbd.co.uk
Subject: Re: LWP::Useragent problem with https
Message-Id: <3grj36Fdmb37U1@individual.net>
mothra <mothra@nowhereatall.com> wrote:
> usenet@isbd.co.uk wrote:
>
> > So is there anything else I have to do to get LWP::UserAgent to
> > support HTTPS or is it something wrong with the perl script I've
> > downloaded?
>
> perldoc LWPcook should give you what you need.
>
> Hope this helps
>
It would if I had LWPcook anywhere on my system, when I try the above
I get 'No documentation found for "LWPcook".'
I'll see if I can find it, thanks.
--
Chris Green
------------------------------
Date: 9 Jun 2005 19:24:52 GMT
From: usenet@isbd.co.uk
Subject: Re: LWP::Useragent problem with https
Message-Id: <3grjc4Fdmb37U2@individual.net>
mothra <mothra@nowhereatall.com> wrote:
> usenet@isbd.co.uk wrote:
>
> > So is there anything else I have to do to get LWP::UserAgent to
> > support HTTPS or is it something wrong with the perl script I've
> > downloaded?
>
> perldoc LWPcook should give you what you need.
>
> Hope this helps
>
Re: my previous Follow-up: LWPcook refers me to the README.SSL file
found in the libwww-perl distribution. When I started all this I
installed HTTP::Request which seemed to install a load of other stuff
including LWP::UserAgent. Is this part of libwww-perl or is that
something else that I also need?
--
Chris Green
------------------------------
Date: Thu, 9 Jun 2005 12:42:33 -0700
From: "mothra" <mothra@nowhereatall.com>
Subject: Re: LWP::Useragent problem with https
Message-Id: <42a89a22$1@usenet.ugs.com>
usenet@isbd.co.uk wrote:
> Re: my previous Follow-up: LWPcook refers me to the README.SSL file
> found in the libwww-perl distribution. When I started all this I
> installed HTTP::Request which seemed to install a load of other stuff
> including LWP::UserAgent. Is this part of libwww-perl or is that
> something else that I also need?
You need to install the libwww-perl distribution. If you are on a unix/linux
system you can use CPAN to install it.
perl -MCPAN -e shell
cpan> i /libwww/
Author LWWWP ("The libwww-perl mailing list" <libwww@perl.org>)
Distribution G/GA/GAAS/libwww-perl-5.10.tar.gz
Distribution G/GA/GAAS/libwww-perl-5.53.tar.gz
Distribution G/GA/GAAS/libwww-perl-5.77.tar.gz
Distribution G/GA/GAAS/libwww-perl-5.803.tar.gz
Then
cpan> install G/GA/GAAS/libwww-perl-5.803.tar.gz
should work
Hope this helps
Mothra
------------------------------
Date: 09 Jun 2005 23:23:59 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <42a8cf8e$0$14572$8b463f8a@news.nationwide.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.5 $)
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://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
"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 <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Thu, 09 Jun 2005 12:12:00 -0700
From: Joe Smith <joe@inwap.com>
Subject: Re: summarize bytes
Message-Id: <ddGdnVsZe-YTCTXfRVn-3Q@comcast.com>
bastardx wrote:
> works great
> this exacly what i want
> how to read this data from file?
There are some things that you have to learn on your own.
------------------------------
Date: Fri, 10 Jun 2005 00:29:43 GMT
From: "Robert" <rbutcher.nospam@hotmail.com>
Subject: Switches for configuring email sending
Message-Id: <X95qe.1624272$Xk.96082@pd7tw3no>
Hi,
While this is only a semi perl question, I hope someone here can help me
configure my sendmail parameter. (no responses from sendmail newsgroup) I
have a simple form that gets passes to sendmail for sending. Due to spammers
hijacking sendmail scripts, I no longer pass the recipient from the form,
rather I want to hardwire the recipient into the script. But I cannot find
and documentation out there on sendmail switches ... ie ... -t -i etc etc
and what each does (and other switches I dont know about). I just want my
script to send the email to a hardwired recipient within the script.
$mailprog = "/usr/sbin/sendmail -t";
I think the above means get recipient from the form fields.
$mailprog = "/usr/sbin/sendmail -i";
Not sure what the above does.
I thought I read somewhere a while back that to hardwire the recipient you
did something like below.
$mailprog = "/usr/sbin/sendmail user\@email.com";
No switches or anything ... anyways if someone know where I might find
complete documentation for sendmail in a CGI envoronment, that would be much
appriciated.
Robert
------------------------------
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 V10 Issue 8160
***************************************
