[mythtv-users] Suse Slave Startup issue

[Jon]

On Feb 8, 2008, at 1:06 AM, Graham Smith wrote:

> On Fri, 8 Feb 2008, Jon wrote:
>> Okay, just installed OpenSUSE 10.3, and installed myth 0.21.2 using
>> YaST. I got it all configured as a slave, and everything seems to be
>> working, but I can't seem to configure it to startup the backend at
>> boot time.
>>
>> I can manually start the service by running:
>>> sudo /sbin/service mythbackend start
>>
>> and I've ran (as root)
>>
>> #chkconfig mythbackend 35
>
> Incorrect - please use insserv
>>
>> which apparently is the syntax that SUSE likes (according to the man)
>> When I do chconfig -l, it shows me that it should start on levels 3
>> and 5. I've also tried 345 to no avail.
>>
>> mythslave1:~ # chkconfig -l mythbackend
>> mythbackend               0:off  1:off  2:off  3:on   4:off  5:on
>> 6:off
>>
>> It appears to me that this should startup at boot time, but it is
>> not. What might I be missing?
>>
>
> You have basically 3 options to get mythbackend running at bootup.
>
> a) use the command  'insserv mythbackend'
> 	See 'man insserv' for more details
>
> b) use Yast --> System --> System Services
> 	I normally use "Expert Mode"
>
> c) Use inittab instead - this ensures the backend restarts after it  
> crashes
>
> 	edit /etc/inittab and add in the following lines at the end of the  
> file
>
> # Mythbackend
> my:345:respawn:/usr/bin/mythbackend --logfile /var/log/mythtv/ 
> mythbackend.log
>
> You need to use the command 'telinit q' to get init to re-examine
> the /etc/inittab file after modifying it.

Okay, so I went into yast, and it appears that mythbackend should be  
starting on runlevles 3 and 5. (I presume it reads chkconfig  
settings?) Still doesn't start on bootup.