The Perfect Setup - Fedora Core 5 (64-bit) - Page 6

Want to support HowtoForge? Become a subscriber!
 
Submitted by falko (Contact Author) (Forums) on Tue, 2006-04-11 21:36. ::

11 ProFTPd

ISPConfig has better support for proftpd than vsftpd, so let's remove vsftpd and install proftpd:

yum remove vsftpd
yum install proftpd
chkconfig --levels 235 proftpd on
/etc/init.d/proftpd start


12 Webalizer

To install webalizer, just run

yum install webalizer


13 Synchronize The System Clock

If you want to have the system clock synchronized with an NTP server do the following:

yum install ntp
chkconfig --levels 235 ntpd on
ntpdate 0.pool.ntp.org
/etc/init.d/ntpd start


14 Install Some Perl Modules

ISPConfig comes with SpamAssassin which needs a few Perl modules to work. We install the required Perl modules with a single command:

yum install perl-HTML-Parser perl-DBI perl-Net-DNS perl-Digest-SHA1


15 The End

The configuration of the server is now finished, and if you wish you can now install ISPConfig on it.


15.1 A Note On SuExec

If you want to run CGI scripts under suExec, you should specify /var/www as the home directory for websites created by ISPConfig as Fedora's suExec is compiled with /var/www as Doc_Root. Run

/usr/sbin/suexec -V

and the output should look like this:

To select /var/www as the home directory for websites during the installation of ISPConfig do the following: When you are asked for the installation mode, select the expert mode.

Later during the installation you are asked if the default directory /home/www should be the directory where ISPConfig will create websites in. Answer n and enter /var/www as the home directory for websites.


16 Links


Please do not use the comment function to ask for help! If you need help, please use our forum.
Comments will be published after administrator approval.
Submitted by Anonymous (not registered) on Mon, 2006-06-26 15:40.
Hello, After frustrating with other "all-in-one" guides, I had just about given up but my drive to get it done directed me to this little gem and now I have my complete FC5 system just the way I wanted on a VMWare machine. This basically allowed me to have a carbon copy of my production server. If I could have found this a few days ago I would have been done so much sooner, but I am still very pleased with the end result. Sincerely, Very happy reader/developer Matt
Submitted by Anonymous (not registered) on Sun, 2006-06-25 17:01.

Dude!

Thanks so much for the "disabling sulinux" tip. I was killing myself trying to get viewvc or trac setup as CGI's behind httpd. I disabled sulinux, and suddenly, everything worked as advertised!

Howtos like this help clarify the process for everyone. Choice is good, and a proven baseline is even better.

-Ted Husted.

 

 

Submitted by Anonymous (not registered) on Mon, 2006-04-17 00:27.

Thankfully I read your fedora core 4 walkthrough and actually attempted it but wanted to use fc 5 instead. You didn't mention here though that this os needs the /etc/pam.d/ftp file created just like in fc 4 so for those users that would like their clients to have ftp access do the following. Excellent walkthrough by the way, this software is very impressive!!!

Some users reported that they were not able to login with system users so you might have to do the following steps:

Create the file /etc/pam.d/ftp with the following content:

#%PAM-1.0
auth required pam_unix.so nullok
account required pam_unix.so
session required pam_unix.so

Restart proftpd afterwards:

/etc/init.d/proftpd restart

Submitted by Anonymous (not registered) on Tue, 2006-04-18 20:48.

(this is my third try.. It it doesn't work, then someone needs to post a how-to on posting comments here since this interface is buggy.)

The proftpd RPM should include /etc/pam.d/proftpd which, following the fedora/redhat methodology, would use system-auth. If you don't have it, hunt around for it (I would post it here, but it seems to not like the posting of the pam.d/proftpd code).

In regards to the how-to, there are a couple of things that don't seem to click correctly:

1. Installing bind-chroot (step 7) will automatically set up the chroot'ed environment. There is no need to make the symbolic links by hand.

2. Why install additional software, as in Step 5, when you can just do it during the install process (that's what I did)?

3. Why the preference towards webalizer? It hasn't been updated in *ages* (2001, I believe) and there are other (better) applications out there now (ie: awstats).

4. In step 9.1, it is stated that "dovecot uses Maildir format (not mbox)", but that is incorrect. The beauty of dovecot is that it supports both Maildir and mbox formats equally. (we use dovecot here with mbox)

I have to agree with you completely regarding SELinux. :) And, with all of that aside, this how-to is an excellent article! Nice work!

Submitted by tommytomato (registered user) on Tue, 2006-10-03 03:58.

Is this for 64bit FC5 only ? or can it been installed on a 32bit system ?

 TT