Nick Tonkin <[EMAIL PROTECTED]> writes:
> I'm confused. Since when did bloat surpass elegance as a measure of
> success in Perl programming?
Indeed. Generic question: "How many lines of code have you spent today?"
--
Frank Cringle, [EMAIL PROTECTED]
voice: (+49 7745) 928759; fax: 928761
Bill Desjardins <[EMAIL PROTECTED]> writes:
> Just as a FYI about something that caught my attention recently. This year
> on Saturday September 8, 2001, the unix time stamp flips to 1 billion and
> gets another digit going from 9 to 10 digits. Not sure if anyone else but
> me is using the timesta
Matt Sergeant <[EMAIL PROTECTED]> writes:
> Now to the wierd bit. I could track this down if it wasn't for this:
>
> The memory leak starts after the Nth hit, usually around 35. This is
> running under httpd -X.
>
> So it goes along very happily for 35 hits - memory usage is rock solid
> stable.
Nicolas MONNET <[EMAIL PROTECTED]> writes:
> Might be a faq, but why would open(FH,'|qmail-inject') fail with
> fatal: read-error from within mod_perl?
Are the files in /var/qmail/control world readable?
Is QMAILMFTFILE defined in the environment and pointing to a file that
the httpd process can
[EMAIL PROTECTED] (William R. Ward) writes:
> [EMAIL PROTECTED] writes:
> >please use the [EMAIL PROTECTED] list for support questions.
>
> Then please put that e-mail address somewhere obvious on the
> perl.apache.org website. Yours was the only one I could find.
> (It was listed as [EMAIL PROT
Ken Williams <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (Frank D. Cringle) wrote:
> >
> >This sounds dreadfully microsoftian. Trashcan: check; Bouncing
> >paperclip: check.
>
> Well yeah, if you choose features that nobody cares about, then nobody will
&g
Drew Taylor <[EMAIL PROTECTED]> writes:
> Ken Williams wrote:
> >
> > I suggest having not just a simple checkmark, but a 3-way check. A
> > system either supports a feature, or it doesn't, or it *optionally*
> > supports it (can be switched on and off). This is often very helpful to
> > know,
Vivek Khera <[EMAIL PROTECTED]> writes:
> > "RE" == Rob Egan <[EMAIL PROTECTED]> writes:
>
> RE> CGI scripts to behave in mod_perl. All it does is capture e-mail addresses,
> RE> and place them in a text file so we can gather them up later and drop them
> RE> into a database. If you run the s
Dave DeMaagd <[EMAIL PROTECTED]> writes:
> Have an application that generates nicely formatted HTML (from
> templates, so that they can be easily edited), but since there's a
> awful lot of extra line breaks (and other things, like comments) that
> we'd like to strip out (save bandwidth), is there
Lloyd Zusman <[EMAIL PROTECTED]> writes:
> I've been sending email to `[EMAIL PROTECTED]' almost
> every day for the past week or two, but I still keep receiving email
> from this list.
The list is run using ezmlm. Sending mail to modperl-unsubscribe is
just the first step in the process. You s
"Benjamin Reed" <[EMAIL PROTECTED]> writes:
> I've turned off PerlSendHeader, but no matter what I do, it seems that I'm
> already getting headers before I ever print anything.
If you turn PerlSendHeader off, you are responsible for sending the
headers yourself. In the Apache API, and mod_perl's
John Walker <[EMAIL PROTECTED]> writes:
> After fighting with RedHat SWS and never being sure if what went wrong
> was my scripts' fault or some wierdness in my
> Apache/mod_perl/RedHat-SSL, I'm going to follow the instructions in the
> guide to make my own. (Would have saved a lot of time if I ju
jiminy <[EMAIL PROTECTED]> writes:
> PS - this is my first time to post here. Most mailing lists I've seen have
> as the reply-to the address of the list, however this one doesn't seem to
> have that feature, so that when I just reply to a message, it does to the
> poster, not the list. Am I perce
Daniel Jacobowitz <[EMAIL PROTECTED]> writes:
> This worked! Can I get opinions on the attached patch?
I am not competent to check whether the patch has any hidden problems,
but I hope Doug will be able to evaluate it and include it in the next
release. Your description of the sequence leading
Stas Bekman <[EMAIL PROTECTED]> writes:
> Just read the mod_ssl vs. apache_ssl thread at /.org:
> http://slashdot.org/apache/99/12/22/1711203.shtml
>
> jimjag claims that DSO is slower than static builds at the runtime:
>
>
> Q: Why has using DSOs anything to do with run-time performance? I alw
Ricardo Kleemann <[EMAIL PROTECTED]> writes:
> Hmmm :-(
>
> On 14 Jan 2000, Frank D. Cringle wrote:
>
> >
> > Without having checked your list, I'll wager that the "good" modules
> > are all pure perl and the "bad" ones use machine
Ricardo Kleemann <[EMAIL PROTECTED]> writes:
> Hi everyone,
>
> I don't know what's causing this, and there are no errors being logged in
> my error_log.
>
> I'm running apache 1.3.9, mod_perl 1.21, linux 6.1
>
> I have a startup.pl with a bunch of modules in it. If I run the startup.pl
> by it
Alan Burlison <[EMAIL PROTECTED]> writes:
> $ LD_PRELOAD='/home2/web/apache_1.3.9/libexec/libperl.so \
> /home1/software/perl/debug/lib/5.00503/sun4-solaris/CORE/libperl.so'
> ./httpd
> $
>
> hey presto! A working httpd.
Excellent!
> Obviously this is just a workaround - the
> real fix is to
Alan Burlison <[EMAIL PROTECTED]> writes:
> Note that the SEGV only happens when Apache/perl/modperl are dynamically
> linked. Statically linked code behaves fine. I'm wondering if the
> mod_perl code goes down a different code path if it is dlopen'd rather
> than being statically linked.
Apach
Jeff Macdonald <[EMAIL PROTECTED]> writes:
> Hi,
> I've read the archives, and from what I can tell, mod_perl sometimes
> works as a DSO, and other times doesn't. I've seen Frank Cringle say it
> works, then later to link static. I've seen Doug say it should work.
> I've seen other say it works, b
David Bushong <[EMAIL PROTECTED]> writes:
> A few times in the past months (I've been playing with Embperl a
> lot, it's a hell of a lot more fun than JSP, straight CGI, or
> HTML::Template),
I have been trying to resist asking this, but it's no use:
why ?
[ I'm a recent convert to HTML::Templa
Christof Damian <[EMAIL PROTECTED]> writes:
> there must be someone (*) out there who has a working spec file for:
>
> Apache 1.3.9
> + shared mod_ssl-1.3.9.2.4.6
> + static mod_perl
> + shared everything else
>
> it would be nice if it would also keep the file layout from redhat 6.0
> or 6.1
I
Dave Mee <[EMAIL PROTECTED]> writes:
> Hello, mod_perloids.
>
> I'm having a gutfull of trouble sending mail under mod_perl. I'm doing
> it by the books, to wit, the cookbook and the bigbirdie book, under rh
> linux 5.2.
>
> the code is
>
> warn ("MAIL: Opening sendmail... path is \"".$sen
Stas Bekman <[EMAIL PROTECTED]> writes:
> My personal comment on both of your previews, is that they are very cool!
> But while being flattered with having a Guide as part of the main menu,
> this is unfair to other folks who wrote an invaluable documentation
> (Vivek, Frank and other).
For my p
"Anthony Gardner" <[EMAIL PROTECTED]> writes:
> I'm not sure if I'm being a bit fussy here, or indeed banging my head
> against a wall but can users of these mailing lists make the Subject part of
> the msg more descriptive.
>
> This will help readers to scroll through quicker and to read what
"Andrei A. Voropaev" <[EMAIL PROTECTED]> writes:
> Would it be possible to remove everything after __END__ before
> wrapping it into a function?
That requires a full-blown perl parser, to decide if __END__ is really
__END__.
print "Content-type: text/plain\n\n"
print <
Ofer Inbar <[EMAIL PROTECTED]> writes:
> Alex Krohn <[EMAIL PROTECTED]> wrote:
> (mis)handles lexically scoped variables. This oddity only comes into
> play if you use a lexical variable in a block *and* a sub-block of
> that block, and you run that same code multiple times, and the values
> are
27 matches
Mail list logo
