[mythtv-users] How MANY backend threads!?!?!?

[Gavin Hurlbut]

On Thu, Oct 14, 2010 at 3:12 PM, Mike Perkins
<mikep at randomtraveller.org.uk>wrote:

> It might be useful if the spawned parts of mythbackend actually had
> different names so one could figure out what was happening. 32 threads of
> 'mythbackend' isn't really meaningful, whereas if some of them were, I
> dunno, 'mythgenpreview' for example, one could see what was what.
>

This is already the case.  When we spawn off children, we use fork, which
creates a new process, and then we use execl, which changes the name of the
process.  mythpreviewgen already exists in trunk.


> We already have 'mythtranscode', 'mytharchive',... so why not extend this
> scheme to forked processes? I understand it might not be so easy with
> threads, but still...
>

I think there is some confusion.  Forked processes != threads.

If you truly want to know what each of the threads are, fire up gdb, attach
to the backend process and get a full backtrace of all threads.  This is
standard debugging procedure, and is even outlined on the wiki, if I'm not
mistaken.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20101014/b4f65a33/attachment.htm>