<p><br>
On Sep 8, 2011 11:00 PM, "Raymond Wagner" <<a href="mailto:raymond@wagnerrp.com">raymond@wagnerrp.com</a>> wrote:<br>
><br>
> On 9/8/2011 23:33, Jeremy Jones wrote:<br>
> > Great! I copied in the two lines you added, and if I deciphered the<br>
> > code correctly, I should be specifying the --jobid instead of --chanid<br>
> > %CHANID% --starttime %STARTTIME%.<br>
><br>
> Rather, just specify the jobid as a bare argument. The script does not<br>
> accept a --jobid option. Technically, you could backtrace the jobid by<br>
> searching for a job, currently running on that recording, using a<br>
> command with the same binary name as that stored in the database. But<br>
> there is no way you could make it 100% accurate for all scenarios, and<br>
> it's easier to just require the use of %JOBID% for that behavior.<br>
> </p>
<p>Perfect. I made the change using %JOBID% last night. I'm sure my logs will be nice and clean again when I check them tonight.</p>
<p>Thank you for the help.<br></p>
<p>Jeremy </p>