[mythtv] mythlogserver discussion

[Nigel Pearson]

Wondering about the wisdom of using/requiring mythlogserver
on simple "frontend only" setups, like Mac OS X and Windows.


As far as I can see, the intent of a log server is to collect
logs from multiple programs. It is a tidy way to help debug
complicated interactions between a frontend, backend,
previewgen, et c.


... but having the first Myth program that runs always try to
start it seems a bit of overkill if the user doesn't want it.



How would people feel if, say, there was a

A) --nologthread arg?
or
B) --nostartlogserver arg?


The frontend would still log to console/XTerm as usual,
but A) would create a dummy LoggingThread to just consume lines,
or flush, or something low-overhead, and B) would eventually
send logs to a mythlogserver if the user ever starts one,
and flush socket data until that happens.



Motivation: want to be able to have my MythFrontend.app
reduce the number of unwanted threads/tasks/sockets/crashes

--
Nigel Pearson, nigel at ind.tansu.com.au|"I'm confused."
Telstra Net. Eng., Sydney, Australia |   "Well, its a big club,
Office: 8576 5449    Fax:  9298 9033 |    we should get t-shirts!"
Mobile: 0408 664435  Home: 9792 6998 |- Doctor Who