[6548] in Perl-Users-Digest
Perl-Users Digest, Issue: 173 Volume: 8
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Mar 25 02:07:35 1997
Date: Mon, 24 Mar 97 23:00:17 -0800
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Mon, 24 Mar 1997 Volume: 8 Number: 173
Today's topics:
Cancelled: Randal Schwartz interview (Steve Wainstead)
Perl process doesn't go away (Larry Alexander)
Re: Perl training in Australia? (Ian Chambers)
sendmail and perl question (Robert Hutchinson)
Re: Unix and ease of use (WAS: Who makes more ...) <pgf@stiletto.acadian.net>
Re: What's a bad Perl book? <tchrist@mox.perl.com>
Re: What's a good Perl book? <merlyn@stonehenge.com>
Digest Administrivia (Last modified: 8 Mar 97) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: 24 Mar 1997 21:39:27 GMT
From: swain@boojie.rt.csuohio.edu (Steve Wainstead)
Subject: Cancelled: Randal Schwartz interview
Message-Id: <5h6saf$1ds@csu-b.csuohio.edu>
Do to unforseen circumstances the interview has been cancelled. My
apologies to everyone involved.
--
---
The radio show 31337 -- http://wcsb.org/31337/
finger swain@wcsb.org for PGP key
When encryption is outlawed, ?o'AZ-,++o+i++##4AoA+-/-C++bI+/.+~
------------------------------
Date: 25 Mar 1997 05:22:39 GMT
From: lalex@apnet.com (Larry Alexander)
Subject: Perl process doesn't go away
Message-Id: <859267279.50147@optional.cts.com>
I have been running a script (an HTML registration script where users type
in their name, email address and interests) since December 1996 with no
problem. For the past week, however, I have been noticing a process that
is eating up CPU time. This script, called guestap.pl appears in the ps
listing as "guestap." without the "pl" extension with many minutes of time
against it. I have to manually go in and kill this process.
I've checked the server logs and nothing strange there. This obviously
doesn't happen every time the script is run... only sometimes. (ouch!)
Any clues as to where I can look? perl debug says all is OK.
Any and all suggestions are greatly appreciated.
Thanx!
Larry Alexander
lalex@apnet.com
------------------------------
Date: 25 Mar 1997 05:10:05 GMT
From: ichambrs@nortel.ca (Ian Chambers)
Subject: Re: Perl training in Australia?
Message-Id: <5h7mnd$7ku@bcarh8ab.bnr.ca>
What aspect of perl are you interested in? Where are you located in Australia,
if Sydney then I may be able to help (don't let the e-mail address mislead you).
Ian Chambers - Majik Teachings Computer Consultancy
------------------------------
Date: Wed, 26 Mar 1997 06:26:09 +1200
From: robh@spatial.co.nz (Robert Hutchinson)
Subject: sendmail and perl question
Message-Id: <robh-ya02408000R2603970626090001@news.voyager.co.nz>
Hi,
If I have a text file that contains mail headers will this bit of code send it
to the address I want it to go to?
system("$sendmail $mailto < $output");
where $sendmail = absolute path to sendmail
where $mailto = email address
where $output = absolute path to text file
After sending the message will the program return to the perl script so it can
delete the text file?
unlink($output)
I've only just started learning perl so any pointers to potential problems
would be appreciated. I haven't tested this yet because my server is being
rebuilt.
Thanks
Robert
------------------------------
Date: Mon, 24 Mar 1997 23:00:31 -0600
From: Phil Fraering <pgf@stiletto.acadian.net>
To: brumley@asl.dl.nec.com
Subject: Re: Unix and ease of use (WAS: Who makes more ...)
Message-Id: <Pine.SOL.3.95.970324225300.21723A-100000@stiletto.acadian.net>
On 24 Mar 1997, Randy Wright wrote:
> The figures are soft, but there are those claiming that Linux
> is now the number 3 OS with an installed base of about 6 million.
I'd like to see some sort of proof.
Although I don't think the numbers aren't that important. What I
think Microsoft should be concerned about is the segment of the "market"
that has been drawn into Linux: the fiddlers, fence-menders, and
car-mechanics, so to speak, of modern computing.
> But traditional economics and marketing and management thinking
> will not, as far as I know, be able to digest such an idea.
> It is not at all some socialist or communist thing, as some
> people around usenet have proposed.. It is NOT characterized
> by central planning, or authoritarian production.. That is
> much more like the model of Microsoft. Linux is not controlled.
> It cannot be made unprofitable. It is built BY its market and
> it becomes whatever that market wants it to be as the market
> decides what it wants.
Extending this analogy, supposing software were a commodity; Linux isn't a
commodity, but a commodity exchange.
It's not a company but a stock exchange.
I think there are lessons as to why Linux succeeded and GNU failed
(although the GNU people are trying to claim Linux as their success
because it uses GPL'd code, and they promote the GPL concept, and Linux
uses a lot of GNU code) is that Linux was and is anarchic in development,
while the HURD remained the closed domain of the official "Project Hurd."
I guess one of the lessons is that free software shouldn't be managed like
commercial software.
Phil
Phil Fraering "This tiger is sprawled so still and so flat,
pgf@acadian.net A question arises when glancing thereat.
Standard disclaimer, Is he asleep? To be perfectly frank,
Standard excuses. He looks more as if he was creamed by a tank!"
- Bill Watterson
------------------------------
Date: 25 Mar 1997 04:22:09 GMT
From: Tom Christiansen <tchrist@mox.perl.com>
Subject: Re: What's a bad Perl book?
Message-Id: <5h7jth$hqp$1@csnews.cs.colorado.edu>
Keywords: Hexapodia as the key insight
[courtesy cc of this posting sent to cited author via email]
In comp.lang.perl.misc,
revjack@radix.net writes:
:Sorry, all those other threads were getting to me.
Well, I find "Java in a Nutshell" to be a very bad Perl book. :-)
--tom
--
Tom Christiansen tchrist@jhereg.perl.com
pos += screamnext[pos] /* does this goof up anywhere? */
--Larry Wall, from util.c in the v5.0 perl distribution
------------------------------
Date: 24 Mar 1997 22:32:33 -0700
From: Randal Schwartz <merlyn@stonehenge.com>
To: doom@kzsu.Stanford.EDU (Joe Brenner)
Subject: Re: What's a good Perl book?
Message-Id: <8ck9mwbkpa.fsf@gadget.cscaper.com>
>>>>> "Joe" == Joe Brenner <doom@kzsu.Stanford.EDU> writes:
Joe> If you're interested, my reaction to the first chapter was
Joe> something like "Gee, this example he's working with is so
Joe> artificial. Wouldn't it be better if he could show how to
Joe> write something in Perl that's actually useful?"
OK. Here's the assignment that I was given. See if you can do better...
Task: write a series of examples that:
* introduce only one or two things from each chapter,
* don't introduce anything not actually covered in the book,
* build on each previous example,
* are under 30 lines or so maximum even when you get done,
* involve something you can actually type in and run at each stage,
* involve some interactivity so they're sexy and sizzle,
* don't involve the web or anything that doesn't come in the distribution,
* can be read in about 30-60 minutes even with explanation,
* don't make perl look more complex than it is,
* and are clear of copyright.
Go. You have 48 hours. (That's about how long I had between
committing to the demo run and actually starting to work implementing
it. I did most of the best thinking in the shower that next morning.)
I think after you look at the constraints, you'll see why it's a bit
artificial. The *requirements* are artificial. This is a "demo run",
walking you through the very top level of the language as it is being
introduced. No *practical* program would meet half of those
requirements, let alone all of them. It's like building a car engine
from leftover parts. It's a bit tricky, and the result is a bit, uh,
McGuyver-ish. :-)
print "Just another Perl hacker," # but not what the media calls "hacker!" :-)
## legal fund: $20,495.69 collected, $182,159.85 spent; just 525 more days
## before I go to *prison* for 90 days; email fund@stonehenge.com for details
--
Name: Randal L. Schwartz / Stonehenge Consulting Services (503)777-0095
Keywords: Perl training, UNIX[tm] consulting, video production, skiing, flying
Email: <merlyn@stonehenge.com> Snail: (Call) PGP-Key: (finger merlyn@ora.com)
Web: <A HREF="http://www.stonehenge.com/merlyn/">My Home Page!</A>
Quote: "I'm telling you, if I could have five lines in my .sig, I would!" -- me
------------------------------
Date: 8 Mar 97 21:33:47 GMT (Last modified)
From: Perl-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 8 Mar 97)
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.misc (and this Digest), send your
article to perl-users@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.
The Meta-FAQ, an article containing information about the FAQ, is
available by requesting "send perl-users meta-faq". The real FAQ, as it
appeared last in the newsgroup, can be retrieved with the request "send
perl-users FAQ". Due to their sizes, neither the Meta-FAQ nor the FAQ
are included in the digest.
The "mini-FAQ", which is an updated version of the Meta-FAQ, is
available by requesting "send perl-users mini-faq". It appears twice
weekly in the group, but is not distributed in the digest.
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 V8 Issue 173
*************************************
