View Single Post
  #4   (View Single Post)  
Old 10th July 2009
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 7,984
Default

Quote:
Originally Posted by badguy View Post
...i assume i have the built in apache running bcos when i do a lynx localhost i can see "it worked"
Correct.
Quote:
...i also installed php using # pkg_add php4-core-4.3.8.tgz (that was all i did. not sure if i have to do more)
php4-core-4.3.8 ??? Are you absolutely sure? That version was for OpenBSD 3.4, which was released in 2003 and has not been supported since November 2004. (By the way, the last release of OpenBSD to have php4 in it was 4.3, which is no longer supported, either. The most recent release is 4.5; 4.6 will be released on or about November 1. Only the most recent release and its immediate antecedent are supported.)
Quote:
...i don know how to check if i have php running so I cant say for now that it is properly installed.
You do not have an operational PHP system, as additional steps are required to integrate it into the web server. When you installed this ancient package, you should have seen the echo'ed message from within this script on your console. This script (link below) was part of the packaging of php4-core for OpenBSD-3.4, back in 2003:

http://www.openbsd.org/cgi-bin/cvsweb/~checkout~/ports/www/php4/core/pkg/Attic/INSTALL?rev=1.4;content-type=text%2Fplain;hideattic=0
Quote:
what is Apache default directory for www files, &
Which configuration files will be useful to troubleshoot?
The built-in Apache is chrooted. It was chrooted, even back when your version of the OS was released. The OpenBSD FAQ discusses this in FAQ 10.16. Of course, it is discussing the most recent -release... which is years beyond what you are running. I mentioned this FAQ to you, above. It also describes the directory structure used by the built in webserver, /var/www. Please, read it. More than once.

If you wish to become a successful and happy OpenBSD user:
  1. Run a supported system. No one can really help you, or will even want to help you, with such an antiquated OS. Not only is it very different from what everyone else is using, so that they cannot replicate your environment without a great deal of effort ..... there have been hundreds of thousands of patches and fixes and improvements applied in the years since 3.4-release. Including many security fixes. If this platform gets exposed to the Internet in any way, it is ... unsafe. Really. If it were just an internal-network router and had no services running... it might be considered robust enough. But certainly not when serving dynamic web applications. And never when exposed to the Internet. Even with nothing on it, if it gets compromised, it becomes a vector in to other platforms on your private network.
  2. Read the FAQ. Please. And do so repeatedly. Over and over. It is the handbook; much more than simply a FAQ, it is the primary "how to" collection for the OpenBSD community, written by the developers. It covers almost all aspects of general operation that admins will be interested in. Note that since the FAQ is for the most recent release, so most of it won't apply to your antiquated platform. (It is possible to grab a historical FAQ from CVS, as I've done for the php4 post-install message script... but you're better off installing and using a modern release. The changes to the OS since 3.4 have been vast.)
  3. Avoid "how to" documents you find in the wild. While some might be wonderful, most will lead you astray; they are often written by new users, who while proud of some accomplishment usually are not technical writers, do not explain what and why they make particular choices for commands and configuration information, nor what the implications are for environments that do not exactly match their own particular configurations may be. More people have gotten into trouble blindly following "how to" documents than you might imagine.

Last edited by jggimi; 10th July 2009 at 04:02 AM.
Reply With Quote