From: Benjamin Podszun <ben@galactic-tales.de>
To: azarah@gentoo.org
Cc: Hasse Hagen Johansen <hhj@musikcheck.dk>,
Gentoo-Dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] Performance once again..
Date: 13 Apr 2003 17:46:19 +0200 [thread overview]
Message-ID: <1050248779.1280.54.camel@blafasel> (raw)
In-Reply-To: <1050190221.4224.67.camel@nosferatu.lan>
[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]
I applied it and had no problems so far with it. But I changed a lot of
other things as well (disabled lots of non-critical apache-modules,
tried to tweak the php.ini etc.), so I'm not sure if the patch solved my
problem or if it's solved at.
On Sun, 2003-04-13 at 01:30, Martin Schlemmer wrote:
> On Sun, 2003-04-13 at 00:55, Benjamin Podszun wrote:
> > Attached.
> >
> > On Sun, 2003-04-13 at 00:25, Martin Schlemmer wrote:
> > > On Sat, 2003-04-12 at 22:44, Benjamin Podszun wrote:
> > > > jay:~/apache-1.3.27/debian/patches# ls
> > > > ab_overzealous_connections mime_type_fix
> > > > apxs_assumes_dso mod_bandwidth_paths
> > > > apxs_wrong_prefix phf_dot_log
> > > > custom_response_segfaults
> > > > regex_must_conform_to_posix_for_LFS_to_work
> > > > dbm_part_2_the_revenge server_subversioning
> > > > debian_config_layout suexec_combined
> > > > debian_ps_is_brutal suexec_of_death
> > > > debian_requires_fPIC thetarget_unquoted
> > > > hurd_compile_fix_for_upstream usr_bin_perl_owns_you
> > > >
> > > > Uhm.. That's not really helpful for me... Any other ideas?
> > > >
> > >
> > > Could you attach patches:
> > >
> > > ab_overzealous_connections
> > > mod_bandwidth_paths
> > > suexec_combined
> > > suexec_of_death
> > > usr_bin_perl_owns_you
> > >
> > > Although I do not think the last are related.
>
> Mind applying the ab_overzealous_connections patch, and
> see if that makes a difference ? If you have issues
> to get it applied, let me know (although I am going to
> bed now =)
>
>
> Regards,
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-04-13 15:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-12 19:09 [gentoo-dev] Performance once again Benjamin Podszun
2003-04-12 19:13 ` Jon Portnoy
2003-04-12 19:44 ` Benjamin Podszun
2003-04-12 19:54 ` Jon Portnoy
2003-04-12 20:24 ` Brian Jackson
2003-04-12 20:32 ` Benjamin Podszun
2003-04-12 20:38 ` Hasse Hagen Johansen
2003-04-12 20:44 ` Benjamin Podszun
2003-04-12 22:25 ` Martin Schlemmer
2003-04-12 22:55 ` Benjamin Podszun
2003-04-12 23:30 ` Martin Schlemmer
2003-04-13 15:46 ` Benjamin Podszun [this message]
2003-04-13 18:11 ` Martin Schlemmer
2003-04-13 21:20 ` Benjamin Podszun
2003-04-12 20:45 ` Robin H.Johnson
2003-04-12 21:46 ` Benjamin Podszun
2003-04-12 22:05 ` leahcim
2003-04-12 22:09 ` Robin H.Johnson
2003-04-12 22:17 ` Brad Laue
2003-04-12 22:35 ` Benjamin Podszun
[not found] ` <1050187146.3931.12.camel@nexus6.musikcheck.dk>
2003-04-12 22:51 ` Benjamin Podszun
2003-04-13 0:22 ` Brad Laue
2003-04-12 22:32 ` Terje Kvernes
2003-04-14 8:51 ` Václav Hůla
2003-04-14 9:03 ` Benjamin Podszun
2003-04-14 9:33 ` Paul de Vrieze
2003-04-14 12:30 ` Dar-Klajid
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1050248779.1280.54.camel@blafasel \
--to=ben@galactic-tales.de \
--cc=azarah@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=hhj@musikcheck.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox