Good Day, all!
I'm a big fan of FreeBSD and OpenBSD and would like to see if I can get Cacti to run under these, but I have a couple of questions:
a) is the linux compatibility required under FreeBSD to run Cacti?
b) does Cacti run under Apache 2.x ?
c) The libphp4.so seems to link closely with Apache 1.xx is there a way to use the static php4 enstead?
OK, I guess there were three questions.
Dan McGinn-Combs (the other Dan)
Apache/PHP and FreeBSD
Moderators: Developers, Moderators
Wow, easy ones for a change.
a) Linux compat is only required if you want to use the included scripts to return info on the local box because (to my knowledge) *BSD doesn't have all the /proc/* stuff that the included scripts use. For polling other devices, BSD is fine w/out compat.
b) I haven't tried Apache 2.0 but that's more a question of whether or not PHP will run, not so much Cacti. As I understand it, PHP runs under 2.0 but is much slower than 1.3.x. I'd stick with 1.3.x until 2.x matures a bit more and a PHP that's better optimised for it comes out.
c) I'm not sure what you mean by 'link closely' but you can build PHP statically or as a module. PHP doesn't care which. use --with-apxs to build as a module, --with-apache to build it in statically, or neither to build as a CGI.
Hope this helps.
Rob.
a) Linux compat is only required if you want to use the included scripts to return info on the local box because (to my knowledge) *BSD doesn't have all the /proc/* stuff that the included scripts use. For polling other devices, BSD is fine w/out compat.
b) I haven't tried Apache 2.0 but that's more a question of whether or not PHP will run, not so much Cacti. As I understand it, PHP runs under 2.0 but is much slower than 1.3.x. I'd stick with 1.3.x until 2.x matures a bit more and a PHP that's better optimised for it comes out.
c) I'm not sure what you mean by 'link closely' but you can build PHP statically or as a module. PHP doesn't care which. use --with-apxs to build as a module, --with-apache to build it in statically, or neither to build as a CGI.
Hope this helps.
Rob.
Hmmm... I guess what I meant was that I hadn't seen any method for using the PHP4 .so file available for OpenBSD with Apache2 at all. OK -- figured that one out. Don't use Apache2, stay with Apache1.x.x.robsweet wrote:c) I'm not sure what you mean by 'link closely' but you can build PHP statically or as a module. PHP doesn't care which. use --with-apxs to build as a module, --with-apache to build it in statically, or neither to build as a CGI.McGinn-Combs wrote: c) The libphp4.so seems to link closely with Apache 1.xx is there a way to use the static php4 enstead?
Also, I have found that the PHP build is important (imagine that! ). Installing on OpenBSD, I get a few choices for PHP: with MySQL or with SNMP or with LDAP and often without X11. Sigh -- much simpler to just build my own... particularly since there isn't a static version I've found available for OpenBSD.
But by and large, the package is working on OpenBSD and FreeBSD. I still have to incorporate the SNMP features, but that should be reasonably simple.
thanks for the guidance!
Dan McGinn-Combs
Geac Computers, Inc.
Atlanta
Personally, I prefer to hand-roll my Apache and PHP on any machine that's not Debian Linux (blatant plug). Debian seems to have just about everything available either as a module or statically compiled. Lots 'o packages. I haven't seen any other distro, BSD, or Solaris with so many pre-packaged builds (binaries, modules, whatever) so on anything else, I just roll my own.
My two bits.
Rob.
My two bits.
Rob.
-
- Posts: 35
- Joined: Sat Apr 13, 2002 5:16 pm
- Location: Santa Barbara, CA
Who is online
Users browsing this forum: No registered users and 3 guests