Title: RE: Search Engine Theory
Check out the book Managing Gigabytes
Text indexing theory and algorithms. Source code too.
-Original Message-
From: Jamie Krasnoo [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 27, 2001 3:03 PM
To: Modperl
Subject: Search Engine Theory
Can
Title: RE: Debugging mod_perl with gdb
Hey thanks. I'll try this. I tried the 'man gdb' command and it didn't help much I'm afraid...
-Original Message-
From: sterling [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 06, 2001 12:33 PM
To: Shane Adams
Cc: [EMAIL PROTECTED]
Subject
Modperlers...,
Hello, this is Shane Nay, I used to post quite a bit. (Hello Josh, Stas,
Peren, Doug, and many others of course) BTW Stas,
$contributors=~/Shane/Shane Nay/;, and big Thanks .
Well I'm posting now, (and resubscribed :) because I need someone to fill a
modperl developement
/perl5/site_perl/5.005/i386-freebsd/Digest/MD5.pm line 20.
BEGIN failed--compilation aborted at
/usr/local/lib/perl5/site_perl/5.005/Apache/ASP.pm line 13.
[Tue Dec 19 17:55:44 2000] [error] Undefined subroutine
Apache::ASP::handler called.
Thanks
-Shane Reid
it,
cansuexec be used, I was unclear as to if it could be used and if it was
being used if some files needed to be modified etc. Any help on setting it
up suexec with modperl or just correcting this error would be
appreciated.
Shane Reid
Title: RE: :Parse segmentation fault
Yes. We found a problem in Expat.pm line 451 (in sub parse). The following chunk of code (latest version from cpan)
sub parse {
my $self = shift;
my $arg = shift;
croak Parse already in progress (Expat) if $self-{_State_};
$self-{_State_} = 1;
my
: Shane Adams; '[EMAIL PROTECTED]'Subject: RE:
:Parse segmentation fault
I did a
little more digging around and found that you could also avoid the problem by
turning off EXPAT in apache with:
Rule
EXPAT=no
Which fix
is more preferable?
-Original Message-From
Title: RE: :Parse segmentation fault
no
clue. I emailed your comment to a friend at work and see what he can make
of it. He's the fellow that found the cause of the segfault in the first
place.
Shane
-Original Message-From: Herrington, Jack
[mailto:[EMAIL PROTECTED]]Sent
Title: Core file (debugging info turned on/stack trace)
Apache 1.3.12, mod_perl 1.24, Perl 5.6.0, Redhat 6.1
...
Program terminated with signal 11, Segmentation fault.
...
0 0x814abd4 in Perl_sv_setsv (dstr=0x8d34514, sstr=0x84afba4) at sv.c:2774
#1 0x813b6b3 in Perl_pp_sassign () at
($parser, $arg);
}
$self-{_State_} = 2;
$result or croak $self-{ErrorMessage};
}
As I recall, Doug, you helped me patch part of HTML::Mason dealing with typeglobs under an eval ... I believe that * is a typeglob in perl yes?
-Original Message-
From: Shane Adams
Sent: Tuesday, September 26
is received on line 1254 in pp_ctl.c
(course you could probably tell that =)
To bad
I can't take a peek into the POPSUB macro itself... It's like 20 lines long and
there is no way to get gdb to display the macro. Least no way I
know.
Shane
How
the hell do people actually try to fix this? The learning
Title: Core dumping
Sorry
I forgot to include the stack trace with debugging turned
on:
#0 0x81714f7 in Perl_dounwind (cxix=3) at
pp_ctl.c:1254#1 0x8171bd1 in Perl_die_where (
message=0x848eb68 "Can't upgrade that kind of scalar at
/home/shane/sparty/runtime/perl/lib/site_perl/5.6.0
(there are like 20 different ones and I forget which is which - check the docs) to wake up and drain the queue.
If you want anymore speed then that, you have to either install ram disks or seriously write your own mta. We installed ram disks =)
Shane
-Original Message-
From: Andrew
if this will shed any details as to what the problem is.
Any help is appreciated.
Shane
odperl and a machine of your own without paying the hefty
cost of a colocation service. (You can restrict memory for each VM, and each
VM has bios and all that jazz..., check it out vmware.com)
Thanks,
Shane.
(Credit where credit is due: This was originally Josh Chamas's idea)
On Wed, 28 Jun 2000, yo
of memory,
and then it digs into its own swap rather than tearing down everyone elses
modperl.
Shane.
could be
worked out that number could be higher. The other problem is getting the right
data structure to handle this stuff..., working on that right now.)
Thanks,
Shane.
BTW: This is part of a larger project to abstract fast i/o into a library...,
the goal is to have a set of source code you
symbols in place, I would say it's probably the AIX linkers
fault. I don't know much about AIX specifically but I have heard lots of
people complain about their linker :-(.
Thanks,
Shane.
;what happened log")
I can see from Jens-Uwe's reply that the DSO building process is a LOT
different on AIX than on linux with gnutools. (Hey what happened to gcc
--shared? :-)
Sorry,
Shane.
was helping out with I hadn't used
Windows in about 2 years. (BTW: Huge plug for VMWare, that's some
REALLY cool software, not just for runing windows on linux, but testing other
OSes... I can't say enough good stuff about vmware)
Thanks,
Shane.
to
think long and hard about how you're using your sessions.
Shane.
Option three (removing all page-specific state from the session hash)
seems like the right thing to do. I'd like to avoid it if possible,
however, because it means passing more information through URLs and having
to secu
orry about performance later. Much later. Clean
code tends to lend itself to better performance in the long run anyway,
because it's easier to optimise serious performance problems away.
Can't really disagree with that. Clean code is 100x easier to work on
later.
Shane.
.
BEGIN failed--compilation aborted at /home/httpd/perl/test.pl line 12.
Any hints, Thank you very much.
Steven.
End of code:
1;
Every module has to return a true value at the end of it you could
probably do 1000; at the end, but 1 is convention.
Thanks,
Shane.
]- I'm not sure but I think phttpd is included in RH6.2
Wow..., you're right. What a trip. Okay, I'm going to grab the srpm
for RH's site, and extract it into a tarball. It'll be on my anonymous
ftp under the pub/matofali directory if anyone's interested.
Thanks,
Shane.
(Thanks BTW
(people.redhat.com/zab/). It's faster
than khttpd, and it runs in userland.
Thanks,
Shane.
Shane,
I noticed that all the phhttpd pages have disappeared. What's up?
Hmm.., you are right. Well..., Zach doesn't work for redhat anymore.
I don't have a copy of the latest source..., well, I do
.
So if you are, drop me a note.
Thanks,
Shane.
*Update* I just got an email reply to Zach (man that was like 5
minutes..., very cool), anyhow. He said that they pulled a bunch of
his stuff, but he's getting together backup stuff. It will likely be
on zabbo.net in a couple days. If anyone
clients
their dishing out to simultaneoulsy.
Thanks,
Shane.
as well, and can dish out to more
clients simultaneously. However, I think that apache will incorporate
a lot of the stuff used in Static accel's soon..., so the gap will be
small. But this is very OT..., we're dynamic remember! :-)
Thanks,
Shane.
On Mon, May 15, 2000 at 12:49:12PM -0700, Ask Bjoern
hould look into isolating a lot of this
stuff into modules. I'm sure your sub's are shared quite frequently
between many scripts..., well, there is no need to suck up all that
extra memory, just pull that into your own module set.
Thanks,
Shane.
The rule is... NO GLOBALS! :-) Of course, every ru
s make Nazi designers out of the
best of us..., we allow our sense of design to get in the way of our
sense of algorithms.)
Allright, well, I'm done ranting about languages, sorry to bring you
along for the trip :-).
Thanks,
Shane.
(Let me make a quick note: I had two good professors. Dr. Kir
language when
writing stuff in c/c++... mostly because mixing the two can be really
messy sometimes. (Not when writing an app from scratch, but
supporting a legacy c app. Including c++ in there makes things
nutty.)
Thanks Gunther,
Shane.
..., that is something
interesting to check up on. I think it's mostly that us mod_perl
programmers have been oftly busy :-). Lord knows I have.
Shane.
with the caching)
Thanks,
Shane.
On Fri, May 05, 2000 at 03:24:40PM +0100, lists wrote:
I am having a tricky problem with a mod_perl backend and a vanilla proxying
front end
I have set up:
Apache 1.3.9 + Mod_perl 1.23 + Embperl 1.2.1 as a back-end server
Apache 1.3.9 + mod_proxy as a front-end
nd of
more universally applicable anyway.., the reading is a "specific
case".
Thanks,
Shane.
) in the states,
and would greatly alleviate your problem. But if you're running
pre6..., downgrade, quick! :-)
Later,
Shane.
On Tue, May 02, 2000 at 09:34:45AM -0300, FEITO Nazareno wrote:
Hi, wassup ppl...
I have a little problem, when I start up my apache 1.3.12 with
mod_perl.1.23, it seem
of developers working on it. Four that I know of for
sure, two of which have already done a huge body of work on this
module.
Thanks,
Shane.
On Sat, Apr 29, 2000 at 12:35:39AM -0400, Greg Stark wrote:
A few lessons on this arena:
1) Move your pictures to another server *even if you're
here would be no reason to contemplate another
package. (Clearly HUGE personal bias here)
Thanks,
Shane.
BTW: As Mike Hall brought up, they wanted to kill it because there is
no maintainer for mod_proxy. There are a lot of people
working on it right now (Graham and Sam..., Grahams cleaning up the
cod
eally quickly.
It's at: people.redhat.com/zab/ , or they'll probably pull that down
at some point in the future since he doesn't work there anymore, drop
me an email since Zach no longer works for RH. Its just a lightning
speed HTTPD static accelerator.
Thanks,
Shane.
you back it up with a real reason. Like
it's too slow, or it sucks up too much memory. Or developement time
is significantly impacted.
Maybe I'm just in a bad mood..., but this isn't the kind of thing that
should be on the list.
Thanks,
Shane.
recommendation cut because I'm in a Nazi-ish
resources
for other programs.
Thanks,
Shane.
On Thu, Apr 27, 2000 at 04:35:26PM +0100, Matt Sergeant wrote:
I'm behind a 64k leased line here (net access is *extremely* expensive
here in the UK) and I was thinking, a proxy front end is probably really
not necessary for me. Worst case scenario: I
tiny (500k, maybe smaller) processes feeding
these clients. I posted a URL that shows you how to config it with
modrewrite..., check it out, it was a couple days ago. Or just search
the mod_perl list for mod_proxy.
Later,
Shane.
On Thu, Apr 27, 2000 at 01:09:51PM -0300, FEITO Nazareno wrote
mented on every platform, so either poll(), or select would take
it's place in these scenarios... still more efficient than having a
"heavy" mod perl enabled server sending data to 28.8k client)
Anyhow... thanks Doug,
Shane.
(Man, you've got a good memory... that was over two months ago I
brought up the GC)
I should note, there have been lots of "tweaks" along the way, but
nothing essentially different in concept)
Thanks,
Shane.
-Justin
must have a couple of mysql connections open, so you are
probably right..., he is partially CPU bound, but also io bound, so
his 8 processes was probably dead on. I didn't think about that for
some reason... I guess I have a one track CPU bound mind :-).
Thanks,
Shane.
omething to consider) But,
as Perrin noted, if you have some scripts that query TONS of data, and
others relatively small, the 2:1 ratio might make sense, but no matter
what 1:1 will always produce the most overall efficiency in the
"everythings local scenario".
Okay, these are my thoughts, what do you think?
Shane.
r speaking of is probably the coolest
thing about the JServ engine..., with a little tweaking mod_proxy
could give us that..., but a lot of it's sort of patched up if you
know what I mean at the moment)
Thanks,
Shane.
Les Mikesell
[EMAIL PROTECTED]
about mod_ssl
though - I think it has to patch the Apache source. I'm almost certain
this is covered in one of the INSTALL.foo documents.
Just install the SSL patch first, and then do what Matt said and
everything should work fine. I have a similar config over here.
Thanks,
Shane.
raid they might not go into enough
depth on these exact issues. Not only that, but these are also very
kernel related too..., you have to understand how both pieces fit
together, and frankly I couldn't answer that, and I don't know a
person alive that could :-). (I'm sure there are some, but who?
On Tue, Apr 18, 2000 at 02:07:24AM -0400, Jeff Stuart wrote:
I understand that. :) And that was something that I had to learn myself.
:) It's a BAD thing when suddenly your httpd process takes up 100 MB. :)
It's just that it sounded like Shane was saying that his httpds were
starting OUT
sonable size?
That's the behaviour I thought that would happen, but I was thinking
the value would be retained through the stack (clearly my error).
(Okay, so sue me it would call somememory hog more than 20 times, I'm
just trying to clear up something :-)
Thanks,
Shane.
interested in doing this. You don't
have to know a lot of perl internals, but you would have to understand
the c code in mod_perl fairly well.)
Or... do both! :).
Thanks,
Shane.
Later,
Gunther
__
Gunther Birznieks ([EMAIL PROTEC
:-). I haven't tested that second one, but based on what I know
about how perl works... it should prove... interesting.
Thanks,
Shane.
- Perrin
Try that, and you will truely find out how memory inefficient modperl
is :-). I haven't tested that second one, but based on what I know
about how perl works... it should prove... interesting.
Thanks,
Shane.
Quick note about this: You'll have to hit the same process, so you
might have to
You're right. I am mistaken :-(. Just tested it, and it was
something silly in an old script I had lying around that I thought was
a bug... my mistake. (Note to self: Test all examples before
posting... or you look like an idiot :-) )
Sorry,
Shane.
I think you're mistaken. Try the following
me. Hmm... I guess it's time to pick apache 2.0 stuff and do some
tinkering! :) As far as the present problem... I'm not all that
concerned about it. It actually falls outside of the area of my
responsibilities at our site..., I'm thinking for the other people in
the community mostly.
Thanks!
Shane
- Perrin
ogether a slower approach than queing because of the context
switching type overhead. Not to mention the I/O issue of this...
yikes! makes my head spin.
Thanks,
Shane.
Les Mikesell
[EMAIL PROTECTED]
Actually it's a problem for mod_perl too..., but it's not
nearly as large of a problem than for the design I had in mind.
Congrats Stas... good thinking.
Thanks,
Shane.
(DOSlike isn't fair though! :. Though I see your point... efficiency
was the key element to what I was thinking, but I
peration
of the two components seems like it should be done, but there must be
a reason why no one has done it yet... I'm afraid this reason would be
the apache module API doesn't lend itself to this.
Well, thanks to everyone in advance for their thoughts/comments...
Shane Nay.
rse
of execution. That hash will be checked after running the program and
delete all the appropriate SV's, AV's, HV's, etc.
Just wanted to get your opinion since you've all been down this road,
and suggest something that may be cool, or have zero merit :).
Shane.
59 matches
Mail list logo
