[mythtv-users] mysqld & mythbackend will not start automatically on restart

[R. G. Newbury]

On 10/02/2012 05:47 AM, Mike Perkins wrote:
> On 01/10/12 23:34, R KANNAN wrote:
>>> Date: Sun, 30 Sep 2012 20:25:26 -0500
>>> From: Bill Meek <keemllib at gmail.com>
>>> To: mythtv-users at mythtv.org
>>> Subject: Re: [mythtv-users] mysqld & mythbackend will not start
>>> automatically on restart
>>> Message-ID: <5068F106.4010205 at gmail.com>
>>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>>>
>>> On 09/30/2012 07:34 PM, R KANNAN wrote:
>>> ...
>>> > Now I find that mysqld & mythbackend do not start up automatically on
>>> boot.
>>>> If I do it manually they seem to be running fine. Is there some setting
>>> in
>>>> Mythbuntu control center that got unset?
>>>>
>>>> Any help is appreciated.
>>>
>>> Hi;
>>>
>>> Are you starting them manually with:
>>>
>>> sudo start mysql and sudo start mythtv-backend?
>>>
>>
>> No. I just started them with 'mysqld &' and 'mythtv-backend >
>> /var/log/mythtv/mythbackend.log'
>>
>> When I tried to start them as service, it did not work.
>>
>> /usr/bin/service: 127: /usr/bin/service: stop: not found
>> /usr/bin/service: 128: exec: start: not found
>> myth-backend: unrecognized service
>>
> Syntax! check your /etc/init.d directory for the exact name of the
> service: I imagine you will find that it is 'mythtv-backend', which is
> not what you have described immediately above.
>

And the full command line would be:  service mysql start (or possibly 
service mysqd start, depending on the name of the script in 
/etc/init.d/) and service mythtv-backend start

Fedora has a program chkconfig which can show and set the startup status 
of all of the services handled through /etc/init.d. I have no idea if it 
exists in Mythbuntu. But try 'chkconfig --list' to see the services 
being run.

Use 'chkconfig mysql on' to tell the system to start mysql on bootup. 
Similarly with chkconfig mythtv-backend on. (And 'off' to kill things 
you do not need to run. The list may be looonnng.)

There are fine-grain possibilities with the --levels switch to turn on 
things only when booted into certain operating system levels. Normally 
*everything* is only set 'on' when operating in a graphical level.

Note that the usual "... and the demands are all going to change 
tomorrow so f...ing stay awake!' applies here. None of this is 
meaningful if you are using systemd.


Geoff













--