[Pianod] Minor Bug Report and a Question

[Perette Barella]

[Bringing this back onto the list to request help from folks who know Linux admin better]

Bruce,

Thanks for running the tests.  It’s a race condition we’re seeing.  The audio settings fail validation (by attempting to open the specified device) when pianod starts up at boot time.  It works later, either by invoking pianod after the system is up or creating the room manually, because the device has become available and can be opened by then.

This also explains why ROOM CREATE with audio parameters fails: if the audio parameters are deemed invalid, the command gets aborted before the room is created.  (I can see where having startscript responses go somewhere for review would be helpful with things like this.  I’ll look into that.)

Based on this, I believe something else is needed in the “After=“ line in of the pianod.service, to wait for the audio subsystems to be fully up and available.  Do we have any experienced Linux or systemd folks that can shed some light on this?  A transcript of Bruce’s file is below.

Thanks all,

Perette



> --------- pianod.service ----------
> [Unit]
> Description=Pianod Music Daemon.
> After=syslog.target alsa-util
> 
> [Service]
> ExecStart=/usr/local/bin/pianod -n bruce -d /home/bruce/.config -c /home/bruce/monoamp/MonoAmp/pianod_html
> Restart=always
> 
> [Install]
> WantedBy=default.target





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.deviousfish.com/pipermail/pianod-deviousfish.com/attachments/20160729/67bdfff8/attachment-0002.htm>