As with the mythfrontend, there can be multiple backends. One backend process is designated as the master backend. This is usually the first backend installed on a system. This backend is responsible for coordinating the activities of the other backends known as slaves. This is especially true for scheduling as the master backend will determine the best distribution of programs across all available tuners. Each backend can have any number of tuners, including zero. Commercial Detection can be distributed across different backends, thereby spreading the load of that process.

There is no requirement for direct user interaction with the backend. The backend can use local HardWare/File Storage or have it mounted from another system. If remotely mounted, network performance should be considered as there will be considerable traffic on the network as recordings are stored and retreived by the backend process.

Contents

Command Line Options

Valid options are:

-h or --help List valid command line parameters
-l or --logfile filename Writes STDERR and STDOUT messages to filename
-p or --pidfile filename Write PID of mythbackend to filename
-d or --daemon Runs mythbackend as a daemon
-v or --verbose debug-level Use '-v help' for level info
--printexpire List of auto-expire programs
--printsched Upcoming scheduled programs
--testsched Test run scheduler (ignore existing schedule)
--resched Force the scheduler to update
--nosched Do not perform any scheduling
--noupnp Do not enable the UPNP server
--nojobqueue Do not start the JobQueue
--nohousekeeper Do not start the Housekeeper
--noautoexpire Do not start the AutoExpire thread
--version Version information

Most options are additive except for none, all, and important.
These three are semi-explicit and take precedence over any
prior options given. You can however use something like
'-v none,jobqueue' to get only JobQueue related messages
and override the default verbosity level.

The additive options may also be subtracted from 'all' by
prefixing them with 'no', so you may use '-v all,nodatabase'
to view all but database debug messages.

Some debug levels may not apply to this program.

Need to add backend-specific troubleshooting help here, or at least link to Troubleshooting

Interpreting --printsched Output

The --printsched command line option prints out upcoming scheduled recordings.

This format is also used in mythbackend logs of scheduling activity (with -v schedule), and is particularly useful when obtaining schedule data with --testsched.