Hello Romain and others,
I've made some significant progress and now have a working git
buildpackage for Arch Linux. Before I'm going to upload it to the Arch
User Repo, I have the following remarks/questions:
1. The logrotate script contains the following postrotate script:
postrotate
for liq in /var/run/liquidsoap/*.pid ; do
if test $liq != '/var/run/liquidsoap/*.pid' ; then
start-stop-daemon --stop --signal USR1 --quiet --pidfile $liq
fi
done
endscript
Although start-stop-daemon is available in the arch repository, it isn't
installed by default. I also didn't find the package installed by
default on an OpenSuse system. How about using the more generic way of
accomplishing the same?
postrotate
for liq in /var/run/liquidsoap/*.pid ; do
if test $liq != '/var/run/liquidsoap/*.pid' ; then
kill -s USR1 `cat $liq`
fi
done
endscript
It is still somewhat buggy. Imagine a situation where a liquidsoap
daemon closes and the pidfile isn't being removed. I need to dive in
this somewhat more to give a better solution to let the logrotate script
whether the process is running before killing. Also, it would be nice if
liquidsoap removes te PIDFile after closing.
2. When is the pidfile created in the daemonizing process? When i try to
use my own sample systemd service, i get the following messages:
systemd[1]: Starting Liquidsoap service for channel foo...
systemd[1]: PID file /run/liquidsoap/foo.pid not readable (yet?) after
start.
systemd[1]: [email protected]: Supervising process 2564 which is
not our child. We'll most likely not notice when it exits.
systemd[1]: Started Liquidsoap service for channel foo.
When Systemd tries to read the pidfile, it doesn't exist yet. This might
be because the pidfile is created quite late in the daemonizing process.
This is probably not only a problem with Systemd, but also with the
start-stop-daemon init.d implementation Debian uses, which also needs
the PIDFile to exist as quick as possible.
May be there is a way to make the PID creation more fast or create it
earlier in the process?
Thanks,
Leonard
On 4/12/2013 21:50, Romain Beauxis wrote:
> Hi Leonard,
>
> 2013/4/12 Leonard de Ruijter <[email protected]>:
>> I have plans to create a custom Arch Linux (AUR) package for Liquidsoap.
>
> Thank you for this!
>
>> There are two packages in the aur now:
>> - Liquidsoap, version 1.00, quite outdated, unmaintained
>> - Liquidsoap-full, up to date, though buggy and without the needed
>> dependency references in the buildfile.
>
> Using the -full tarball is an easier option if you do not wish to also
> provide packages for the related bindings. It is a perfectly find
> approach if there's no traction in your OS for those, which is most
> likely the case (unfortunately).
>
>> I'm thinking about creating liquidsoap-git, which automatically builds
>> Liquidsoap from the most recent git branch. I also feel like adding a
>> SystemD service ([email protected]) which allows starting and stopping
>> Liquidsoap from systemd. I have the following questions though:
>> 1. Is there an up to date list of dependencies which aren't managed by
>> liquidsoap and should be installed from the distribution?
>
> It depends what you need. You can have a look at our documentation:
> http://liquidsoap.fm/doc-svn/build.html
> Or the Debian package source:
>
> http://anonscm.debian.org/gitweb/?p=pkg-ocaml-maint/packages/liquidsoap.git;a=blob;f=debian/control;h=1dca72a39b59d5380b33c4f38ac1a732a3adb044;hb=HEAD
> Or the homebrew build file:
>
> https://github.com/drfill/homebrew-liquidsoap/blob/master/Formula/liquidsoap.rb#L140
> At the end of the day, though, you will probably end-up compiling this
> list manually, because package names and availability may different
> from one distribution to another.. Also, the two packages above are
> packaging each module in -full as a seperate package, which may not be
> your case.
>
>> 2. It's difficult to distinguish between dependencies needed for
>> compiling and runtime dependencies. I assume that most of the
>> dependencies needed for compiling Liquidsoap, such as library sources,
>> aren't needed for running Liquidsoap itself. How to make this distinction?
>
> If you are compiling to a native binary, then runtime dependencies are:
> * Libraries required for the binary to run, which can be listed using ldd
> * Camomile runtime files
> * wget and festival (optional)
>
> I think that's it.
>
> We have never experienced with systemd configuration, let us know if
> that works good and perhaps share that, we'd be super happy to include
> it in our next release..
>
> Romain
>
> ------------------------------------------------------------------------------
> Precog is a next-generation analytics platform capable of advanced
> analytics on semi-structured data. The platform includes APIs for building
> apps and a phenomenal toolset for data science. Developers can use
> our toolset for easy data analysis & visualization. Get a free account!
> http://www2.precog.com/precogplatform/slashdotnewsletter
> _______________________________________________
> Savonet-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/savonet-users
>
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users
