[25430] in Perl-Users-Digest
Perl-Users Digest, Issue: 7675 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Wed Jan 19 21:05:25 2005
Date: Wed, 19 Jan 2005 18:05:13 -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 Wed, 19 Jan 2005 Volume: 10 Number: 7675
Today's topics:
checking existance of a directory <lastname_nospam@heritage.nv.gov>
Re: checking existance of a directory <noreply@gunnar.cc>
Re: checking existance of a directory <perl@lennychallis.co.uk>
Re: checking existance of a directory <terrylr@blauedonau.com>
Re: checking existance of a directory <jl_post@hotmail.com>
Re: checking existance of a directory <1usa@llenroc.ude.invalid>
Re: checking existance of a directory <perl@lennychallis.co.uk>
Re: Help Perlling a program <someone@example.com>
Re: IPC looking for simple/best way to communicate whansen_at_corporate-image_dot_com@us.com
Re: Kalender programm <lv@aol.com>
Re: Low level data manipulation in Perl <a.newmane.remove@eastcoastcz.com>
Re: Low level data manipulation in Perl <perl@lennychallis.co.uk>
Re: telnet timed out <lv@aol.com>
Re: The array ARGV <1usa@llenroc.ude.invalid>
Re: The world's shortest 'Hello World!' program: a prop <tadmc@augustmail.com>
Re: The world's shortest 'Hello World!' program: a prop <perl@lennychallis.co.uk>
Whats the variable holding the dir seperator? ipellew@pipemedia.co.uk
Re: Whats the variable holding the dir seperator? (Jay Tilton)
Re: Whats the variable holding the dir seperator? <gargoyle@no.spam>
Re: Whats the variable holding the dir seperator? <perl@lennychallis.co.uk>
Re: Whats the variable holding the dir seperator? <No_4@dsl.pipex.com>
Re: Whats the variable holding the dir seperator? <perl@lennychallis.co.uk>
Re: Whats the variable holding the dir seperator? <1usa@llenroc.ude.invalid>
Re: Whats the variable holding the dir seperator? <1usa@llenroc.ude.invalid>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Thu, 20 Jan 2005 00:06:05 GMT
From: "Eric Peterson" <lastname_nospam@heritage.nv.gov>
Subject: checking existance of a directory
Message-Id: <NBCHd.8307$1c.4138@newssvr31.news.prodigy.com>
I'm looking for the equivalent of
if (-e "filename") { }
for checking existance specifically of a directory
Thanks,
-Eric
------------------------------
Date: Thu, 20 Jan 2005 01:39:06 +0100
From: Gunnar Hjalmarsson <noreply@gunnar.cc>
Subject: Re: checking existance of a directory
Message-Id: <358cssF4fg5o5U1@individual.net>
Eric Peterson wrote:
> I'm looking for the equivalent of
> if (-e "filename") { }
> for checking existance specifically of a directory
perldoc -f -X
--
Gunnar Hjalmarsson
Email: http://www.gunnar.cc/cgi-bin/contact.pl
------------------------------
Date: Thu, 20 Jan 2005 01:06:41 -0000
From: "Leonard Challis" <perl@lennychallis.co.uk>
Subject: Re: checking existance of a directory
Message-Id: <csn078$c7i$1@news7.svr.pol.co.uk>
> I'm looking for the equivalent of
> if (-e "filename") { }
> for checking existance specifically of a directory
First:
http://www.google.co.uk/search?hl=en&q=check+a+directory+exists+perl&meta=
-e is a so called -X flag. On google there are pleny of links to
comprehensive lists of these.
To check if a file is a directory, use the -d flag. e.g:
Plenty of examples are on the first Google result here:
http://www.developer.be/forums/index.cfm/fuseaction/dsp_full_thread/fullthreadid/355/forumID/5.htm
Personally, something like
| mkdir("c:\temp", 0777) unless (-d "c:\temp");
looks quite nice to me :D
Lenny
------------------------------
Date: Wed, 19 Jan 2005 18:17:06 -0600
From: "terry l. ridder" <terrylr@blauedonau.com>
Subject: Re: checking existance of a directory
Message-Id: <Pine.LNX.4.61.0501191815590.23579@johann.blauedonau.com>
hello;
On Thu, 20 Jan 2005, Eric Peterson wrote:
> I'm looking for the equivalent of
> if (-e "filename") { }
> for checking existance specifically of a directory
>
man perlfunc
-d File is a directory.
> Thanks,
> -Eric
>
>
>
--
terry l. ridder ><>
------------------------------
Date: 19 Jan 2005 17:11:38 -0800
From: "jl_post@hotmail.com" <jl_post@hotmail.com>
Subject: Re: checking existance of a directory
Message-Id: <1106183498.856323.282600@f14g2000cwb.googlegroups.com>
Eric Peterson wrote:
>
> I'm looking for the equivalent of
> if (-e "filename") { }
> for checking existance specifically of a directory
Use the "-d" call, like this:
if (-d "directory") { }
(Note that "-e" only checks to see is "filename" exists, but it does
not verify that if "filename" is an actual name of a file (it could be
the name of a directory).)
To check for the existance of a file, use "-f", like this:
if (-f "filename") { }
There are a lot more call like "-e", "-f", and "-d" that you should
probably know about. You can read about them by typing
"perldoc -f -e" at the command line.
I hope this helps, Eric.
-- Jean-Luc
------------------------------
Date: 20 Jan 2005 01:45:46 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: checking existance of a directory
Message-Id: <Xns95E3D33BE29EBasu1cornelledu@132.236.56.8>
"Leonard Challis" <perl@lennychallis.co.uk> wrote in
news:csn078$c7i$1@news7.svr.pol.co.uk:
> Personally, something like
>
>| mkdir("c:\temp", 0777) unless (-d "c:\temp");
>
> looks quite nice to me :D
1. Did you really want to create a directory whose name contains a tab
character?
2. There is no guarantee that a directory or file will not spring to
existence between the check for its existence and your attempt to create.
Therefore, you are better off with just attempting to create it straight
away.
Sinan.
------------------------------
Date: Thu, 20 Jan 2005 02:00:53 -0000
From: "Leonard Challis" <perl@lennychallis.co.uk>
Subject: Re: checking existance of a directory
Message-Id: <csn3cm$sqs$1@news8.svr.pol.co.uk>
"A. Sinan Unur" <1usa@llenroc.ude.invalid> wrote
> 1. Did you really want to create a directory whose name contains a tab
> character?
Thanks for pointing that one out. Programming in different languages besides
Perl really can mess your syntax up sometimes hehe :D
> 2. There is no guarantee that a directory or file will not spring to
> existence between the check for its existence and your attempt to create.
> Therefore, you are better off with just attempting to create it straight
> away.
That's interesting. I would have thought that it would be less than a split
second to check AND create the file. Is there really a possibility? Do you
have any examples? Thanks for the tip I'll bear that one in mind.
Are you saying something such as the following would be more "correct" in
your views?
| if (mkdir "dirname") { # created successfully }
| else { #not made }
or something similar?
Lenny
------------------------------
Date: Wed, 19 Jan 2005 23:25:38 GMT
From: "John W. Krahn" <someone@example.com>
Subject: Re: Help Perlling a program
Message-Id: <S%BHd.129079$KO5.34312@clgrps13>
YYusenet wrote:
>
> I am new to Perl, so I am probably making my programs (or scripts?) in a
> non-Perl way. I was wondering if the following script could be made with
> less repition or lines of code, or in a more Perl like way.
Certainly!
> The script is used so if I download a lot of pictures with not very useful
> names (like from digital camera software that exports pictures called
> IMG000001234 or something), it would name them in order, starting with zero.
> It also should work assuming that there may already be files named 0.jpg,
> etc.
>
> I am running this with ActivePerl versin 5.8.6.811 on windows XP.
>
> Here is the code:
> ----------------------------------------
>
> [snip code]
** UNTESTED
#!perl
use warnings;
use strict;
print "--------RENAMING STARTING--------\n";
my $counter = 0;
for my $file ( grep -f, glob '*.jpg *.gif' ) {
my $new = $counter++ . substr $name, rindex $name, '.';
redo if -e $new;
print "renaming $file...\t\tto\t$new\n";
rename $file, $new or die "unable to rename $file: $!";
}
print "--------PROGRAM FINISHED--------\n";
<STDIN>
__END__
John
--
use Perl;
program
fulfillment
------------------------------
Date: Thu, 20 Jan 2005 01:06:47 GMT
From: whansen_at_corporate-image_dot_com@us.com
Subject: Re: IPC looking for simple/best way to communicate
Message-Id: <41ef01db.26250355@news.sonic.net>
I'm going to go over your quick and dirty server code. I haven't been
able to work on this much recently due to other related issues being
more importatant.
I think my largest concern is how many processes can work well
together with memory being fininate. Each process is maintaing a
telnet session with a mainfraime. Current tests with 50 proceesses
operate at arround 150 requests per second combined. A request is
wasted if it is given for a product that is known to already be
'taken', and yes it would be better to make 145 valid requests per
second wasting 5 requests than to only make 50 valid requests. That's
why I think it's just something that I'll have to expierement with.
IPC::Shareable has a lot of overhead. So a server solution may be able
to decrease memory usage significantly increasing the number of
processes that can be run at the same time.
I hope I haven't pissed everyone off. Talking about things like this
is very helpful for thinking this through and I value all of your
suggestions.
On 11 Jan 2005 01:52:29 GMT, xhoster@gmail.com wrote:
>whansen_at_corporate-image_dot_com@us.com wrote:
>
>> I actually did something like that, but used a string instead of an
>> array. It greately sped things up. Each process merely looks for a
>> change to the string and if there are any it then decodes the string
>> and modifies its internal list.
>
>When you have your variable tied to IPC::Shareable, merely looking for a
>change isn't just "merely". It has a lot of overhead. (Not to mention
>potential for corruption if you aren't careful about locking).
>
>>
>> >> Basicly each process is iterating over a list (array) and every so
>> >> often a process gets a result that means that item no longer needs to
>> >> be ran, so it should remove it from it's list and notify the other
>> >> processes so that they can remove it from theirs as well.
>> >
>> >What are the consequences if a process doesn't get the message and runs
>> >that task anyway? Is it just a waste of resources, or is it fatal to
>> >the whole thing you are trying to do?
>> >
>> >How many such removal messages do you generate, in relation to the full
>> >size of the array to iterate over? If small, it would probably be most
>> >efficient to just run even the "removed" tasks and then filter them out
>> >in post-processing.
>>
>> It's not fatal, but it wastes the request.
>
>I'm not sure what the "request" is that you are talking about. That
>sounds like you are doing some kind of http or other network processing,
>rather than the parallel computational processing in a SMP environment what
>I had originally thought you were talking about. If you just have one CPU
>and are issuing many slow IOs, maybe you should look at using non-blocking
>IO in just one process rather than spawning an extravagant number of
>processes.
>
>Anyway, unless someone is charging you per request, a request is not
>something that can be wasted. Only the resources associated with it can be
>wasted, and you should weigh those resources against the resources that, as
>you have discovered, are used by excessive IPC::Shareable (or any other
>synchronization method).
>
>> Each request has a chance
>> of getting a product for my company. So, concentrating on products
>> that are still available and not wasting requests on taken products
>> will improve our chances of getting products 10-20% or so.
>
>Let us say that the overhead of extremely fine-grained synchronization
>means that you can only perform 50 requests per second, with none of them
>wasted. While the lowered overhead of more loose synchronization means you
>can do 150 requests per second, with 5 of them wasted? Would it be
>preferable to have 50 good requests per second or 145 good requests per
>second?
>
>> >Each process could keep their own private version of the array, and
>> >only refresh it against the shared version (or against a shared
>> >exception list) every now and then. How often it would do this refresh
>> >would depend on the cost of the refresh vs. the wasted effort that goes
>> >into processing tasks that have been removed since the last refresh.
>>
>> I have it do it for every request. Durring actual conditions the
>> requests slow down to a 10 second response which is all the time in
>> the world for this use.
>
>If you already have all the time in the world, why are you worried about
>further optimizing it?
>
>Xho
>
>--
>-------------------- http://NewsReader.Com/ --------------------
>Usenet Newsgroup Service $9.95/Month 30GB
------------------------------
Date: Wed, 19 Jan 2005 19:27:24 -0600
From: l v <lv@aol.com>
Subject: Re: Kalender programm
Message-Id: <41ef0978$1_2@127.0.0.1>
A. Sinan Unur wrote:
>
> Did you really have to quote the full message to say this?
>
> Sinan
Honestly, I concentrated on valid code and was saving the sniping until
the end and forgot in my haste to go to bed. Sorry
Len
------------------------------
Date: Wed, 19 Jan 2005 16:57:39 -0800
From: "Alfred Z. Newmane" <a.newmane.remove@eastcoastcz.com>
Subject: Re: Low level data manipulation in Perl
Message-Id: <358e04F4is41eU1@individual.net>
Arndt Jonasson wrote:
> "Leonard Challis" <perl@lennychallis.co.uk> writes:
>> I am referring to most people in this group who aren't newbies. If
>> you do plenty of searching first and then ask a question you will
>> still get flamed. People seem to enjoy flaming each other in this
>> group. It's quite sad really. I fully agree with people just posting
>> "I cant do it how do i do it!" questions, but when people show what
>> they have searched already and why they are still struggling do they
>> deserve being flamed still?
>
> The text you quote (*) mostly mentions attributions, and their absence
> in your article. You wrote "You don't seem to get me straight", with
> no indication on who or what you mean.
I don't know about you but it seemed plainly obvious to me that he was
referring to the name attributed /below/ that line:
(An excerpt.)
You don'tseem to get me straight...
> "Leonard Challis" <perl@lennychallis.co.uk> wrote:
>> What I am saying is this: Is there any way of opening a file, and
>> instead
>> of getting the text in side it, you actually see the 1s and0s or the
>> hexnumbers?
(End of excerpt.)
While he wasn't using "standard quoting" practice, is that hard to see
who he was referring to? (Nothing wrong with wanting to correct his
quoting technique, but I don't see why some people had to act like it
was so hard to tell...)
------------------------------
Date: Thu, 20 Jan 2005 01:15:01 -0000
From: "Leonard Challis" <perl@lennychallis.co.uk>
Subject: Re: Low level data manipulation in Perl
Message-Id: <csn0mn$msj$1@news6.svr.pol.co.uk>
"Alfred Z. Newmane" <a.newmane.remove@eastcoastcz.com> wrote in message
news:358e04F4is41eU1@individual.net...
> While he wasn't using "standard quoting" practice, is that hard to see who
> he was referring to? (Nothing wrong with wanting to correct his quoting
> technique, but I don't see why some people had to act like it was so hard
> to tell...)
This is the point I was trying to put forward, but anyhow let's drop the
issue it doesn't matter.
Would you mind pointing me in the direction of the newsgroup guidelines and
quoting techniques and anything else you feel I ought to know. Thanks for
your time,
Lenny Challis
------------------------------
Date: Wed, 19 Jan 2005 19:56:17 -0600
From: l v <lv@aol.com>
Subject: Re: telnet timed out
Message-Id: <41ef103e$1_2@127.0.0.1>
Petterson Mikael wrote:
The following untested code is for clearification only.
# below is the object refered in the documentation and is where
# you need to set the prompt when using login();
>>> my $telnet = new Net::Telnet ( Timeout=>30,
Prompt => '/ws3196.+]/',
>>> Errmode=>'die');
>>>
>>>
>>>
> ws3196{NONE}[espresso/rbssw/1.1]
>
> I am using the following (code below) but I still get a timeout.
>
> $telnet->open("$hostname");
> $telnet->login("$username", "$password");
Delete the waitfor() as it is not needed. However, you should check
that login() worked by calling errmsg .
> $telnet->waitfor('.[\]] $');
cmd() will return the output of 'who' if you use the command in array
context. @cmdOutput = $telnet->cmd('who');
> $telnet->cmd('who');
or you can use getlines() to read the output from who. @cmdOutput =
$telnet->getlines();
> $telnet->close;
>
> Hmmmm have I missed something fundamental about Telnet in this module.
> it is not obvious to me but maybe to a more experienced perl coder?
>
> //Mikael
Len
------------------------------
Date: 20 Jan 2005 02:00:31 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: The array ARGV
Message-Id: <Xns95E3D5BC58750asu1cornelledu@132.236.56.8>
"A. Sinan Unur" <1usa@llenroc.ude.invalid> wrote in
news:Xns95E3AA041650Aasu1cornelledu@132.236.56.8:
> "g3000" <carlton_gregory@yahoo.com> wrote in
> news:1106170458.765259.129850@z14g2000cwz.googlegroups.com:
>
>> I have read that the array ARGV holds the command line arguments.
>
> It is @ARGV. ARGV is a bareword.
Well, actually, there is a fair bit of magic associated with ARGV:
See perldoc perlvar.
Sinan.
------------------------------
Date: Wed, 19 Jan 2005 18:30:08 -0600
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: The world's shortest 'Hello World!' program: a proposal
Message-Id: <slrncutusg.6mf.tadmc@magna.augustmail.com>
Leonard Challis <perl@lennychallis.co.uk> wrote:
> That exactly what I mean about people getting flamed for no reason.
Have you considered that there might _be_ a reason, but that you do
not know what it is?
There is always a reason, IMO.
The debate could be about whether or not it is a good reason though.
--
Tad McClellan SGML consulting
tadmc@augustmail.com Perl programming
Fort Worth, Texas
------------------------------
Date: Thu, 20 Jan 2005 01:12:06 -0000
From: "Leonard Challis" <perl@lennychallis.co.uk>
Subject: Re: The world's shortest 'Hello World!' program: a proposal
Message-Id: <csn0h8$78e$1@newsg2.svr.pol.co.uk>
Heh, I guess your right. I admit there probably is a reason and whatever it
is I apologise.
Some people do seem to be quite untowards however, no matter the
circumstance, creating a mixed atmosphere.
Lenny
"Tad McClellan" <tadmc@augustmail.com> wrote in message
news:slrncutusg.6mf.tadmc@magna.augustmail.com...
> Have you considered that there might _be_ a reason, but that you do
> not know what it is?
>
> There is always a reason, IMO.
>
> The debate could be about whether or not it is a good reason though.
------------------------------
Date: 19 Jan 2005 15:58:39 -0800
From: ipellew@pipemedia.co.uk
Subject: Whats the variable holding the dir seperator?
Message-Id: <1106179119.617459.132580@z14g2000cwz.googlegroups.com>
Hi all;
Whats the Perl variable that holds the directory file seperator,
IE "/" or "\"
Is there a variable that holds the dot character?
Usually "."
EG perl.exe
A
Regards
Ian
------------------------------
Date: Thu, 20 Jan 2005 00:59:52 GMT
From: tiltonj@erols.com (Jay Tilton)
Subject: Re: Whats the variable holding the dir seperator?
Message-Id: <41ef0155.167101739@news.erols.com>
ipellew@pipemedia.co.uk wrote:
: Whats the Perl variable that holds the directory file seperator,
: IE "/" or "\"
Why do you believe there is one?
There isn't.
Use the File::Spec module for platform-independent path handling.
: Is there a variable that holds the dot character?
: Usually "."
: EG perl.exe
: A
No. A "." in a filename has no special significance to Perl.
Among its many capabilities, the the File::Basename module can snatch the
extension off a filename.
------------------------------
Date: Thu, 20 Jan 2005 01:04:13 GMT
From: gargoyle <gargoyle@no.spam>
Subject: Re: Whats the variable holding the dir seperator?
Message-Id: <hsDHd.19622$vh.10143@bignews4.bellsouth.net>
On 2005-01-19, ipellew@pipemedia.co.uk <ipellew@pipemedia.co.uk> wrote:
> Whats the Perl variable that holds the directory file seperator,
> IE "/" or "\"
> Is there a variable that holds the dot character?
> Usually "."
There's no variable for that stuff. Use the File::Spec module to work
with paths, if you need to. Though generally it's ok to just use / as a
separator in your code, when calling open(), etc.
------------------------------
Date: Thu, 20 Jan 2005 01:10:08 -0000
From: "Leonard Challis" <perl@lennychallis.co.uk>
Subject: Re: Whats the variable holding the dir seperator?
Message-Id: <csn0dl$8kb$1@newsg1.svr.pol.co.uk>
"gargoyle" <gargoyle@no.spam> wrote in message
news:hsDHd.19622$vh.10143@bignews4.bellsouth.net...
<snip>
> There's no variable for that stuff. Use the File::Spec module to work
> with paths, if you need to. Though generally it's ok to just use / as a
> separator in your code, when calling open(), etc.
Does anyone think that this could be a nice addition to the built in
variables in Perl, such as $`, $^0 etc? It would cerrtainly make life a lot
easier IMO.
Lenny Challis
------------------------------
Date: Thu, 20 Jan 2005 01:31:10 +0000
From: Big and Blue <No_4@dsl.pipex.com>
Subject: Re: Whats the variable holding the dir seperator?
Message-Id: <X4qdnZeUUcVDlHLcRVnygw@pipex.net>
Leonard Challis wrote:
>
> Does anyone think that this could be a nice addition to the built in
> variables in Perl, such as $`, $^0 etc? It would cerrtainly make life a lot
> easier IMO.
In what way would it make your life easier?
What is the pathname separator on, say, VMS? (Does Perl run on
VMS???). You are assuming that suhc concepts are universal.
Likewise the comment about the '.' in pathnames. On Unix systems this
is just a dot - it has no special meaning at all.
--
Just because I've written it doesn't mean that
either you or I have to believe it.
------------------------------
Date: Thu, 20 Jan 2005 01:44:56 -0000
From: "Leonard Challis" <perl@lennychallis.co.uk>
Subject: Re: Whats the variable holding the dir seperator?
Message-Id: <csn2ep$o1g$1@news6.svr.pol.co.uk>
"Big and Blue" <No_4@dsl.pipex.com> wrote
> In what way would it make your life easier?
Well, instead of using something like the File::Spec module for
platform-independent path handling, we could simply do something like:
my $file = "dir1$*dir2$*file.ext";
#where $* is the seperator
Just a thought.
Lenny
------------------------------
Date: 20 Jan 2005 01:49:22 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Whats the variable holding the dir seperator?
Message-Id: <Xns95E3D3D8732BBasu1cornelledu@132.236.56.8>
ipellew@pipemedia.co.uk wrote in news:1106179119.617459.132580
@z14g2000cwz.googlegroups.com:
> Hi all;
>
> Whats the Perl variable that holds the directory file seperator,
> IE "/" or "\"
>
> Is there a variable that holds the dot character?
> Usually "."
> EG perl.exe
> A
>
The answer has not changed since the last time you posted the same message
with a different subject line.
http://tinyurl.com/4kf3f
Sinan.
------------------------------
Date: 20 Jan 2005 01:57:49 GMT
From: "A. Sinan Unur" <1usa@llenroc.ude.invalid>
Subject: Re: Whats the variable holding the dir seperator?
Message-Id: <Xns95E3D5474AB36asu1cornelledu@132.236.56.8>
"Leonard Challis" <perl@lennychallis.co.uk> wrote in news:csn2ep$o1g$1
@news6.svr.pol.co.uk:
> "Big and Blue" <No_4@dsl.pipex.com> wrote
>
>> In what way would it make your life easier?
>
> Well, instead of using something like the File::Spec module for
> platform-independent path handling, we could simply do something like:
>
> my $file = "dir1$*dir2$*file.ext";
> #where $* is the seperator
On the other hand, if $dir1, $dir2 and $file are variables, you end up
with:
my $path = $dir1.$*.$dir2.$*.$file.'.ext';
I am hoping that I am not the only one who thinks
use File::Spec::Functions 'catfile';
my $path = catfile $dir1, $dir2, "$file.ext";
is vastly clearer.
File::Spec provides a lot in the way of platform neutral file name and
path handling -- more than just a simple variable holding the directory
separator character.
Additionally, one is usually more interested in using the correct
character(s) for the OS than the actual character(s) themselves.
Sinan.
------------------------------
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 7675
***************************************
