[SOLVED] Slackware-current need a double reboot command to really reboot the system
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Thank you for all suggestions, but It was my mistake with default system rc scripts. Sorry! In this case I modified rc.samba, a month ago, changing rc.samba script to run samba4 AD. I don't searched what the default system is doing in reboot process to start and stop samba3, I just believed that using samba4 rc script as rc.samba could simplify, wrong! Because I'm using samba4 for serving an Active Directory, I had to do it in other way. The resolution was revert the samba4 rc script to rc.samba4, then starting rc.samba4 at boot in rc.local, and stop in rc.local_shutdown.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
You only need to do the sh shell_prog_name if shell_prog_name is not executable; if it is, just type the name and optional argument. You (c|w)ould
chmod 755 /etc/rc.d/rc.wicd
and problem solved.
What the dot-space prefix does is to execute a shell program in the current environment; the shell does not execute the program in a new PID, it executes in the current PID. What that does is allow you to modify your current environment if desired -- any environment variables set in a dot-space execution will remain set in the current environment.
Just for grins, the "rc" comes from DEC days (like the PDP line), means "run command." The boyos at Bell Labs built Unix on DEC PDP's and, gee, wonder why the used rc, eh?