[6967] in Perl-Users-Digest
Perl-Users Digest, Issue: 593 Volume: 8
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Mon Jun 9 20:17:27 1997
Date: Mon, 9 Jun 97 17:01:33 -0700
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, 9 Jun 1997 Volume: 8 Number: 593
Today's topics:
RFD: comp.lang.perl reorganization (A. Deckers)
Running CGI in the background (Angel Leyva)
Re: Running CGI in the background <sibsib@hotmail.com>
Sample Simple Server from Camel book (Sigi)
Suppressing Echo to STDOUT? (Ben Neil Gerdemann)
WEBDNS script barfing on .00307 (Dean Carpenter (AREYES))
Re: What does "UNIX" stand for.. (Robert Munck)
Re: why won't 'print <<end_print...end_print' work? <bryan@eai.com>
Digest Administrivia (Last modified: 8 Mar 97) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 09 Jun 1997 23:21:25 GMT
From: deckers@man.ac.uk (A. Deckers)
Subject: RFD: comp.lang.perl reorganization
Message-Id: <865898485.4144@isc.org>
REQUEST FOR DISCUSSION (RFD)
moderated group comp.lang.perl.data-structure
moderated group comp.lang.perl.inter-process
moderated group comp.lang.perl.programmer
moderated group comp.lang.perl.regex
This is a formal Request for Discussion (RFD) for the creation of
world-wide moderated Usenet newsgroups in the comp.lang.perl
hierarchy. This is not a call for votes; you cannot vote at this
time. Procedural details are below.
Newsgroups lines:
comp.lang.perl.data-structure Using Perl data structures. (Moderated)
comp.lang.perl.inter-process Inter-process communications in Perl. (Moderated)
comp.lang.perl.programmer General non-FAQ Perl programming issues. (Moderated)
comp.lang.perl.regex Using Perl regular expressions. (Moderated)
RATIONALE: all groups
Most Perl-related issues are currently discussed in
comp.lang.perl.misc (clpm). The statistics compiled by one of the
proponents indicate that this group regularly receives more than
one thousand articles from approximately 500 posters each week, a
volume of traffic many readers find overwhelming.
In addition, a significant fraction of the traffic on clpm
consists of off-topic articles, many of them widely cross-posted
through the comp.* hierarchy and ammounting to little more than
flame-wars, articles asking questions that are answered in the
FAQs, and above all, a regular flow of articles asking questions
related to the Common Gateway Interface (CGI) but unrelated to
Perl.
In these circumstances, a number of regular posters to the group
have stopped reading clpm, while new readers can find it
difficult to find relevant posts. Both facts result in a reduced
usefullness of the existing clpm newsgroup.
These comp.lang.perl groups are therefore proposed as high
signal-to-noise moderated newsgroups where readers are not
subjected to the types of articles described above. The intention
is both to provide a usefull resource for inexperienced Perl
programmers, and to attract and retain experienced programmers
who can make a substantial contribution to the group.
In the light of experience in clpm, moderation is considered
essential to ensure a sufficiently high signal-to-noise ratio
that will guarantee the usefullness of the proposed groups.
The thematic split is proposed in order to provide more
specialised groups where readers (and posters) can follow topics
in which they have a special interest without necessarily having
to see articles related to other aspects of Perl.
CHARTER: all groups
The group shall be moderated using a Perl script, which shall be
overseen by a moderation panel. The moderation panel may at its
discretion implement any technical solutions it considers
necessary to enforce the provisions of this charter.
The moderation script will escrow submissions from first-time
posters, who will be sent registration instructions in addition
to the group charter and pointers to relevant references.
Submitions from registered users will be auto-approved provided
their posts comply with all the criteria set out in this charter.
By submitting a registration, users implicitly accept to abide by
the provisions of this charter. Any poster who has 5 consecutive
posts rejected by the moderation script will be removed from the
pre-approval list.
In addition, the moderation script shall be configured to reject
any article:
+ which is cross-posted, save for the blanket cross-posting
provisions described below;
+ which is deemed to contain a binary file. In so far as it is
practicable, the moderation script shall be configured so as to
pass PGP signatures and similar authentication schemes, while
rejecting articles containing binary files;
+ which is deemed to be encoded primarily using a markup scheme,
with the exception of Plain Old Documentation (POD). In so far
as it is practicable, the moderation script shall be configured
so as to pass articles containing short fragments of markup
embedded within them;
+ which is deemed to be encoded in any MIME type considered
inappropriate by the moderation panel. Initially, only articles
of text/plain MIME type will be accepted by the moderation
script;
+ which is deemed to contain more quoted than unquoted text.
This condition will not be applied to articles containing fewer
than 40 lines of body text, excluding the signature if one is
found. Articles without any unquoted text, not taking into
account the signature if one is present, will be rejected;
+ which is deemed to be a duplicate of a previously submitted
article;
+ which has a subject header starting with the string 'Re: ' but
doesn't contain a references header;
+ which contains a signature over 6 lines in length.
In the context of this charter, a signature is defined as
everything found after the last cut line, ie /^-- $/, found in
the article. Posters are requested to make use of such cut lines
to delimit their signature from the article body.
Any article whose primary purpose is the advertisement of a
commercial property, good or service, including job offers and
demands, MLMs and MMFs, shall be off-topic and therefore
forbidden in the group. The moderation panel may at its
discretion implement appropriate technical solutions to ensure
such articles are not published in the group.
Posters are requested to use informative subject lines, to be
concise and to the point, and to include in their posts any
relevant diagnostic information and code. The moderation panel
may at its discretion implement technical measures to enforce all
or part of this provision.
Posters are requested not to post answers to questions which are
explicitly addressed in the documentation, including the relevant
FAQs. A pointer to the relevant resource should instead be
emailed to the questionner.
Any article rejected by the moderation script will be returned to
its author together with a copy of the charter of the relevant
group and a brief note explaining the reason for the rejection.
No attempt will be made to verify the validity of the poster's
email address, and bounces will be discarded.
The moderators of comp.lang.perl.announce, comp.answers and
news.announce.newgroups, and any succesor groups thereto, are
hereby granted blanket permission to cross-post to the proposed
groups at their discretion.
While permission to routinely cross-post to the group will not be
granted in other cases, the moderation panel will consider
requests on a case-by-case basis, and grant their approval if
they deem that this would be of significant benefit to the
readership of the group. This provision applies especially, but
is not limited to, relevant FAQs.
Sites wishing to receive posts approved by the moderation script
via email, shall apply to the moderation panel, which shall
maintain a mailing list for this purpose. This provision is
primarily intended to help poorly connected sites to reduce
propagation delay for the proposed groups.
The moderation panel will consist of no fewer than 5 and no more
than 10 members. In the case of a temporary absence by a member
of the moderation panel, he or she shall nominate a replacement
for the duration of said absence. New members may be appointed
upon the permanent departure of an existing member, or as the
moderation panel deems appropriate.
With the exception noted in the next paragraph, the moderation
panel shall take all its decisions on the basis of a simple
majority vote among its current members, and formulate and
publish additional terms of reference, including rules of
procedure, in accordance with the provisions of this charter, at
its earliest convenience.
The moderation panel may depose one of its members if a motion to
this effect is approved by a majority of 2/3 of existing members.
All members of the moderation panel shall be authorised to cancel
any article which has not been approved by an authorised
moderation site.
Any article submitted by a member of the moderation panel outside
the exercise of his or her administrative role will be subject to
the full moderation procedure described herein.
END CHARTER.
CHARTER: comp.lang.perl.data-structure
The group comp.lang.perl.data-structure will deal with issues
related to Perl's data-structures as described in the perldata,
perldsc, perllol, perlobj and related manual pages included in
the Perl distribution.
Any article which doesn't address issues related to Perl's data
structures will be off-topic in this group, and the moderation
panel may at its discretion implement appropriate technical
solutions to ensure they are not published in the group.
END CHARTER.
MODERATOR INFO: comp.lang.perl.data-structure
Moderator: Russ Allbery <rra@stanford.edu>
Moderator: Greg Bacon <gbacon@cs.uah.edu>
Moderator: Tom Christiansen <tchrist@jhereg.perl.com>
Moderator: Alain Deckers <deckers@man.ac.uk>
Moderator: Andrew M. Langmead <aml@world.std.com>
Moderator: Tad McClellan <tadmc@flash.net>
Moderator: Chris Nandor <pudge@pobox.com>
Submission address: clp-data@perl.com
Administrative address: clp-data-request@perl.com
END MODERATOR INFO.
CHARTER: comp.lang.perl.inter-process
The group comp.lang.perl.inter-process will deal with issues
related to the implementation of interprocess communications
(signals, fifos, pipes, safe subprocesses, sockets, semaphores
and related issues) in Perl.
Any article which doesn't address issues related to the
implementation of inter-process communication in Perl structures
will be off-topic in this group, and the moderation panel may at
it discretion take appropriate measures to ensure that such
articles are not published in the group.
END CHARTER.
MODERATOR INFO: comp.lang.perl.inter-process
Moderator: Russ Allbery <rra@stanford.edu>
Moderator: Greg Bacon <gbacon@cs.uah.edu>
Moderator: Tom Christiansen <tchrist@jhereg.perl.com>
Moderator: Alain Deckers <deckers@man.ac.uk>
Moderator: Andrew M. Langmead <aml@world.std.com>
Moderator: Tad McClellan <tadmc@flash.net>
Moderator: Chris Nandor <pudge@pobox.com>
Submission address: clp-interprocess@perl.com
Administrative address: clp-interprocess-request@perl.com
END MODERATOR INFO.
CHARTER: comp.lang.perl.programmer
The group comp.lang.perl.programmer will deal with all general
Perl-related issues that are not explicitly addressed in Perl's
documentation, where documentation is defined as anything which
is found in the <URL:http://www.perl.com/CPAN/doc/> directory,
and which exceed the scope or doesn't match the subject matter of
other comp.lang.perl groups.
Any article which doesn't satisfy the preceding criteria will be
off-topic in this group, and the moderation panel may at its
discretion adopt technical measures to ensure that they are not
published in comp.lang.perl.programmer.
END CHARTER.
MODERATOR INFO: comp.lang.perl.programmer
Moderator: Russ Allbery <rra@stanford.edu>
Moderator: Greg Bacon <gbacon@cs.uah.edu>
Moderator: Tom Christiansen <tchrist@jhereg.perl.com>
Moderator: Alain Deckers <deckers@man.ac.uk>
Moderator: Andrew M. Langmead <aml@world.std.com>
Moderator: Tad McClellan <tadmc@flash.net>
Moderator: Chris Nandor <pudge@pobox.com>
Submission address: clp-programmer@perl.com
Administrative address: clp-programmer-request@perl.com
END MODERATOR INFO.
CHARTER: comp.lang.perl.regex
The group comp.lang.perl.regex will deal with issues related to
Perl's regular expressions as described in the perlre manual page
and related documents.
Any article which doesn't address issues related to Perl's
regular expression will be off-topic in this group, and the
moderation panel may adopt appropriate technical solutions to
ensure that such articles are not posted in the group.
END CHARTER.
MODERATOR INFO: comp.lang.perl.regex
Moderator: Russ Allbery <rra@stanford.edu>
Moderator: Greg Bacon <gbacon@cs.uah.edu>
Moderator: Tom Christiansen <tchrist@jhereg.perl.com>
Moderator: Alain Deckers <deckers@man.ac.uk>
Moderator: Andrew M. Langmead <aml@world.std.com>
Moderator: Tad McClellan <tadmc@flash.net>
Moderator: Chris Nandor <pudge@pobox.com>
Submission address: clp-regex@perl.com
Administrative address: clp-regex-request@perl.com
END MODERATOR INFO.
PROCEDURE:
This is a request for discussion, not a call for votes. In this
phase of the process, any potential problems with the proposed
newsgroups should be raised and resolved. The discussion period
will continue for a minimum of 21 days (starting from when the
first RFD for this proposal is posted to
news.announce.newgroups), after which a Call For Votes (CFV) may
be posted by a neutral vote taker if the discussion warrants it.
Please do not attempt to vote until this happens.
All discussion of this proposal should be posted to news.groups.
This RFD attempts to comply fully with the Usenet newsgroup
creation guidelines outlined in "How to Create a New Usenet
Newsgroup" and "How to Format and Submit a New Group Proposal".
Please refer to these documents (available in
news.announce.newgroups) if you have any questions about the
process.
DISTRIBUTION:
This RFD has been posted to the following groups:
news.announce.newgroups
news.groups
comp.lang.perl.misc
comp.lang.perl.modules
comp.lang.perl.tk
Proponent: Russ Allbery <rra@stanford.edu>
Proponent: Greg Bacon <gbacon@cs.uah.edu>
Proponent: Tom Christiansen <tchrist@jhereg.perl.com>
Proponent: Alain Deckers <deckers@man.ac.uk>
Proponent: Andrew M. Langmead <aml@world.std.com>
Proponent: Tad McClellan <tadmc@flash.net>
Proponent: Chris Nandor <pudge@pobox.com>
--
Alain Deckers <deckers@man.ac.uk>
------------------------------
Date: Mon, 09 Jun 1997 16:09:10 -0400
From: angel_leyva@prenhall.com (Angel Leyva)
Subject: Running CGI in the background
Message-Id: <339c618a.20896096@news.prenhall.com>
I have a perl script that takes about 10 minutes to complete. It is
actually about 25 different commands which are run at the operating
system level using the back tic '`'.
What I wanted to do, was provide some blurb to the user on there browser
as I finished with each section of the script. What seems to be
happening is that the process is taking so long to respond, that the
browser times out, and a No Data message comes up on the browser.
Any suggestions?
Angel
---
Angel Leyva
(http://www.leyvagroup.com/airborne)
(aleyva@leyvagroup.com )
(airborne@leyvagroup.com )
------------------------------
Date: Mon, 09 Jun 1997 18:49:49 -0400
From: Scott Blanksteen <sibsib@hotmail.com>
Subject: Re: Running CGI in the background
Message-Id: <339C888D.C27D41AE@hotmail.com>
Angel Leyva wrote:
> I have a perl script that takes about 10 minutes to complete. It is
> actually about 25 different commands which are run at the operating
> system level using the back tic '`'.
>
> What I wanted to do, was provide some blurb to the user on there browser
> as I finished with each section of the script. What seems to be
> happening is that the process is taking so long to respond, that the
> browser times out, and a No Data message comes up on the browser.
>
> Any suggestions?
Write shorter scripts :-)
Or, more constructively, use the 'sleep' function
to write a '.' to the browser every few seconds.
Scott
--
Scott I. Blanksteen
sib (at) worldnet (dot) att (dot) net
------------------------------
Date: Mon, 09 Jun 1997 20:08:40 GMT
From: sigi@remsmurr.de (Sigi)
Subject: Sample Simple Server from Camel book
Message-Id: <339c611b.255977468@news.seicom.net>
Hi greats.
I want:
When I'm login in at my login computer I want to start a perl job on
another computer.
The job:
I searched in the camel book and found the Sample Simple Server +
Client. So I took them. My login program starts the client. It's ok.
The Server recieve's the info from the client. It's ok. Now I changed
the origin line to print out the message in a line like
>>>system("/.../program.pl $_");<<< to start a job ( a perl program).
The gag:
All is working. I found in the prozess status the working program with
ending line ".... (perl 5...)". Ok I thought. But when the program is
ending, the prozess status line is allways there with "(perl 5...)".
This works for a few times adding new "(perl 5...)" lines then the
server hangs.
The end:
I hope you can help me to jump out of this problem. I didn't found
something which is starting this or doesn't ending something. Could
you help me please.
Excuse my bad english. Sigi. sigi@remsmurr.de
------------------------------
Date: 9 Jun 1997 23:43:29 GMT
From: gerdemb@rice.edu (Ben Neil Gerdemann)
Subject: Suppressing Echo to STDOUT?
Message-Id: <5ni4f1$eiu$1@joe.rice.edu>
Hello,
I would like to use Perl to input data from the keyboard without echoing
it to the screen (like the way passwd works.) How is this possible?
Thanks,
Ben
------------------------------
Date: 9 Jun 97 15:21:23 GMT
From: deano@netaxis.com (Dean Carpenter (AREYES))
Subject: WEBDNS script barfing on .00307
Message-Id: <339c1f73.0@news.netaxis.com>
Is anyone familiar with the neat webdns script ? from MIT.
I just put it on a Debian 1.3 Linux box with perl 5.00307
and it's having a problem on a funtion call. Specifically
on line 211 :
sub load_rr {
local($domain,$origin,@_) = @_;
local($i);
dies with the error :
Bizarre copy of ARRAY in aassign at /usr/lib/cgi-bin/webdns line 211, chunk 11.
I don't know enough of perl to know just what's killing it.
By the way, the aasign is what it produces, that's not a typo.
TIA
--
Dean Carpenter deano is at areyes.com
------------------------------
Date: Mon, 09 Jun 1997 21:58:59 GMT
From: munck@mindspring.com (Robert Munck)
Subject: Re: What does "UNIX" stand for..
Message-Id: <339c789b.35848461@news.mindspring.com>
On 5 Jun 1997 17:41:38 GMT, dgy@rtd.com (Don Yuniskis) wrote:
>In article <01bc71a4$dca66980$49818e9f@gsa.gov>,
>I've never understood the bias *against* MULTICS as I thought it was
>*decades* ahead of it's time!
The bias against MULTICS was entirely within IBM, who saw it as a
major competitor and a reminder that they were unable to produce
a usable time-sharing system. Big Blue's reaction was to create a
planet-sized kludge called TSS. I once taught a semester course
comparing the internal architectures of TSS and MULTICS.
(at Brown in 1969)
> I suspect the delays in getting it
>up and running were the inspiration for UNICS's genesis.
Nah, MULTICS was running wonderfully well years before
UNIX was ever thought of. It ran on a mainframe (GE 635)
that cost about $20 million in today's dollars. UNIX was
created to provide similar, though greatly reduced, facilities
on a machine in the $100K range. Like MSDOS a decade
later, it was a huge setback in the development of operating
systems. C took a similar position in HOLs.
PR1ME Computer did a knock-off informally called "MULTICS
In A Matchbox" in the early 80's. Unfortunately, they let the
h/w people control the company, and it went right into the
dumpster. Btw, MULTICS was one of the first major OSs
written in a HOL, PL/I. IBM didn't make the shift to BSL for
many years.
Bob Munck
Haymarket, VA
MULTICS -- a tremendous improvement on all of its successors.
------------------------------
Date: Mon, 09 Jun 1997 17:24:37 -0500
From: Bryan Hart <bryan@eai.com>
Subject: Re: why won't 'print <<end_print...end_print' work?
Message-Id: <339C82A5.15FB@eai.com>
Chris Hilton wrote:
>
> Will Sexton wrote:
> >
> > If I do the following:
> >
> > print <<"end_print";
> > some text
> > some text on the next line
> > end_print
> >
> > my (multiple) sources tell me the program should print the text, without
> > having to set the print command for each new line (said sources lacking
> > further explanation). But when I try it, I get an error message ("Can't
> > find string terminator "end_print" anywhere before EOF at <progname>
> > line <line number>.") And can't find feature documented among usual
> > suspects (camel, llama, etc.).
> >
> > Why won't it work?
> > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> > Will Sexton wise2@mindspring.com
> > UNC-CH/Info Sci sextw@ils.unc.edu
>
> p.43, 2nd Edition Camel book.
>
> Be sure that 'end_print' has no surrounding white space (like the tab
> you used above). It must appear by itself on the line.
>
> --
>
> Chris
> Be seeing you.
Also, I don't think that you should double-quote the terminator string
either...
Bryan
--
-------------------------------
| Bryan Hart
| Network Products Engineer
| Engineering Animation Inc.
| Phone: (515) 296-5979
| Fax: (515) 296-7025
| Email: bryan@eai.com
| Web: http://www.eai.com/
-------------------------------
"A conclusion is simply the place where you got tired of thinking"
------------------------------
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 593
*************************************
