I'm a tad bit (read: extremely) new to linux. I'm attempting to setup a semi decent webserver that I hope to someday put on the net (for now, local lan will have to do)

I'd like information on how dameon processes are started/handled.


More general/specific definition: httpd is currently set to automatically start with the comp. I'd like to know how to change that (remove httpd), or add other processes.

I'm using Slack 10.1, default kernel, for the record.

Thanks for any help provided to the poor n00b.

httpd is the web server (doesn't matter what program you are using)
do not remove httpd by any means

since you are using slackware 10.1, then your httpd is apache 2.0
this is the best you can get in a web server, it will blow the pants off of anything else out there.

you need to read a whole lot before you start messing w/ such things as servers/daemons on your linux system

check out The Linux Documentation Project

and start with reading the Linux Users Guide, then read a whole bunch of Howtos and the Linux Network Admins Guide. (save this for last!!)

All the initialization scripts are in /etc/rc.d/
There you've a mix of them, some are run-level scripts and other are services scripts, like rc.httpd rc.sshd
A "graphical" front-end for selecting which services to run on startup is pkgtool. Run pkgtool goto Setup and there select Services.
If you want to do it manually, just make the script not executable by typing: chmod -x /etc/rc.d/rc.httpd (or other scritpt, BE CAREFULL to not set run level scrtips, usually those with just a letter or number, to not executable).

Thank you.

And, for the record, for a reason which no doubt illudes me, After a fresh/full install of Slack10.1, I have apache 1.3.11. Not apache 2.0.

(and, one item i forgot, I was trying to end the mysql dameon... for a no doubt good reason, it would keep ending as soon as I got to login prompt (missing file I beleive, can't recall specifics but will no doubt be something I'll come back for sooner or later)


Thanks for the help y'all

Hi TL1moss, the problem with mysql ending itself at boot is that by default the databases for it aren't created. To solve this read inside the file /etc/rc.d/rc.mysqld where you can find instructions to create them.