linux

Documentation http://spamassassin.apache.org/

1. Install spamassassin on the server

# yum install spamassassin

2. Install required perl CPAN modules

# perl -MCPAN -e shell
cpan> install Digest::SHA1
cpan> install HTML::Parser
cpan> Install option perl modules...

2. Edit spamassassin configuration in /etc/mail/spamassassin/local.cf .

When starting httpd service, the following error message appears and the service failed to start.

# service httpd start
Starting httpd: (98)Address already in use: make_sock: could not bind to address 0.0.0.0:443
no listening sockets available, shutting down
Unable to open logs

The error message means that when httpd tried to start, some other process was already listening on 443. To see what other processes are using port 443, the following two commands may be used:

Mass virtual hosting using mod_vhost_alias or mod_rewrite module simplifies pattern-based virtual hosting. However, there is a major problem if your virtual host application makes use of the DOCUMENT_ROOT environment variable. According to the Apache documentation, the mod_vhost_alias does NOT correctly sets the DOCUMENT_ROOT variable and hence pontentially break PHP web applications that makes use of this environment variable.

Secure Sockets Layer (SSL) provides secure connections by allowing two applications connecting over a network connection to authenticate the other's identity and by encrypting the data exchanged between the applications. A server identity is verified by three components: Private Key, Digital Certificate and Trusted Certificate Authority.

1. download FreeVPS Kernel, and FreeVPS Tools for RH_EL4 from the following location:

http://www.freevps.com/download/rpms/RH_EL4/

Download both single and SMP versions:

kernel-freevps-1.5-1.i686.rpm
kernel-freevps-smp-1.5-1.i686.rpm
freevps-tools-1.4-2.i386.rpm

*Note: A sigle processor version is necessary to satisfy dependency requirement for freevps-tools.

2. Install the new kernel packages

Platform setup:
Fedora Core 3
Apache 2.0.52-3
SELinux enabled.

Apache configuration is setup correctly with right permissions, we the server throws a 403 error.

The log entry in the /etc/httpd/logs/error_log:
"[error] [client xx.xx.xxx.xxx] (13)Permission denied: access to / denied"

The issue is well known but the fixes only apply to Fedora 3, such as :
"Use : chcon -R -t httpd_sys_content_t "

or

"deactive SELinux at the command line or GUI".

or

Installing apache2, php5 and mod_php5 shouldn't be too hard, but it took me nearly 2 hours trying to get this installed on SuSE v11.1. The later SuSE 11.4 works just fine by installing the required modules with zypper, but the SuSE 11.1 wouldn't work right out of the box.

Here are the steps required to get the mod_php5 to work on SuSE 11.1. The v11.1 installs php5-5.2.6 where v11.4 installs php5-5.3.5. We had to downgrade the php due to package dependency issues.

1. Add official OpenSuSE repository

I have recently acquainted with SuSE linux, and I looked for package manager that I can use to manage software packages. I've started out with yast, but it wasn't very good at providing resolutions to dependency problems. Someone recommended zypper over yast and yast2, so here I am sharing my experience with zypper.

What is Zypper?

If your date.timezone is not properly set, your web application will not display your local time correctly.  The default date.timezone will be set to the server time zone. If you (or your company) is located in different time zone from the server, you may have to override the value in your PHP application.. The date.timezone can be set at the system level, PHP level or application level.

Linux Server Timezone

To set the date.timezone value globally within the server, you'll have to follow the steps outlined below.

On a production server, you will definitely want to turn off errors from displaying on the screen due to security and usability reasons but what do you do when you're on a development machine trying to debug a malfunctioning PHP script? PHP gives a programmer an ability to control logging of errors, and the types of errors to be displayed. You may enable PHP error display in one of two ways.

1. You may turn on error display at the script level when a server level error display is turned off.