Here's the dilemna,

I'm running OpenSuse 10.0 x86_64

I have MythTV installed and [mythbackend] is listed in YaST under system\services/runlevel.

mythbackend shows runlevel 35 and is set to run automatically on startup.

It is not starting however.

I get this error "/etc/init.d/mythbackend start returned 6 (program is not configured)" when I try to start the (daemon?)

mythbackend is listed in /etc/init.d/mythbackend

I chmod a+x mythbackend
I chmod 666 mythbackend
I chkconfig --runlevel 35 mythbackend on

Nothing works.

Yes, the program works if I type mythbackend from the terminal/command line.

HELP!

You may have misinterpreted something you read: mythbackend shows runlevel 35 . There are only 6 runlevels. This probably should read: mythbackend shows runlevel 3,5, meaning runlevels 3 and 5.

chkconfig --runlevel 35 mythbackend on' would fail because there is no such thing as runlevel 35. Try the chkconfig command again, this way:
chkconfig --runlevel 3 mythbackend on
chkconfig --runlevel 5 mythbackend on

If I understand you correctly,
You're saying I need to run chkconfig twice (2x. Once for runlevel 3 and again for runlevel 5?

So why does runlevel in YaST show 3 and 5?

ok I looked at the init.d/mythbackend script and one of the targets was off by one directory. I fixed the directory structure, and now Mythbackend launches on bootup.

New problem - My configuration file is not allowing me to see my settings/tv/tv guide etc..

What is the difference between these two commands?

#:mythbackend
#:/etc/init.d/mythbackend start

Do both launch the program from the same location? I don't think so, but I have to ask.

Have a look at the file /etc/init.d/mythbackend. It's only a script file, and typically would have a bit of checking before starting a program, neat shutdown and restart options, etc.

Yea, I've looked at that already and I need to figure out the difference between the two previous commands to launch mythbackend because:

#:mythbackend (works)
#:/etc/init.d/mythbackend start (works but the config isn't correct) so if I can figure out where

#:mythbackend is being called from, I can figure out where the correct config file is.

is #:mythbackend called from /usr/bin/mythbackend ??