From: Russell Coker <russell@coker.com.au>
To: Tom <tom@lemuria.org>
Cc: selinux@tycho.nsa.gov
Subject: Re: PHP and other CGI stuff
Date: Mon, 20 Jan 2003 17:45:13 +0100 [thread overview]
Message-ID: <200301201745.13703.russell@coker.com.au> (raw)
In-Reply-To: <20030120162504.D30542@lemuria.org>
On Mon, 20 Jan 2003 16:25, Tom wrote:
> > Due to this I was unable to determine a better solution than to have a
> > seperate instance of Apache for every separate PHP domain. This consumes
> > extra resources, but generally you don't have that many PHP customers...
>
> Well, we have about 1000. So running seperate Apaches is definitely not
> an option.
True.
> Ok, then I'm starting one now. After some experimentation I think I've
> found a way. But what is the performance impacts of domains and rules?
They take up non-pagable kernel memory, which reduces the performance of the
machine.
> I would create 10 domains/types and about 700 rules per hosted site
> (this is after macro expansion, of course).
> What would the memory and performance impact of 10000 new types and 700000
> rules be? If it just means another 512 MB of memory for the machine, that's
> not a problem.
It sounds like you are multiplying the size of the policy-db by a factor of
30. If you have 30 times the RAM of the smaller SE Linux machines (given
your comment about 512M it sounds like you do) then it should be OK.
There's no reason to expect this to give any problems apart from RAM usage and
load time (both of which should scale linearly to the size of the policy).
Try it, if it fails then file some appropriate bug reports.
> > I think that the entire way that Apache operates should be reviewed in
> > light of the way things are currently working in SE Linux policy and the
> > usage of typical systems. Many things have changed since the Apache
> > policy was written, it's a bit of a dinosaur.
>
> I posted an updated one in october, though it retains much of the old
> stuff, it should be much newer. See my other posting earlier today.
Which posting?
--
http://www.coker.com.au/selinux/ My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/ Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/ My home page
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2003-01-20 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-20 13:11 PHP and other CGI stuff Tom
2003-01-20 14:05 ` Russell Coker
2003-01-20 15:25 ` Tom
2003-01-20 16:45 ` Russell Coker [this message]
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=200301201745.13703.russell@coker.com.au \
--to=russell@coker.com.au \
--cc=selinux@tycho.nsa.gov \
--cc=tom@lemuria.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.