[SOLVED] unable to stop services with chkconfig or sysv-rc-conf utility for ubuntu
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I will try out bum. Another thing is the link suggests using sysv-rc-conf utility for fine grained control. I am using the same, but I am unable to understand - why is the service started at all, when I have deactivated it in the sysv-rc-conf utility?
Did you deactivate it in all runlevels? Debian at least defaults to all runlevels 2-5 being the same, with the default runlevel set to 2. People coming from Red Hat are used to default multiuser gui being runlevel 5.
Distribution: Debian, Arch Linux, Linux Mint, Ubuntu, Fedora, Suse, Mepis, Redhat, Sayabon, mandrake and android (
NKD if you want this much control... I would suggest Slackware, Gentoo or my favorite Arch Linux...
They allow for more control over boot process.... Tried running Boot Chart and sysv-rc-conf.. I couldn't get the boot times below 23 seconds..... My Windows 7 machine boots in 21 seconds...
Ubuntu, Fedora, Suse etc... Have pre-installed software such as there own management systems and drivers that eat up load time.... With Slackware, Gentoo and Arch Linux you have to load in the specific
driver for the xconf editor to run xserver.. As well as Loading in extra Apps... Minimum would come with either gnome, kde or whatever windows manager you install...
With Arch Linux I can get 15 second boot times... Arch Linux is a lot harder to install, but they have excellent documentation for the install...
I really looking forward to installing Slackware in the near future...
If your spending endless amounts of time trying play with sys-rc-conf... I would suggest Just trying one of the other distro's. But lots of advice from someone in the forums that can tell you the difference between Slackware and Arch Linux. They can maybe give you better insight into setup for Slackware...
My problem is not about trying to reduce the boot time, it is rather a Security issue. I wish to just stop the server from listening on these ports which are open on my system :-
I have tried to disable the services in the runlevel 2-5 using the chkconfig command and I have double checked the runlevel and the services are configured to be off on all the runlevels, using the sysv-rc-conf command.
But when I restart the system, I find the services are still running. The following confirmed the same :-
sudo service smb status
sudo nmap -A 192.168.0.11
sudo netstat -l
Both the commands confirmed the services are very much on. I am confused !
BTW when I stop the services with
sudo service smb stop
the above commands all confirm the port has closed. The problem is the effect is temporary as on successive boots
the services will come up.
Because of Ubuntu is switching services to new "upstart method" from old "rc method", some of them are not configurable by "sysv-rc-conf" or "chkconfig" utilities. To disable that service, find its configuration in "/etc/init/*.conf" file and remove line (or comment with #) with "start" word at the begining. By the way, if you do not want to ever use this services you can just uninstall them.
To disable that service, find its configuration in "/etc/init/*.conf" file and remove line (or comment with #) with "start" word at the begining.
Thanks a lot and I could stop all the services.
I felt it is a bit strange that the sysv-rc-conf and chkconfig are still being made available in the repos of the latest releases ! while the Sys V startup method is being discontinues withe the Upstart scheme of things !