Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
starting apache in Redhat 7.2
- Thread starter zoomforce
- Start date
If you have Nautilus you can click on "System Settings" then "Service Configuration". In the window, scroll down to httpd then check the box under "Start at Boot". In the upper part of the window you will also see that you can Start, Stop or Restart the service you have hilighted. Do the same for all the services you want to start at boot up.
- Thread starter
- #4
- Thread starter
- #5
)- Thread starter
- #8
- Thread starter
- #9
- Thread starter
- #10
Hi,
Mandrake is based on Redhat so, for rpm installed stuff, they mostly start the same way. When you install a binary (pre-compiled) redhat rpm of apache it puts a sysv init script called 'httpd' into /etc/rc.d/init.d and that accepts arguments of 'start', 'stop', 'restart', etc. In the first few lines of the script is a comment entry something like this :
# chkconfig: 345 20 80
(actual may be different for httpd)
This indicates the default runlevels and start and stop priorties. When you install via rpm the install script would do a :
# /sbin/chkconfig --add httpd
That reads those defaults so, out of the box, a redhat apache rpm should automatically start when the system reaches the stated run-levels. If you want to change the 'start' runlevels you'd do (as root) :
# /sbin/chkconfig --level 345 httpd on
(example to turn on at runlevels 3,4 & 5)
To stop /start without changing runlevels you'd call the script manually. For example (as root) :
# /etc/rc.d/init.d/httpd restart
So, unless you especially want to build from source or need a newer version than redhat has (e.g. to try Apache 2.0 beta), I generally recommend installing from a rpm built for you particular version of linux rather than from tar.gz files. The latest redhat one is --> ftp://rpmfind.net/linux/redhat/updates/7.2/en/os/i386/apache-1.3.22-2.i386.rpm .
Just download that somewhere, change directory to the same place then do as root:
# rpm -Uvh apache-*.rpm
(and assuming no dependency errors.....)
# /etc/rc.d/init.d/httpd start
The rpm install script should have set it to autostart as described above. It seems kind of odd if you had to set it manually - it shouldn't be necessary unless you changed the defaults.
Regards
Mandrake is based on Redhat so, for rpm installed stuff, they mostly start the same way. When you install a binary (pre-compiled) redhat rpm of apache it puts a sysv init script called 'httpd' into /etc/rc.d/init.d and that accepts arguments of 'start', 'stop', 'restart', etc. In the first few lines of the script is a comment entry something like this :
# chkconfig: 345 20 80
(actual may be different for httpd)
This indicates the default runlevels and start and stop priorties. When you install via rpm the install script would do a :
# /sbin/chkconfig --add httpd
That reads those defaults so, out of the box, a redhat apache rpm should automatically start when the system reaches the stated run-levels. If you want to change the 'start' runlevels you'd do (as root) :
# /sbin/chkconfig --level 345 httpd on
(example to turn on at runlevels 3,4 & 5)
To stop /start without changing runlevels you'd call the script manually. For example (as root) :
# /etc/rc.d/init.d/httpd restart
So, unless you especially want to build from source or need a newer version than redhat has (e.g. to try Apache 2.0 beta), I generally recommend installing from a rpm built for you particular version of linux rather than from tar.gz files. The latest redhat one is --> ftp://rpmfind.net/linux/redhat/updates/7.2/en/os/i386/apache-1.3.22-2.i386.rpm .
Just download that somewhere, change directory to the same place then do as root:
# rpm -Uvh apache-*.rpm
(and assuming no dependency errors.....)
# /etc/rc.d/init.d/httpd start
The rpm install script should have set it to autostart as described above. It seems kind of odd if you had to set it manually - it shouldn't be necessary unless you changed the defaults.
Regards
- Thread starter
- #12
I do - but don't use it. It'll drive ya nuts. If ya wanna play with it. Make a backup copy of httpd.conf so you can get back to the real world. It's also not a bad idea to make a backup of sendmail.mc. This is the file you edit to configure sendmail and is used to make sendmail.cf, the config file sendmail reads on startup. I like to use a text editor so I can edit stuff these configuration scripts don't handle. They also want to put a lot of lines of blank space and have stuff aranged so it's hard to find. As long as you have your backups, what the heck - go for it. It could make life easier. If ya blew it and tested them out without a safety net, let me know and I will send you copies.
- Thread starter
- #14
lol
i tried that webmin but forgetaboutit. way to much info, all i want is to run a few virutal websites and get the email to work... i know how to set up name based virtual in http.conf file, now for sendmail. I gotta go get a POP program now right? i set up my dns to point mx records at my ip, so now i just need to know how to get the mail from that spool dumb file.
i tried that webmin but forgetaboutit. way to much info, all i want is to run a few virutal websites and get the email to work... i know how to set up name based virtual in http.conf file, now for sendmail. I gotta go get a POP program now right? i set up my dns to point mx records at my ip, so now i just need to know how to get the mail from that spool dumb file.
- Thread starter
- #16
hey i learned a few things in redhat and switched back to mandrake, mostly cause i had hardware issue sin redhat for some reason. I just did three reinstalls today trying to get the right mix of modules and i think its right. Im just gonna go get sendmail off the sendmail website and install it. You have been great, i think the only thing i need to figure out now is the whole how to get email picked up, and then how to divide it between the differnt virtual accounts.
also, sometimes my cdrom works, sometimes it doesnt? do i have to mount it everytime or something?
also, sometimes my cdrom works, sometimes it doesnt? do i have to mount it everytime or something?
Guest_imported
New member
- Jan 1, 1970
- 0
Help...I'm very new at this. I'm manually partitioning my system, but I can't figure something out. It seems that RedHat 7.2 documentation, Compaq Proliant docs, and various user docs encourage ceating the html document root in /home. But for some reason, when I install Apache, it defaults (and doesn't give the option to change this in the REd Hat distribution) to /var. Earlier releases of Red hat and new releases of ColdFusion also encourage installation in /var. I'm at a crossroads. Please offer advice. I also want to mention that I need to enable non-anonymous ftp access for a few users. thanks for any help
Hi,
If you don't like the defaults that redhat set just change the DocumentRoot directive in /etc/httpd/conf/httpd.conf to point to somewhere different. Did you read this stuff --> .
For anon ftp on redhat, you can either configure wu-ftpd to permit that (via /etc/ftpaccess config file) or you can install the anonftp package (ftp://rpmfind.net/linux/redhat/7.2/en/os/i386/RedHat/RPMS/anonftp-4.0-9.i386.rpm) as long as its just for read-only access.
Hope this helps
If you don't like the defaults that redhat set just change the DocumentRoot directive in /etc/httpd/conf/httpd.conf to point to somewhere different. Did you read this stuff --> .
For anon ftp on redhat, you can either configure wu-ftpd to permit that (via /etc/ftpaccess config file) or you can install the anonftp package (ftp://rpmfind.net/linux/redhat/7.2/en/os/i386/RedHat/RPMS/anonftp-4.0-9.i386.rpm) as long as its just for read-only access.
Hope this helps
- Status
Similar threads
- Locked
- Question