Hi,
being just in the process of setting up a test machine with Rivendell
3.0.1 to maybe upgrade our station still running 2.5.1 (!), i've just
encountered this problem a few minutes ago.
My workaround so far has been to edit the
/lib/systemd/system/rivendell.service
by adding
User=rduser
Group=rivendell
in the [Service] section of the file.
This way, rivendell services run as my rduser and can see jackd running
as the same user.
There may be adverse effects which i'm not aware of, so i would wait for
more seasoned sysadmins to confirm it's ok to do this before putting
that box on the air.
++
. leo
On 07/19/2019 03:12 PM, Hoggins! wrote:
Hi list,
Upgrading from 2.19.3 to 3.0.1, I have an issue that has occurred
before, but somehow I had managed to get through. Now I'm stuck.
My jackd server runs as unprivileged user (like it normally should), but
Rivendell won't see it and connect to it unless I start a jackd (dummy
driver) instance as root user.
I remember several references of such an issue, stating that a first run
as root is necessary to detect jack and then it can be run as an
unprivileged user. This is not working anymore, and I'm kinda lost here.
Any idea?
Thanks!
Hoggins!
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
