LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Listing/Stopping Running Services (https://www.linuxquestions.org/questions/slackware-14/listing-stopping-running-services-82139/)

mooreted 08-15-2003 12:10 AM

Listing/Stopping Running Services
 
Sorry if this is too noobie of a question but I have been searching for hours and can't find the answer. I'm still pretty lost in Slackware.

In Mandrake, if I wanted to find out what services are running and turn services off so they wont start on boot, I used the Mandrake Control Center. In Slack I can't even figure out how to list the running services, much less turn them off. I thought "ps -aux" listed everything that's running but it doesn't show running services like: arts, shorewall, nfs... etc.

Could someone please take a minute and point me in the right direction?

Thanks,
Ted.

contrasutra 08-15-2003 12:43 AM

All the service and startup scripts are located in:

/etc/rc.d/


If you dont want the service to start at boot, just make that script not executable (chmod -x [filename])


ps -aux will list your running services though. Most end in a "d" (for daemon).

mooreted 08-15-2003 10:07 AM

Thank you for the reply. Slack is kind of different. In Mandrake you had rc3.d, rc4.d and so on. You just comment out the services you don't want running at whatever run-level the service ran. I tried using the instructions for stopping services in my Linux administration book but the instruction won't work for Slack. I'll keep studying though.

Have a good day,
Ted.

yocompia 08-15-2003 11:28 AM

another way of doing the same thing that contra explained is to do the following:

1) if you want to see what services are listening on given ports, use "$socklist" or "$netstat -l"

2) to get rid of these services, i just go through the various scripts in /etc/rc.d/ that start and stop the respective services; if you want to not have httpd (or any of the other daemons) run on startup, then go through the scripts rc.0, rc.K, rc.M, rc.S, and rc.inet2 and comment out the lines where those services are mentioned; also remember to go through /etc/inetd.conf to shutdown services like finger, auth, etc.

3) check that no services are listening by using commands in 1)

mooreted 08-15-2003 03:02 PM

Thanks everyone. I printed out your pointers and will go through them when I get home from lunch.

Appreciate it,
Ted.

Finlay 08-15-2003 05:57 PM

ps -A
make sure it is a CAP A

than just the 'kill...' command

mooreted 08-16-2003 07:40 PM

I have gone back to Mandrake. Tired of trying to fix Slackware.

Thanks for all the help,
Ted.

Amir 09-14-2003 12:30 AM

how do you make linux start a service at startup?? I would like my linux computer to load vncserver :1 and :2 at startup, but i don't know how :(

Any help would be greatly appreciated!

g00$e 09-14-2003 10:46 AM

Quote:

Originally posted by mooreted
I have gone back to Mandrake. Tired of trying to fix Slackware.

Thanks for all the help,
Ted.

Trying to fix Slackware? There is nothing broke in it.

What your are doing under the 'Mandrake Control Center' is using a GUI interface to manipulate scripts and configuration files. Since you have no idea where these files are and how they interact with each other you require a GUI.

Some do not wish to use a GUI or have a greater desire to understand how their OS works.

To suggest that Slackware is broken is crap.

nuzzy 09-14-2003 12:11 PM

ps -ef | sort | more will sort it out for you...

MandrakeDave 09-17-2003 12:15 PM

Quote:

Originally posted by contrasutra
All the service and startup scripts are located in:

/etc/rc.d/


If you dont want the service to start at boot, just make that script not executable (chmod -x [filename])

How do you make it "executable" again if you want the service to start at boot again?

g00$e 09-17-2003 01:08 PM

checkout 'man chmod' or Alphabetical Directory of Linux Commands under chmod.

Short answer is:

chmod 755 /etc/rc.d/rc.httpd

loadedmind 08-20-2004 08:30 AM

Mandrake???
 
Ok, since I'm a hardcore Slacker, I have to call a foul. Mere MENTION of Mandrake requires a quick disembowelment! Keep in mind, the true power of linux is still yielded at the command line. I tried Mandrake when I first started with linux way back when. Even at first glance I hated it. GUI configs were buggy and no real control over your own environment unless you went to the command line which is where Slackware comes in. To truly understand linux, I honestly believe you need to put yourself in the shoes of the creator. It's really not that hard to comprehend once you start to recognize certain patterns in the obvious logic that is Slackware. I really must say - the more I use Slackware, the more I appreciate it over the other distributions, truly.

Mephisto 08-20-2004 08:42 AM

Quote:

Originally posted by mooreted
I have gone back to Mandrake. Tired of trying to fix Slackware.

Thanks for all the help,
Ted.

There are those who like to do things for themselves and those who like to have things done for them. If you prefer the latter then you are better off in Mandrake. Don't get me wrong, I think Mandrake is a fine distro and does it's job well. It just has a different philosophy. Slackware is very low level for administration, if this does not suit you then you probably will never like it. But Slackware does not need "fixing" it needs administration.

wakeras 08-20-2004 09:10 AM

quote:
Originally posted by mooreted
I have gone back to Mandrake. Tired of trying to fix Slackware.

Thanks for all the help,
Ted.

_-----------------------------------------------------------------------------------------_

hi.....don't worry, it just a normal process of learning linux. Ppl will go forth and back again to various distro until they stop and think. Which distro teach them someting. For me, itys Slackware. Once you know how Slackware works, it will become easier everyday.


All times are GMT -5. The time now is 03:46 PM.