[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Handling the new Apache chroot
- To: ports_(_at_)_openbsd_(_dot_)_org
- Subject: Handling the new Apache chroot
- From: "C. Bensend" <benny_(_at_)_bennyvision_(_dot_)_com>
- Date: Tue, 5 Nov 2002 19:20:11 -0600
So, I'm getting adventurous, and I'm working on a port
of Nagios. First question - anyone working on one already? I
didn't see anything in the list archives.
Second question - how are you folks handling the new
Apache chroot? For those of you that aren't familiar with it,
Nagios is a network monitoring system with a web interface. The
main daemon runs by itself, and a number of CGI's are used to
present the web interface and manipulate the running daemon.
With the Apache chroot, I guess I have the option of
either building everything statically or copying libs into a
/usr/lib directory within the chroot. I would like to keep Apache
in secure mode, if possible - the developers did it for a reason,
and I trust them. I know the '-u' flag can be used to solve my
problem, but as I said, the chroot is there for a reason.
The main daemon builds statically, with no problem. If
I choose to build the CGI's statically, I'm running into problems.
If I build the CGI's dynamically, I'll need copies of everything
from libc to libpng to libgd. I don't think this is desirable,
Thoughts/suggestions, anyone? Henning?
There's always time for Cheerios...
Visit your host, monkey.org