> the answer is the same for any service on suse, go into yast and find > the bit where services are started.
You need to distinguish between enabling a service to be started every boot, or doing this manually after the box has booted. To make a service start each time the box is booted, go into the yast runlevel editor. Activating a service for a runlevel does not start it right there and then though. Incidentally, somewhere around the runlevel editor you can also instantly start and stop a service, which is easy but overkill. Keep in mind that on SuSE, services are in the root path with "rc" prepended, so all you need to type is rcapache2 start and because it's in the path, you get away with rcap<tab> start This by itself doesn't of course cause apache to be startet each boot. (on earlier versions, the service was halled httpd instead of apache2) Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
