Mythlogserver
m (typo) |
m (Added missing letter.) |
||
| Line 6: | Line 6: | ||
the ''--syslog'', and ''--logpath'' command line options as well | the ''--syslog'', and ''--logpath'' command line options as well | ||
as to the database (if ''--nodblog'' isn't set.) For details on | as to the database (if ''--nodblog'' isn't set.) For details on | ||
| − | how the | + | how the logging options work, refer to [[Logging]]. |
A single copy of <code>mythlogserver</code> is started on each host, | A single copy of <code>mythlogserver</code> is started on each host, | ||
Latest revision as of 14:36, 1 January 2013
Note: The correct title of this article is mythlogserver. It appears incorrectly here due to technical restrictions.
mythlogserver is a program added in the 0.26 release.
Log messages generated by all of the other MythTV programs are sent to
mythlogserver which then distributes them to files based on
the --syslog, and --logpath command line options as well
as to the database (if --nodblog isn't set.) For details on
how the logging options work, refer to Logging.
A single copy of mythlogserver is started on each host,
as soon as any MythTV program starts,
typically mythbackend and mythfrontend.
mythlogserver's own logging options are inherited from the
program that starts it. Log entires in mythlogserver's own
log can be seen whenever one of its clients, such as a backend, starts
and stops using it. Also note that when mythlogserver
detects that no other MythTV program is using it, it will stop running
after 5 minutes.
See 0.26 specific sections in Logrotate All Applications and Simple rsyslog Configuration if they are used.
mythlogserver uses ZeroMQ libraries, which
are included with the MythTV distribution.
