Greetings, One more caveat to add to my mystery.
I compiled 3.4.1 from git hub source on Ubuntu 18.04 and my scripts work with RN macro. So does this obviously mean something is being treated differently on Centos 7. They run on Centos from the terminal. But not with the RN macro from rivendell. I had pretty much made up my mind to move to Centos so that the future would be easier regarding updates and the like, but console integration is major so I have to figure this out before making my decision. Any ideas why the rml would work so differently between the distros? I know that "printf" has some variations between distros and versions but I wouldn't think that has any bearing since the scripts run from the terminal on both. Tim Camp WZEW-FM On Sat, Oct 24, 2020 at 6:45 PM Tim Camp <[email protected]> wrote: > OK > RN sh -c usr/bin/6M! does not work > RN sh -c "/usr/bin/6M"! doesn't work.... someone had suggested that after > -c the command had to be in quotes > RN sh -c 6M! does not work > All of the above commands work from terminal both as rd or as root > no luck from rmlsend > > Tim Camp > WZEW-FM > > > > > On Sat, Oct 24, 2020 at 6:10 PM Fred Gleason <[email protected]> > wrote: > >> On Oct 24, 2020, at 18:56, Tim Camp <[email protected]> wrote: >> >> The Scripts that we mostly run are simple, we avoid echo because of >> its various problems across distros because of escape character troubles. >> an example of our usage >> RN 6M! >> 6M is a script to mute channel six on the console >> scripts are, where string is the command to the audio console. >> that script contains >> >> #!/usr/bin/env bash >> printf "/ch/06/mix/on\00\00\00,i\00\00\00\00\00\00" > >> /dev/udp/consoleip/port (you can see why echo when have trouble with >> that) >> >> >> Ah. Bangpath trouble... >> >> This has a similar problem to your earlier example that used STDOUT >> redirection. The first line ("#!/usr/bin/env bash”) is actually an >> instruction *to the shell* to treat this as a shell script. But, since it’s >> being directly invoked as an executable, the shell never gets to see it, >> and the kernel’s exec() call barfs on it. Run it like this: ‘RN sh -c 6M!’ >> and it should work. (You’ll probably need to provide the full path to the >> ‘6M’ script.) >> >> Since this seems to be a common problem, perhaps we should alter the ‘Run >> Script’ [‘RN’] so that it automatically executes everything as ‘sh -c >> <script>’? Or do we want a new RML in addition to ‘RN’ to do this? >> >> Cheers! >> >> >> |---------------------------------------------------------------------| >> | Frederick F. Gleason, Jr. | Chief Developer | >> | | Paravel Systems | >> |---------------------------------------------------------------------| >> | A room without books is like a body without a soul. | >> | | >> | -- Cicero | >> |---------------------------------------------------------------------| >> > > > -- > Tim Camp > Director of Operations/Programming > Dot Com Plus L.L.C. > dba WZEW-FM WNSP-FM > Mobile, Al. > > -- Tim Camp Director of Operations/Programming Dot Com Plus L.L.C. dba WZEW-FM WNSP-FM Mobile, Al.
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
