Ashley,

When you run

/etc/init.d/liquidsoap start

It will look for any files ending in .liq (that's dot liq) in the directory
/etc/liquidsoap

When I look at the default install that I have, the only file in there is
radio.liq.example (note that this file has .example at the end).

So when it tries to start, it can't find any script to start, so liquidsoap
just dies.

Nick

On Wed, Apr 6, 2016 at 9:34 PM, Ashley Bernard <[email protected]>
wrote:

> Thanks for the rc.local trick. It does start my script upon reboot.
> However, I’d love to be able to start and stop scripts without rebooting
> the entire server, especially during this testing phase.
> I’m running debian Jessie, so pretty sure there’s an init.d script that
> just isn’t working for some odd reason
> > On Apr 6, 2016, at 4:38 PM, Lars Kruse <[email protected]> wrote:
> >
> > Hi Ashley,
> >
> >
> > Am Tue, 5 Apr 2016 13:29:38 -0400
> > schrieb Ashley Bernard <[email protected]>:
> >
> >> now it seems when I run /etc/init.d/liquidsoap start I get
> >> Starting liquidsoap channels: radio.liq /etc/init.d/liquidsoap:
> >> 55: /etc/init.d/liquidsoap: start-stop-daemon: not found OK
> >
> > I think, "start-stop-daemon" is debian-specific. Thus maybe you are
> using a
> > non-debian-based distribution? In this case the init script is probably
> not
> > usable for you (out of the box).
> >
> > Maybe the most simple way of starting a process could work for you? In
> this
> > case just put the following line into /etc/rc.local:
> > su -c "liquidsoap -d /etc/liquidsoap/radio.liq" liquidsoap
> > This will get executed during bootup.
> >
> > Then you could start it manually:
> > /etc/rc.local
> > Or stop it:
> > killall liquidsoap
> >
> >
> > If you want to do it properly (instead of the above quick and dirty
> approach)
> > then you should look around for a liquidsoap init script for your
> distribution
> > or for a systemd unit file (if applicable).
> >
> > Cheers,
> > Lars
> >
> > PS: maybe you should file a wishlist bug against the liquidsoap package
> for
> > your distribution. Adding an init script / systemd unit is usually done
> by
> > the maintainer of the packager for your distribution.
> >
> >
> ------------------------------------------------------------------------------
> > _______________________________________________
> > Savonet-users mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/savonet-users
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Savonet-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/savonet-users
>
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial! http://pubads.g.doubleclick.net/
gampad/clk?id=1444514301&iu=/ca-pub-7940484522588532
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users

Reply via email to