[25567] in Perl-Users-Digest
Perl-Users Digest, Issue: 7811 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Feb 22 06:05:44 2005
Date: Tue, 22 Feb 2005 03:05:17 -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, 22 Feb 2005 Volume: 10 Number: 7811
Today's topics:
Re: Correct way to inherit from 3rd party class <spamtrap@dot-app.org>
Re: cubic root subroutine <do-not-use@invalid.net>
Re: How to NOT use utf8. <vek@station02.ohout.pharmapartners.nl>
Perl Expect send array <geen@mail.invalid>
Re: Perl Expect send array (Anno Siegel)
Re: Perl Expect send array <geen@mail.invalid>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Problems using Module PDF::Create (kielhd)
Regular expression problem <gwillem@gmail.com>
Re: swift MT940 files <zen13097@zen.co.uk>
Re: The Problem with Perl <dformosa@zeta.org.au>
Re: Web Application Installation Script <andres@exlibris-usa.com>
What Is This ".pureftpd-rename.47188.a1518ccc" File? <>
Re: What Is This ".pureftpd-rename.47188.a1518ccc" File <jurgenex@hotmail.com>
Re: What Is This ".pureftpd-rename.47188.a1518ccc" File <>
Re: What Is This ".pureftpd-rename.47188.a1518ccc" File <jurgenex@hotmail.com>
Re: What Is This ".pureftpd-rename.47188.a1518ccc" File <josef.moellers@fujitsu-siemens.com>
Re: What Is This ".pureftpd-rename.47188.a1518ccc" File <josef.moellers@fujitsu-siemens.com>
Re: Why aren't 'warnings' on by default? <tassilo.von.parseval@rwth-aachen.de>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Tue, 22 Feb 2005 01:09:51 -0500
From: Sherm Pendley <spamtrap@dot-app.org>
Subject: Re: Correct way to inherit from 3rd party class
Message-Id: <qPqdnVAHn6gyUYffRVn-og@adelphia.com>
jonnytheclown wrote:
> What is the correct (recommended) way to inherit from an arbitrary
> class when I know nothing about its internals (and don't want to know)
> but need to hold additional instance variables. The next question is
> how should I implement a class that allows other programmers to inherit
> from it and hold their own instance variables.
Have you had a look at "perldoc perlbot"?
sherm--
--
Cocoa programming in Perl: http://camelbones.sourceforge.net
Hire me! My resume: http://www.dot-app.org
------------------------------
Date: 22 Feb 2005 09:35:33 +0100
From: Arndt Jonasson <do-not-use@invalid.net>
Subject: Re: cubic root subroutine
Message-Id: <yzdwtt1yotm.fsf@invalid.net>
Scott Bryce <sbryce@scottbryce.com> writes:
> Arndt Jonasson wrote:
>
> > You may want to handle the sign separately, since letting $foo be
> > negative results in NaN ("Not a number"), at least here, on
> > Solaris 2.8 x86.
>
> Same on Win32.
>
> > Also, it may be worth making sure that the cube of an integer always
> > comes back as an integer, and not with a little rounding-error,
>
> I assume you mean that the cube root of a cube comes back an
> integer. That doesn't appear to be a problem on my machine.
Yes, I meant "comes back from the cube root subroutine". But it is a
problem on my machine:
perl -e 'printf "%d\n", int(64**(1/3))'
3
------------------------------
Date: 22 Feb 2005 08:55:54 GMT
From: Villy Kruse <vek@station02.ohout.pharmapartners.nl>
Subject: Re: How to NOT use utf8.
Message-Id: <slrnd1lssq.1rl.vek@station02.ohout.pharmapartners.nl>
On Sun, 20 Feb 2005 18:10:20 +0100,
pkaluski <pkaluski@piotrkaluski.com> wrote:
> Oppss! I was so excited looking for an answer that I forgot to check in
> perlrun :). Thanks!
>
There wer some changes in 5.8.1 that might be interesting in this context.
Check the -C option.
Villy
------------------------------
Date: Tue, 22 Feb 2005 10:07:02 +0100
From: ruud <geen@mail.invalid>
Subject: Perl Expect send array
Message-Id: <cvesp9$e0e$1@box.nl-netwerken.com>
I am having a logfile called "log".
I am reading the whole logfile into an array:
open (FPTR,"/home/ruud/log");
@logfile = <FPTR>;
When i do print "@logfile"; i get the correct output.
But when i want to send the log to an (internal) newsgroup like this:
$exp->send ("@logfile");
It adds between every line an enter (\n)
Is there a way to work around that ?
--
Gr. Ruud
news://news.nl-netwerken.com
------------------------------
Date: 22 Feb 2005 09:39:30 GMT
From: anno4000@lublin.zrz.tu-berlin.de (Anno Siegel)
Subject: Re: Perl Expect send array
Message-Id: <cveuki$i88$1@mamenchi.zrz.TU-Berlin.DE>
ruud <geen@mail.invalid> wrote in comp.lang.perl.misc:
> I am having a logfile called "log".
> I am reading the whole logfile into an array:
>
> open (FPTR,"/home/ruud/log");
> @logfile = <FPTR>;
>
> When i do print "@logfile"; i get the correct output.
> But when i want to send the log to an (internal) newsgroup like this:
>
> $exp->send ("@logfile");
> It adds between every line an enter (\n)
>
> Is there a way to work around that ?
perldoc -f chomp
Anno
------------------------------
Date: Tue, 22 Feb 2005 11:27:07 +0100
From: ruud <geen@mail.invalid>
Subject: Re: Perl Expect send array
Message-Id: <cvf1fc$ebd$2@box.nl-netwerken.com>
Anno Siegel wrote:
>> It adds between every line an enter (\n)
>>
>> Is there a way to work around that ?
>
> perldoc -f chomp
Thank you for the help, it's working now.
--
Gr. Ruud
news://news.nl-netwerken.com
------------------------------
Date: 22 Feb 2005 08:22:27 GMT
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.5 $)
Message-Id: <421aebc2$0$23560$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: 22 Feb 2005 02:44:34 -0800
From: kielhd@freenet.de (kielhd)
Subject: Problems using Module PDF::Create
Message-Id: <10a4173d.0502220244.7ee0ae7c@posting.google.com>
Hi NG,
After creating the FIRST page successfully with text and drawing, I
have problems to put some text on the second page.
I can draw lines on the SECOND page using ths function
$page2->line($x1, $y1, $x2, $y2);
but as soon as I try to print some text on the SECOND page using the
function
$page2->string($f2, $SIZE2, $COL2, 612 - 10 - $LINE2 * $SIZE2,
"Hannibal");
the text is printed on the FIRST page.
As the dokumentation of the module PDF::Create is very limited, I
would like to have a look at some examples.
Does somebody have experience with this module?
TIA,
Henning
------------------------------
Date: Tue, 22 Feb 2005 11:31:08 +0100
From: Willem <gwillem@gmail.com>
Subject: Regular expression problem
Message-Id: <421b09ec$0$28992$e4fe514c@news.xs4all.nl>
I would like to make a tool that assists in generating ClamAV signatures
[1]. However, I'm stuck with the regular expression required to
transform some, but not all of the signature to hex.
Suppose this signature:
xxxxversion(1|3|5.7)xxxxxxxx
I would like to encode anything _but_ the control characters (,|,) to
hex. However, I only want to protect these control characters that are
included in the following expression: m#\([\d\.|]\)#. In words: the (, )
and | that are used to mark alternatives for version numbers need to
remain unaltered.
Could anyone give me a clue on the regex?
Thanks!
Willem
[1] http://www.clamav.net/doc/0.80rc/signatures.pdf
------------------------------
Date: 22 Feb 2005 09:17:00 GMT
From: Dave Weaver <zen13097@zen.co.uk>
Subject: Re: swift MT940 files
Message-Id: <421af88c$0$8746$db0fefd9@news.zen.co.uk>
Seansan <sheukels=cuthere=@yahooo.co.uk> wrote:
> I am trying to read a bank file with a format called MT940 swift
> into a data structure. The format is as follows:
> :28C:12345/1
> :60F:C041019GBP607,20
> :61:041020C110088,00N540NONREF
That isn't a format specification, it's just a sample of the data. We
can only guess (probably incorrectly) what the format is from a sample
data set. Especially one so brief.
> I am still learning unpack (I always used s/regex/ and then $1, $2,
> etc ..)
^
ITYM m/regex/
The regex approach seem best suited to this data, from what I can see
of it.
> and am wondering if someone can help me decode one of these lines
> e.g. the :60F: record. Is it even possible? The format =
> :<record>:<date,6chars><str,3><amount,0-32>
No it isn't. Let's take another look at that line:
> :60F:C041019GBP607,20
What's that 'C'? Doesn't look like it's part of the date.
And the amount after "GBP" is not in the range 0-32.
Ignoring that:
#!/usr/bin/perl
use strict;
use warnings;
while( <DATA> ) {
if ( /:([^:]+):C(\d{6})(...)(\d+)/ ) {
print qq(record: "$1" date: "$2" str: "$3" amount: "$4"\n);
}
}
__DATA__
:28C:12345/1
:60F:C041019GBP607,20
:61:041020C110088,00N540NONREF
this prints:
record: "60F" date: "041019" str: "GBP" amount: "607"
As you can see, your suggested format matches only one of those 3
records ( and then, only if ignoring that 'C' ).
I suggest you determine your data format first. Then it's simply a
case of composing one or more regexs to extract the information you
require.
------------------------------
Date: 22 Feb 2005 21:42:18 +1100
From: ? the Platypus {aka David Formosa} <dformosa@zeta.org.au>
Subject: Re: The Problem with Perl
Message-Id: <m38y5gzxit.fsf@dformosa.zeta.org.au>
Charlton Wilbur <cwilbur@mithril.chromatico.net> writes:
> >>>>> "?" == ? the Platypus {aka David Formosa}
> >>>>> <dformosa@zeta.org.au> writes:
>
> ?> Charlton Wilbur <cwilbur@mithril.chromatico.net> writes:
>
> >> And is it easier for a manager to prevent teams from treading
> >> on each others' toes, or to turn a programmer with no
> >> self-discipline into one? If history proves me wrong, I'd like
> >> to see more examples.
>
> ?> Ok the best place that explians this is "The Mythical Man
> ?> Month" however Paul Graham has a number of excelent essays on
> ?> the subject.
>
> Yes, I've read "The Mythical Man-Month." I don't believe it addresses
> the issue of programmer skill as definitively as you think it does.
True I will give you that, however I would counter aruge that it
speeks very strongly against the so called "Mongolian hord" method,
that you seem to be advocating. I suspect that a small number of bad
programers may be more productive then a large group.
[...]
> ?> If the software project is getting so big that its infeasable
> ?> to assign a team of 2 to 3 people to it (I think that 5 is a
> ?> rather large team for a software project) then it should be
> ?> split up into sections that are large enought for 2-3 people to
> ?> work on. (And the interfaces between these sections should be
> ?> precisely defined and supported with test sweets).
>
> Which is a beautiful notion -- but the tasks of partitioning and
> defining interfaces are the hard part of the job.
Yes its the role of the architect (also called the designer), who is
most likely the lead programmer. A company doesn't just start a new
project with a fresh set of people, there are allways programers in
the company who are more experienced and respected. You pick this
person as your lead programmer, have them do the design work, and
define the unit tests.
[...]
> Beyond that, in the real world many software projects require more
> than 5 people. Your examples of small software projects - Unix and
> Perl - are both currently developed by teams of *many* more than five
> people.
However the original projects started off with tiny teams, as they
expanded rather then having larger teams, they have people operating
inderpendently.
> (How many people have contributed patches to the Linux
> kernel? How many people are on the core development teams for the
> BSDs? How many people are on the p5p mailing list?)
How meany people work on a perticular patch to the linux kernal? How
meany people check that that patch is worth installing? How meany
people are the pumpking?
--
Please excuse my spelling as I suffer from agraphia. See
http://dformosa.zeta.org.au/~dformosa/Spelling.html to find out more.
Free the Memes.
------------------------------
Date: 21 Feb 2005 21:05:34 -0800
From: "Andres Monroy-Hernandez" <andres@exlibris-usa.com>
Subject: Re: Web Application Installation Script
Message-Id: <1109048734.528373.145570@c13g2000cwb.googlegroups.com>
You could ship your web application with Perl and Apache binaries
already configured to work with your web app. You will save a lot of
time during the installation because it will be just unpacking a tar
file. This can be more complicated if you have to support a lot of
OS's. But it's an option.
--
Andres Monroy-Hernandez
Ex Libris Inc.
------------------------------
Date: Mon, 21 Feb 2005 23:35:58 -0600
From: mary <>
Subject: What Is This ".pureftpd-rename.47188.a1518ccc" File?
Message-Id: <03hl111hgftctd6nan6rakvj850lhf3lnu@4ax.com>
There is a 7MEG file in my cgi-bin directory,
chmod 600, which I cannot delete. What is this file?
Its name:
.pureftpd-rename.47188.a1518ccc
Thanks!
mary
------------------------------
Date: Tue, 22 Feb 2005 06:31:02 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: What Is This ".pureftpd-rename.47188.a1518ccc" File?
Message-Id: <GkASd.32794$uc.16160@trnddc08>
mary wrote:
> There is a 7MEG file in my cgi-bin directory,
> chmod 600, which I cannot delete. What is this file?
> Its name:
>
> .pureftpd-rename.47188.a1518ccc
It's a 7MEG file named .pureftpd-rename.47188.a1518ccc
Do you have a Perl question, too?
jue
------------------------------
Date: Tue, 22 Feb 2005 01:03:26 -0600
From: mary <>
Subject: Re: What Is This ".pureftpd-rename.47188.a1518ccc" File?
Message-Id: <r8ml11ldh90j6imiemu5ehpg5dphqtfkui@4ax.com>
Sure stupid. Do you have something better to do?
On Tue, 22 Feb 2005 06:31:02 GMT, "Jürgen Exner"
<jurgenex@hotmail.com> wrote:
>mary wrote:
>> There is a 7MEG file in my cgi-bin directory,
>> chmod 600, which I cannot delete. What is this file?
>> Its name:
>>
>> .pureftpd-rename.47188.a1518ccc
>
>It's a 7MEG file named .pureftpd-rename.47188.a1518ccc
>
>Do you have a Perl question, too?
>
>jue
------------------------------
Date: Tue, 22 Feb 2005 07:27:47 GMT
From: "Jürgen Exner" <jurgenex@hotmail.com>
Subject: Re: What Is This ".pureftpd-rename.47188.a1518ccc" File?
Message-Id: <T9BSd.18185$uc.2138@trnddc01>
mary spit TOFU into our faces::
> Sure stupid.
Indeed, your question was exactly that.
What on gods blue planet made you believe that your question had anything,
_anything_at_all_, to do with the programming language Perl?
> Do you have something better to do?
Well, yeah, there is always the the PLONK, but I think it is not quite
warrented yet, emphasiz being on _yet_.
>> mary wrote:
>>> There is a 7MEG file in my cgi-bin directory,
>>> chmod 600, which I cannot delete. What is this file?
>>> Its name:
>>>
>>> .pureftpd-rename.47188.a1518ccc
jue
------------------------------
Date: Tue, 22 Feb 2005 08:38:25 +0100
From: Josef Moellers <josef.moellers@fujitsu-siemens.com>
Subject: Re: What Is This ".pureftpd-rename.47188.a1518ccc" File?
Message-Id: <cvenie$chf$1@nntp.fujitsu-siemens.com>
mary wrote:
> There is a 7MEG file in my cgi-bin directory,
> chmod 600, which I cannot delete. What is this file?
> Its name:
>=20
> .pureftpd-rename.47188.a1518ccc
I _guess_ it has something to do with nfs. When deleting (and probably=20
renaming) files in an nfs export, nfs has to take some wierd steps when=20
deleting files, as the files may be (are are) opened by another host, so =
it can't just delete the file but must keep it for some time. The same=20
may apply to renaming files. The 'a1518ccc' may be the hex=20
representation of the other host's IP address.
(explicitly vague as I can't remember the details).
--=20
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
------------------------------
Date: Tue, 22 Feb 2005 08:41:51 +0100
From: Josef Moellers <josef.moellers@fujitsu-siemens.com>
Subject: Re: What Is This ".pureftpd-rename.47188.a1518ccc" File?
Message-Id: <cvenor$chf$2@nntp.fujitsu-siemens.com>
J=FCrgen Exner wrote:
> mary wrote:
>=20
>>There is a 7MEG file in my cgi-bin directory,
>>chmod 600, which I cannot delete. What is this file?
>>Its name:
>>
>>.pureftpd-rename.47188.a1518ccc
>=20
>=20
> It's a 7MEG file named .pureftpd-rename.47188.a1518ccc
>=20
> Do you have a Perl question, too?
To give mary the benefit of the doubt, it may very well be that she=20
stumbled across this file while working on a perl-based cgi-script.
--=20
Josef M=F6llers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize
-- T. Pratchett
------------------------------
Date: Tue, 22 Feb 2005 08:18:48 +0100
From: "Tassilo v. Parseval" <tassilo.von.parseval@rwth-aachen.de>
Subject: Re: Why aren't 'warnings' on by default?
Message-Id: <slrnd1ln6o.q8.tassilo.von.parseval@localhost.localdomain>
Also sprach nospam@geniegate.com:
> In: <slrnd1c8au.13a.tassilo.von.parseval@localhost.localdomain>, "Tassilo v. Parseval" <tassilo.von.parseval@rwth-aachen.de> wrote:
>>If warnings in module context really and rightly suggest there's a bug,
>>then the bug itself will sooner or later manifest in some other way,
>>wont it? Otherwise it wouldn't be one. The point being that warnings
>>rarely provide information useful to people not in charge of the code.
>
> This is where I think warnings belong, for the developers.
>
> I do appreciate the ability to use them, to *me* it's kind of like
> discussing whether or not '-g' should be on gcc by default.
>
> -g is great for debugging but I wouldn't want it on by default.
I always wanted to write a little Perl script that processes Makefiles
and removes any signs of '-g'. Lately I've come across so many programs
that forcibly put them in regardless of the presence of the
'--disable-debug' and '--enable-optimize' switches for Configure.
> Likewise, -w is a useful tool.
>
> If I see existing code that generates lots of warnings with -w,
> I don't consider it buggy. If it bombs with 'use strict'
> I consider it 'potentially buggy.'
>
> Where MY code generates warnings, I will sometimes look into it,
> but usually it's a harmless warning.
>
> I suppose one could argue the same about 'use strict', that
> perhaps it should be off for finished modules. (I like it
> on, but I appreciate 'use strict' being optional)
Strictures are, for me anyway, a different pair of shoes. They leave
almost no visible marks at runtime safe for croaking on symbolic
references. Therefore I never bothered to yank them out again before a
release.
As for 'use warnings', I don't have to remove that from my code either
because I rarely use it. Instead, I have -w switched on in my
testscripts (not the one in t/ but rather my private ones) which will
automatically propagate them into my module.
> Anyone know of the performance differences with -w turned on/off?
> (Same with strict?)
There are rumours that both would have a slight but still noticeable
effect on runtime performance. This is something I refuse to believe.
Strictures and warnings are merely flags that are either set or not. In
both cases however, the Perl interpreter has to check them. The
additional code executed when one of them is one is negligible (usually
just one statement).
This naturally only holds true for programs that don't emit warnings.
For those that do there is a slow-down caused by the simple fact that
warnings write to stderr.
Tassilo
--
use bigint;
$n=71423350343770280161397026330337371139054411854220053437565440;
$m=-8,;;$_=$n&(0xff)<<$m,,$_>>=$m,,print+chr,,while(($m+=8)<=200);
------------------------------
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 7811
***************************************
