I'm in the process of setting up a Rivendell system at WCFR(AM)
Springfield, VT to do Boston Bruins hockey games. I am dealing with a
Broadcast Tools SRC32 serial remote control, which is not directly
supported by Rivendell, but which can be controlled using "SO" RML
commands.
I wrote Perl scripts to manage the start of a game, going into and out of
local breaks, and returning to normal programming at the end of the game.
The scripts worked perfectly from the command line, but not when called
from Rivendell.
rd.conf is set to run Rivendell as user 'scott'. I do this because it is
easier to debug external scripts if Rivendell is running as the same user
I log in as.
However, what I've just discovered is that the Bruins scripts are failing
because they don't have permissions to access the serial port -- even
though user 'scott' is in the dialout group and does have such
permissions.
That means that at least part of Rivendell must be running as a user other
than 'scott'. 'chmod o+rw /dev/ttyS0' cures the problem.
The obvious question is: what user is it running as? Since the scripts
were working from the command line, 'scott' clearly had permissions to
access the serial port.
I vaguely recall having encountered this problem before. This is RD 2.18
running on Debian 8. There's no SELinux installed, so it can't be anything
like that.
For now, I'm adding 'chmod o+rw /dev/ttyS0' to my startup script, as that
seems to be an effective workaround; but I'd love to understand why the
problem crpped up in the first place.
Rob
--
Я там, где ребята толковые,
Я там, где плакаты "Вперёд",
Где песни рабочие новые
Страна трудовая поёт.
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
