[mythtv-commits] Ticket #2918: mythshutdown and mythbackend both use same setting for WakeupTimeFormat

MythTV mythtv at cvs.mythtv.org
Sun Jan 14 03:12:02 UTC 2007


#2918: mythshutdown and mythbackend both use same setting for WakeupTimeFormat
--------------------------------------+-------------------------------------
 Reporter:  adrian.wilkins at gmail.com  |       Owner:  ijr    
     Type:  defect                    |      Status:  new    
 Priority:  minor                     |   Milestone:  unknown
Component:  mythtv                    |     Version:  head   
 Severity:  medium                    |  
--------------------------------------+-------------------------------------
 The recommended program for the backend to set wakeup time is
 mythshutdown. The recommended program for setting wakeup time in the NVRAM
 is nvram-wakeup.

 mythshutdown insists on ISO-8601 date format for it's parameter. (yyyy-MM-
 ddThh:mm:ss)

 nvram-wakeup insists on time_t (seconds since epoch)

 Settings appear correct in the relevant dialogs because of hostname
 prevalence. Backend logs reveal that mythbackend is passing time_t to
 mythshutdown --setwakeup however.

 I have worked around this by setting "both" (local and NULL host) settings
 to ISO-8601 and the nvram-wakeup command to

 {{{date -d "`echo $time | sed "s/T/ /"`" +%s | xargs nvram-wakeup -A -s}}}

 (the sed is necessary because GNU date cannot parse ISO-8601 despite being
 able to generate it).

 The fact that you can have perfectly correct settings in the dialogs that
 do not work needs sorting out (perhaps make a second setting for the time
 format, or even just allow the user to define time formats to use with
 tokens like time_1$ time_2$, etc.

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/2918>
MythTV <http://www.mythtv.org/>
MythTV


More information about the mythtv-commits mailing list