Difference between revisions of "Mythlogserver"
(0.27 changes) |
(Add detail to --nologserver option) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 8: | Line 8: | ||
how the logging options work, refer to [[Logging]]. | how the logging options work, refer to [[Logging]]. | ||
| − | In 0.27, the ''--nologserver'' | + | In 0.27, the ''--nologserver'' option has been added and if used on the |
| − | command line, ''mythlogserver'' will not be started. | + | command line, ''mythlogserver'' will not be started. Output will only |
| − | go to the console. Additionally, users building from source can select | + | go to the console (file, db and syslog are disabled.) Naturally, the |
| + | ''--quiet'' option shouldn't be used if logging is desired (the same is | ||
| + | probably true for ''--daemon'', but that needs testing.) | ||
| + | |||
| + | Additionally, users building from source can select | ||
the '' --disable-mythlogserver'' option when running ''configure''. | the '' --disable-mythlogserver'' option when running ''configure''. | ||
If used, each mythProgram will have a logging thread and that will handle syslog, file | If used, each mythProgram will have a logging thread and that will handle syslog, file | ||
logging. | logging. | ||
| + | |||
| + | Also in 0.27 <code?>mythlogserver</code> is now optional, and really only intended for debugging purposes. | ||
A single copy of <code>mythlogserver</code> is started on each host, | A single copy of <code>mythlogserver</code> is started on each host, | ||
| Line 19: | Line 25: | ||
typically <code>mythbackend</code> and <code>mythfrontend</code>. | typically <code>mythbackend</code> and <code>mythfrontend</code>. | ||
<code>mythlogserver</code>'s own logging options are inherited from the | <code>mythlogserver</code>'s own logging options are inherited from the | ||
| − | program that starts it. Log | + | program that starts it. Log entries in <code>mythlogserver</code>'s own |
log can be seen whenever one of its clients, such as a backend, starts | log can be seen whenever one of its clients, such as a backend, starts | ||
and stops using it. Also note that when <code>mythlogserver</code> | and stops using it. Also note that when <code>mythlogserver</code> | ||
Revision as of 16:18, 29 December 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.
In 0.27, the --nologserver option has been added and if used on the command line, mythlogserver will not be started. Output will only go to the console (file, db and syslog are disabled.) Naturally, the --quiet option shouldn't be used if logging is desired (the same is probably true for --daemon, but that needs testing.)
Additionally, users building from source can select the --disable-mythlogserver option when running configure. If used, each mythProgram will have a logging thread and that will handle syslog, file logging.
Also in 0.27 <code?>mythlogserver</code> is now optional, and really only intended for debugging purposes.
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 entries 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.
