[mythtv-users] 0.27 trying to create a user job script, not starting, remains "queued"

Raymond Wagner raymond at wagnerrp.com
Fri Jun 13 15:44:39 UTC 2014


On 6/12/2014 6:00 PM, R. G. Newbury wrote:
> On 12/06/14 12:57 PM, Hika van den Hoven wrote:
>> Hoi Steven,
>>
>> Thursday, June 12, 2014, 5:41:55 PM, you wrote:
>>
>>> On Wed, Jun 11, 2014 at 4:25 PM, Michael T. Dean
>>> <mtdean at thirdcontact.com> wrote:
>>>> On 06/11/2014 04:23 PM, Michael T. Dean wrote:
>>>>>
>>>>> On 06/11/2014 03:30 PM, Gary Buhrmaster wrote:
>>>>>>
>>>>>> On Wed, Jun 11, 2014 at 7:24 PM, Steven Adeff wrote:
>>>>>>>
>>>>>>> Hello all!
>>>>>>> I'm attempting to create my own user job script, I attempted to 
>>>>>>> run it
>>>>>>> via mythweb, but it sits as "queued" according to the backend 
>>>>>>> status
>>>>>>> page.
>>>>>>> I don't see anything about it in the backend log.
>>>>>>>
>>>>>>> I'm wondering if anyone knows what I've done wrong? or can clue 
>>>>>>> me in
>>>>>>> to what I should start looking for as to why?
>>>>>>> thanks!
>>>>>>
>>>>>> Off the top of my head:
>>>>>>
>>>>>> Did you restart the BE?  It is required if you
>>>>>> update/create jobs via mythweb.
>>>>>>
>>>>>> Did you set your BE to enable user jobs (in
>>>>>> mythtv-setup job queue).
>>>>>>
>>>>>> Does your job queue start/end time allow
>>>>>> running now?
>>>>>
>>>>>
>>>>> And if you want them to be run automatically, there are 3 
>>>>> locations where
>>>>> you must enable (each) jobs.  They must be enabled in the 
>>>>> recording rule, in
>>>>> the recording profile, and on the host.  (These 3 locations allow 
>>>>> you to run
>>>>> jobs on some or all recordings depending on which rule recorded 
>>>>> them, how
>>>>> they were recorded (recording profile), and to run them where you 
>>>>> want
>>>>> (host).
>>>>
>>>>
>>>> Erp, I'm wrong again.
>>>>
>>>> http://www.gossamer-threads.com/lists/mythtv/users/453812#453812
>>>>
>>>> Only automatic transcode jobs need enabled in the recording 
>>>> profile.  (So 2
>>>> locations unless it's an auto transcode job.)
>>
>>> ok, got it to run!
>>> a followup question, when providing the command line to run, what is
>>> the proper way to type the variables so they will be captured properly
>>> by the script?
>>> ie if I'm using a BASH script, if I want to provide the subtitle to
>>> the script, and the subtitle has a colon in it,
>>> "International Friendly: Republic of Ireland vs. Portugal"
>>> would I use
>>> script.sh $SUBTITLE$
>>> or
>>> script.sh "$SUBTITLE$"
>>
>>> to run the script?
>>> thanks!
>>
>>
>> Quote it! Else every space will create a next variable.
>
>
> Better yet, use    /usr/local/bin/script/sh "${SUBTITLE}"
>
> There are some tricky differences between "$SUBTITLE" and 
> "${SUBTITLE}" but it seems that the latter always works when testing 
> the variable (say, inside an 'if [ xx = "${SUBTITLE}" ]; then...' 
> while the bare $SUBTITLE does not always produce the desired result.
>
> The {..} forces the substitution, before the test???? although why 
> that does not happen in the other formulation is unclear to me.
>

Since Steven was referring to variable substitution within the jobqueue, 
and not a shell, he actually wants "%SUBTITLE%".


More information about the mythtv-users mailing list