Hana & Sarah’s blog

By default, Redhat & Fedora comes with smrsh activated.
In order to forward an email to a handler program, the handler program must be in /etc/smrsh (I am not sure if link is sufficient)

Refer to /etc/mail/sendmail.mc
Below line means that smrsh is used.

FEATURE(`smrsh',`/usr/sbin/smrsh')dnl

/etc/aliases

localemail:  |/etc/smrsh/mailhandler.sh

run newaliases to update the aliases db.

Also the /etc/smrsh/mailhandler.sh should read the input from the STDIN.

If you want to activate sendmail (SMTP) Server…

/etc/mail/sendmail.mc file

uncomment by adding dnl in front of below line

DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl
</lang>
So it becomes
<pre lang="none">
dnl DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl

(more…)

When you have problem with uploading large file to your PHP application, try to change below options in /etc/php.ini


;php.ini
max_execution_time = 0 ; unlimited
max_input_time = 0
memory_limit = 8M

; Maximum allowed size for uploaded files.
upload_max_filesize = 240M ; Set this value to max upload file size that you want


Also, if you use Apache 2.0 (Redhat) check if httpd.conf or /etc/httpd/cond.d/php.conf contains below option


LimitRequestBody 0 ; unit is bytes and 0 means unlimited.


I have my php already compiled and working perfectly, but I found that pfpro module was not compiled in.

I needed pfpro module, but I didn’t want to mess up with whole php recompilation…

First download linux SDK kit from verisign website. You need to create an account with verisign first.

Unzip/untar into /var/www/pfpro

So I decided with creating self-contained pfpro module.

1. make a directory and cd into it.
$mkdir mydir
$cd mydir

9. check with phpinfo()


NOTE: When you actaully code the php, you need to set environment variable n the php file before connecting to verisign. Of course you must provide the correct path.
putenv(”PFPRO_CERT_PATH=/var/www/pfpro/certs”);

Please refer to README.SELF-CONTAINED-EXTENSIONS from the original source distribution

—-from the readme file—-

Just to show you how easy it is to create a self-contained
extension, we will convert an embedded extension into a
self-contained one. Install PHP and execute the following
commands.

$ mkdir /tmp/newext
$ cd /tmp/newext

You now have an empty directory. We will copy the files from
the mysql extension:

$ cp -rp php-4.0.X/ext/mysql/* .

It is time to finish the module. Run:

$ phpize

You can now ship the contents of the directory - the extension
can live completely on its own.

The user instructions boil down to

$ ./configure \
[--with-php-config=/path/to/php-config] \
[--with-mysql=MYSQL-DIR]
$ make install

The MySQL module will either use the embedded MySQL client
library or the MySQL installation in MYSQL-DIR.