I realize your specific situation was answered by kikinovak, but since you were confused, the below is to try an un-muddy the waters (hopefully I don't make it worse).
For anything that isn't already built into Slackware (like kikinovak showed you with vsftpd), the general consensus is to add any additional commands to your rc.local (if you add it to rc.M, it can cause issues with system upgrades or Slackware patches if there's changes made to rc.M). It is generally preferred that any new program installed on the system that needs to start at bootup (commonly called a daemon) should have it's own rc.
program_name in /etc/rc.d that supports the start/stop/restart commands (most of these types of programs on SBo will have the needed rc.
program_name file included). With these, it's preferred to call them in rc.local after checking to see if they're executable (this makes it follow the Slackware way of only needing to make the file executable to have it run, and if it isn't executable, you won't get an error because of it):
Code:
# Start program_name
if [ -x /etc/rc.d/rc.program_name ]; then
/etc/rc.d/rc.program_name start
fi
If the program doesn't have an rc.
program_name, you can either insert the command directly in rc.local, or you can create your own rc.
program_name file. The below is a simple example, depending on the startup/shutdown procedure of your program, it can be more complicated (if the program just needs to be run to start, you might just be able to replace
program_name with the name of the program and save the file -- if it is more complicated, it might take a bit more editing).
Code:
#!/bin/sh
# Start/stop/restart program_name
program_name_start() {
echo "Starting program_name daemon: "
/usr/bin/program_name
}
program_name_stop() {
killall program_name 2> /dev/null
}
program_name_restart() {
program_name_stop
program_name_start
}
case "$1" in
'start')
program_name_start
;;
'stop')
program_name_stop
;;
'restart')
program_name_restart
;;
*)
echo "usage $0 start|stop|restart"
esac
As for correctly shutting down the process, unless it is called somewhere else (like the rc.shutdown_local that Hangaber mentioned), Slackware will just send a SIGNAL code to close the program (I think it's actually two codes, with the second one being more severe to force it to close if the first one didn't do it -- but I can't remember which ones). If you want the program to actually shut down properly (if your program has that option), you can input the command in rc.shutdown_local just like rc.local file, but change it to the command to shut down the program (if you made your own rc.
program_name, I would suggest putting the shutdown command in there, replacing the killall command under the stop), then, in the rc.shutdown_local, you could just add the if check to see if the rc.
program_name is executable and then just add
/etc/rc.d/rc.program_name stop, which will properly shut down the program rather than have Slackware manually killing it.
