frequencydrive

try setting tcp_wrappers=YES in your vsftpd.conf file.

Quote: Does PHP4 come pre installed on the Apache server? No. Apache is separate from PHP. If these weren't installed on your system during the install process then you will have to download a precompiled binary or compile each (apache & PHP) from their sources. Most of the time these are rpms (Red hat Package Manager) that are installed during the install process. To check is these were installed as rpms you can use these two commands: rpm -qa php rpm -qa httpd <-- I believe this is the apache rpm name ?? Apache and PHP are separate entities. They work together but you have to configure each to work with the other. These don't come together. Quote: If it is installed already, it isn't working and I will need some help as to how to get it going. This is a tall order. You can easily find the answers to these questions by reading the apache installation manual here: http://httpd.apache.org/docs-2.0/ and the php installation manual here: http://www.php.net/docs.php If you found it difficult to find these you weren't looking very hard! You simply read the manual and it will explain how to compile and configure them. here is how I configured my PHP: [root@Dragon root] cd /usr/local/src/php [root@Dragon root] ./configure --libdir=/usr/lib --with--apxs2=/usr/local/apache2/bin/apxs --with-mysql=/usr/local/mysql --with-gd --with-zlib --with-jpeg-dir=/usr/lib --with-png-dir=/usr/lib --with-tiff-dir=/usr/lib --with-bz2=/usr/lib --with-config-file-path=/etc/php.d --enable-calendar --with-openssl --with-curl --with-dom --enable-ftp --enable-inline-optimization --enable-force-cgi-redirect --enable-pic -with-pear=/usr/share/pear --enable-bcmath --enable-mcal --with-exif then: [root@Dragon root]make [root@Dragon root]make install You will need to go into the php.ini file and modify it some. You will also need to go into the apache config file httpd.conf and tell it how to interpret dot php extensions by telling it where your php module is. Like I said all this is in the manual. That is how I figured it all out. oh I just reread your latest post: Quote: Edit: I found PHP on my Linux computer already, but it isn't installed/working on the Apache server. If you could just tell me where to put all the files and everything, that would be great. If php isn't working with Apache and you KNOW it is installed on your box then you need to go into the apache configuration file and edit it to tell it were to find your php module that you compiled. If you don't know where it is then just type: find / -name libphp4.so (this is assuming you have php 4 installed) If I type this I get the following: /usr/lib/httpd/modules/libphp4.so This is the shared loadable module that apache will load to handle any php scripts. You need to tell apache where this file is so that it can load it. The relevant section of my httpd.conf that I need to change was: Code: ## Dynamic Shared Object (DSO) Support## To be able to use the functionality of a module which was built as a DSO you# have to place corresponding `LoadModule' lines at this location so the# directives contained in it are actually available _before_ they are used.# Statically compiled modules (those listed by `httpd -l') do not need# to be loaded here.## Example:# LoadModule foo_module modules/mod_foo.soLoadModule php4_module modules/libphp4.so# See the line that starts with LoadModule? You will manually have to add that line to your apache configure file (httpd.conf) so that it knows where to find your libphp4.so file. You will also have to tell apache what extensions you want interpreted as PHP. See the relevant httpd.conf snippet below: Code: ## Filters allow you to process content before it is sent to the client.## To parse .shtml files for server-side includes (SSI):# (You will also need to add "Includes" to the "Options" directive.)#AddType text/html .shtmlAddType application/x-httpd-php .php#AddOutputFilter INCLUDES .shtml See the line that starts with AddType? That is the line that tells apache what kind of files it will interpret as PHP. There is more but you need to read the manual and if you still can't figure it out come back and ask.

Ok well I guess I should have tried this before posting. After adding a new path to my .bash_profile I decided to just logout and log back in again to see if it would see my new/modified path then. So I shutdown X-Windows and logged out. Logged back in and typed echo $PATH and BANG! the new/modified path was shown. That is great! So the lesson learned here is that bash only reads the .bash_profile one time and that is when you first log in to the machine. Any modifications to that file do not get passed on to new terminal sessions/windows that you subsequently open. You have to completely log out and log back in. I am sure there is a way to force BASH to reread it's .bash_profile file but I don't know how. I can't even find it in the O'reilley BASH book. But hey everything is working now so I'm happy.

I have just installed MySQL and I am getting tired of having to type the full path name to start the server manually (/usr/local/mysql/bin/mysqld_safe --user=mysql). I thought I would add this path to my $PATH environment variable. So I typed the following to add this path: Code: PATH=$PATH":/usr/local/mysql/bin" This works great only for the current session. If I move to another x-windows terminal (on the same machine just another window running a terminal) then the $PATH I just created isn't visible to any other terminal. So I thought I will just add this new path to my .bash_profile. Here is what my bash_profile looks like right now after adding /usr/local/mysql/bin to my path. Code: # .bash_profile# Get the aliases and functionsif [ -f ~/.bashrc ]; then . ~/.bashrcfi# User specific environment and startup programsPATH=$PATH:$HOME/binPATH=$PATH:/usr/local/mysql/binBASH_ENV=$HOME/.bashrcUSERNAME="root"export USERNAME BASH_ENV PATH If I close the current window that I am running a terminal in and start a new terminal then you would think bash would read the .bash_profile before starting the shell. Apparently it isn't rereading the .bash_profile or I am not adding the path /usr/local/mysql/bin to my $PATH variable correctly. Does anyone see what I am doing wrong? I am aware of creating an aliase but I don't want to do it that way. I want to know what I am doing wrong here. I want the path /usr/local/mysql/bin to be part of my path whenever I start a terminal. I am tired of typing the full path name everytime I start and stop the MySQL server. Thanks

Quote: Is there a recommended site to learn the sytax? You should buy some books about linux at your nearest bookstore or use Google. You can learn a hell of a lot on the web. I would suggest getting a book like Linux in a Nutshell by O'reilley press. This book is mostly just all the man pages printed out in book form. Still very handy to browse through and see what kind of Linux command are available to you. Also might want to pick up something like Running Linux[/] by O'reilley press also. These two will get your started.

I just did this two days ago. I've put MySQL on four machines, three of them Linux machines (including one laptop) and one windows XP machine. You get MySQL here: http://www.mysql.com/downloads/mysql-4.0.html I picked up the latest production release which is 4.0.16 at 14.6 Megabytes (Standard Linux (x86, libc6). I moved it over to /usr/local and gunzipped it did a tar -xvf on it. That created a mysql-4.0.16-standard-bla bla bla directory. I cd'ed into that directory and read the manual.html document. I would advise you to read this document BEFORE you do anything. If you skip down to section 2.2.11 of the manual.html document titled Installing a MySQL Binary Distribution it shows the following: The basic commands you must execute to install and use a MySQL binary distribution Code: shell> groupadd mysqlshell> useradd -g mysql mysqlshell> cd /usr/localshell> gunzip < /path/to/mysql-VERSION-OS.tar.gz | tar xvf -shell> ln -s full-path-to-mysql-VERSION-OS mysqlshell> cd mysqlshell> scripts/mysql_install_dbshell> chown -R root .shell> chown -R mysql datashell> chgrp -R mysql .shell> bin/mysqld_safe --user=mysql & After you do all this the manual says to change the default password for root. There is no password for root. The default is there is no password. So you want to get that corrected right away. The manual also shows you how to set the root pasword. You can use MySQLAdmin or you can manually enter the password into the GRANT tables. If you know nothing about databases then you BETTER use mysqladmin to do it. Code: /usr/local/mysql/bin/mysqladmin -u root password <password>/usr/local/mysql/bin/mysqladmin -u root -h `hostname` password <password> If mysql is installed on the same machine as you are on then hostname would be localhost. To start the mysql server you invoke the startup script "mysqld_safe" by typing: Code: shell> ./bin/mysqld_safe --user=mysql & To test you server type the following (this can also be found in sect. 2.4.0 of the manual) Code: shell> BINDIR/mysqladmin versionshell> BINDIR/mysqladmin variables BINDIR is the bin directory where mysqladmin resides. On my system I would type: /usr/local/mysql/bin/mysqladmin version which would display the following: Code: mysqladmin Ver 8.14 Distrib 3.23.32, for linux on i586Copyright (C) 2000 MySQL AB & MySQL Finland AB & TCX DataKonsult ABThis software comes with ABSOLUTELY NO WARRANTY. This is free software,and you are welcome to modify and redistribute it under the GPL license.Server version 3.23.32-debugProtocol version 10Connection Localhost via Unix socketTCP port 3306UNIX socket /tmp/mysql.sockUptime: 16 secThreads: 1 Questions: 9 Slow queries: 0Opens: 7 Flush tables: 2 Open tables: 0Queries per second avg: 0.000Memory in use: 132K Max memory used: 16773K I won't show you what variables displays because it is too long beside you can see it all in the manual. THE most important thiing you can do is follow the instructions at the very top. This will get your test and mysql database setup so that you can test and start creating your own databases to play with. Finally to shutdown your server: Code: shell> BINDIR/mysqladmin -u root shutdown

I have a Dell 333Mhz machine that I just upgraded to RH 9 (from 7.2). I can't remember all this EXACTLY but I did have the same problem with Redhat not recognizing my CDROM drive. I have a SCSI I/O system. My hard drive, CDROM drive and CDRW drive are all SCSI. When I installed REDHat 6 originally it had no problem recognizing my cdrom drive. Anyway I put the CD into the drive and get a splash screen. When it tries to install RH 9 I get some error saying it can't find the media. I can't remember the exact error. The message on the screen said something about taking the file bootdisk.img and drvblock.img and create a boot disk with those images. So I took the CD out and put it in one of my other Linux machines. I copied the files /images/bootdisk.img and /images/drvblock.img from the RH 9 installation CD 1 (there are three installation cds. you will find these files on the first CD) right onto the floppy by using the dd command. The first bootable disk contains bootdisk.img and the other floppy contains drvblock.img. I used the following command to create the first floppy from the bootdisk.img file: dd bs=2x80x18b if=/mnt/cdrom/images/bootdisk.img of=/dev/fd0/bootdisk.img Do a man dd to see what "if" and "of" means. bs = block size. A floppy has 18 sectors per track, two heads and 80 cylinders hence, 2x80x18b. 18b specifies 18 sectors of 512 bytes. The "x" means multiply. If you multifply these out you get 1474560 bytes (1.44 Mbytes the size of all floppies). This command issues a single 1474560 byte read request to /dev/fd0 and a single 1474560 byte write request to /mnt/floppy. I assume you mount your floppy under /mnt. When you are done make sure you unmount your floppy DON'T just hit the eject button to take it out because Linux doesn't always write to the device immediately so you may end up ejecting the disk before it actually starts making the disk. When you are done type "umount /mnt/floppy". My system didn't actually start writting to the disk until I typed umount /mnt/floppy. Then the little green light came on for a long time (maybe a minute). I waited till it went out and then ejected the disk. I put it back in the drive on the same computer and mounted it to see if the disk was indeed created. I found four files, boot.msg, initrd.img ldlinux.sys,syslinux.cfg,vmlinuz. Those were containted in the image that was written to the disk. I then unmounted it again and stuck it in the original Dell 333Mhz computer so that I could start the installation process. I still had to create the driver disk so that my Dell system could boot from my cdrom drive. So I used the same dd command to copy the drvblock.img over to another floppy. The exact command I typed was: (make sure you mount the floppy first) dd bs=2x80x18b if=/mnt/cdrom/images/drvblock.img of=/dev/fd0/drvblock.img The floppy drive light came on for about a minute (it seemed like a long time) and then went out. I unmounted the floppy and then remounted it to make sure I REALLY had a driver disk. I found the following files on the disk: modinfo, module.cgz, modules.dep, pcitable, rhdd-6.1. After putting in the first bootable disk to load linux I had to put in the driver disk so that it could find my cdrom drive. I was prompted to do this if I can remember right. Anyway after I put in the driver disk and it loaded the drivers for the CDROM I saw my cdrom light come on. I can remember now if I was prompted to continue or if linux just automatically started booting off the cdrom drive. The installation was normal after having to create those the boot disk and the driver disk. Seems like a lot doesn't it. I went smooth though.