[SOLVED] Slackware-current need a double reboot command to really reboot the system
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
changes if you are on a specific runlevel I find shutdown to be more consistent.
BTW: what you are doing with
Code:
# reboot && reboot
it's evil, read the reboot manual for clarification.
I have slackware-current and reboot it's working as expected, Maybe you messed up with rc scripts ?
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.
Since long ago there were discussions why children rc's should be called
1) with the "sh" prefix such as "sh /etc/rc.d/rc.wicd start"
2) with a "." prefix
Has there been any conlusions apart from the negligible performance gain by 2)?
I believe 2) easily messes things up, while 1) just stores one piece of information twice in two places (the command line in the caller and the shebang of the callee).
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
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
Code:
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?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.