-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hey Seth and Lorne (and others!),
If you're using a newer Debian version you can use systemd to start the Rivendell daemons. The Open Source Radio project (of which I am a part) has successfully implemented systemd "service" files for each of caed, ripcd, and rdcatchd. The examples at https://github.com/opensourceradio/ram/tree/master/etc/systemd/system require you to specify the username under which to run the daemons. After copying the unit files to /etc/systemd/system, enable the services with: sudo systemctl enable caed@rivendell.service sudo systemctl enable ripcd@rivendell.service sudo systemctl enable rdcatchd@rivendell.service And then enable the rivendell target as the default with: sudo systemctl set-default rivendell.target After setting all this up you bring up the daemons with: sudo systemctl isolate rivendell.target You can stop the daemons with something like: sudo systemctl isolate multi-user.target or sudo systemctl isolate graphical.target Edit the unit file rivendell.target to specify whether you're depending on the multi-user target (no GUI apps expected to run on this system) or the graphical target (all the GUI apps installed and used on this system). Run the command: sudo systemctl daemon-reload after making changes to any of the unit files in /etc/systemd/system. I may have forgotten a step or two, but I'd be interested to hear others' experience with these. Carry on! ~David Klann Open Source Radio WDRT, Viroqua, WI, USA On 02/24/2016 10:39 PM, Lorne Tyndale wrote: > Hi Seth, > > If it is Debian that still supports sysvinit, then the command you're > looking for is: > > sudo update-rc.d rivendell defaults > > Assuming your rivendell startup script is already copied to /etc/init.d/ > > If you're running with systemd, then you may have to ask the systemd > folks. The last time I tried to use Debian with systemd, I had an > extremely bad experience that left me saying nasty things for days. It > did not take me long to reformat and reinstall something with sysvinit > that I knew worked. I have not looked back since. > > >> I have compiled Rivendell on the raspberry pi version of Debian. Now every >> time the computer is rebooted the daemons aren´t starting. I have to do >> sudo /etc/init.d/rivendell start. I know there is a way to automatically >> have them start on bootup, but it has been a long time since I have done >> it. What is the proper procedure and command? Thanks! >> >> -- >> Seth Stevenson<hr>_______________________________________________ >> Rivendell-dev mailing list >> Rivendell-dev@lists.rivendellaudio.org >> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev > _______________________________________________ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlbPB2kACgkQZtxZ++32cNjNnAEAmLY989l5NmW2Auaxmjrex470 YngVoXXXzt96uD/+Ue0A/iTqlvehlEk11yG/ZLkTk7bwIvTVf9JjYugsRsQ71JkZ =AbTP -----END PGP SIGNATURE----- _______________________________________________ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
