After exploring this more thoroughly we found that rdlogmanager does indeed
treat -d differently than it once did. Changing the argument to -d 1 fixes
the issue.

Hopefully someone else using this feature can take note and avoid trouble.


On Thu, Dec 20, 2012 at 2:22 PM, Max Goldstein, Operations Director <
[email protected]> wrote:

> We run a bash script to generate logs, called daily from a cron job. We
> import cart lists from an external scheduler and then merge music (actually
> stations IDs but it's music to rdlogmanager). Relevant lines below; full
> source 
> here<https://github.com/WMFO/Automation-Scheduler/blob/master/generate_log.sh>
> .
>
> /path/to/external/scheduler > `date --date=2days +"%Y_%m_%d.log"`
> /usr/local/bin/rdlogmanager -g -m -s Automation -d 2
>
> Basically we generate a text file with music carts numbers and times two
> days in advance and then import it into Rivendell. This setup has worked
> for years. After upgrading to 2.2.1 over the weekend (not sure what our old
> version was but it might have been 2.1.5), we discovered only the merged
> carts were present in the logs; the externally scheduled carts were not. I
> noticed that the most recent log in rdlogedit was dated a day ahead of the
> most recent log from the external scheduler. All logs from today on (until
> the 22nd, the last one) also have no externally scheduled carts. So one
> possibility is that something changed in rdlogmanager's command line
> argument parsing of -d 2.
>
> Another possibility is that the new schema requires the output format of
> the scheduler to change. Here's a sample:
> 123800XXXXX000000
> 125035XXXXX000200
> 253053XXXXX000400
>  30356XXXXX000600
> 185825XXXXX000800
>
> or in general:
> cart##XXXXXhhddmm
>
> So carts every two minutes.
>
> Any ideas? Any similar issues?
>
> Thanks,
>
> Max Goldstein
> Operations Director
> WMFO Medford
>



-- 
Thanks,

Max Goldstein
Operations Director
WMFO Medford
_______________________________________________
Rivendell-dev mailing list
[email protected]
http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev

Reply via email to