Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 06-08-2024, 06:37 AM   #1
LQ Newbie
Registered: Feb 2023
Location: Paris, France
Distribution: Slackware Linux
Posts: 6

Rep: Reputation: 1
Question Proper way to start SBo daemons at boot ?


After installing a few daemons from SBo (avahi, sshguard, etc), I noticed that they were not started at boot time although the rc scripts are set executable.

Reading again the Configuration Help page, I am not sure what's the proper way to configure the daemons for autostart.

Shall I add them to rc.local or shall I create symlinks for those in rc3.d and rc6.d?

Thank you.
Old 06-08-2024, 07:07 AM   #2
Registered: Mar 2009
Location: Greece,Crete
Distribution: Slackware64-current, Slint
Posts: 729
Blog Entries: 2

Rep: Reputation: 538Reputation: 538Reputation: 538Reputation: 538Reputation: 538Reputation: 538
rc.local and rc.local_shutdown is the best!
#Start avahidaemon
  if [ -x /etc/rc.d/rc.avahidaemon ]; then
  /etc/rc.d/rc.avahidaemon start

 if [ -x /etc/rc.d/rc.avahidnsconfd ]; then
  /etc/rc.d/rc.avahidnsconfd start
# Stop avahidnsconfd
  if [ -x /etc/rc.d/rc.avahidnsconfd ]; then
  /etc/rc.d/rc.avahidnsconfd stop

#Stop avahidaemon
  if [ -x /etc/rc.d/rc.avahidaemon ]; then
  /etc/rc.d/rc.avahidaemon stop
You should read README or README.SBo if exist for every daemon you installed everything you need is discribed

Last edited by rizitis; 06-14-2024 at 06:36 AM. Reason: :D
2 members found this post helpful.
Old 06-08-2024, 07:46 AM   #3
Registered: Jan 2018
Location: 2001:470:c2d0::/56
Distribution: Anything I can interface with
Posts: 107

Rep: Reputation: Disabled
Originally Posted by jcarnat View Post
Shall I add them to rc.local or shall I create symlinks for those in rc3.d and rc6.d?
Pretty much anything that isn't from standard distribution should be added into the rc.local (optionally rc.local_shutdown) file. You can either call the program startup script directly (/etc/rc.d/rc.??? start) or wrap it under a bash decision loop, as rizltis has shown above, if you want to have the same behavior to disable services at boot time by removing the execute bit from the file. This method also works for non rc.??? files: you can directly start programs and daemons via the rc.local files, the same way, by sending them to the background with the "/path/to/program &" syntax.
3 members found this post helpful.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Suitesparse /Cuda SBo, complains about too advanced GCC, although being built with GCC 5 from the same SBo. Lockywolf Slackware 5 04-28-2019 10:17 PM
nvidia-driver SBo The symbolic link '/usr/lib/' does not point to 'tmp/SBo/package-nvidia-driver/usr/lib64/' Gerardo Zamudio Slackware 5 07-30-2017 10:44 PM
Questions for Robby, ponce, or anyone from SBo about SBo submission requirements. ReaperX7 Slackware 4 06-07-2015 11:30 AM
Nvidia-driver.SlackBuild from SBo (or: I am a bad and sloppy SBo maintainer) kingbeowulf Slackware 8 08-31-2012 02:41 AM
proper way to kill unix daemons? genmaicha Linux - General 2 11-18-2009 02:31 PM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 08:25 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration