Here's a bit more of what's happening: dragonfly ~ # /etc/init.d/mythbackend status * status: stopped dragonfly ~ # /etc/init.d/mythbackend start * Starting myth backend ... [ ok ]dragonfly ~ # /etc/init.d/mysql status * status: started dragonfly ~ # /etc/init.d/mythbackend status * status: started dragonfly ~ # ps aux | grep my root 14160 0.0 0.0 1476 464 pts/0 R+ 13:18 0:00 grep my dragonfly ~ #
I am sure that yesterday I would see either a mythbackend or mysql process at this point: On 4/25/05, Mark Knecht <[EMAIL PROTECTED]> wrote: > Hi, > My kernel didn't call up the right stuff for X-Video support so I > rebuilt it. After rebooting mysql no longer starts and hence > mythbackend doesn't run. Is there anything about mysql that would be > effected by building a new version of an existing kernel? I did start > completely over with the kernel. (make clean/make mrpoper/etc.) Or is > this just a coincidence and something else is the likely culprit? > > Thanks, > Mark > -- [email protected] mailing list
