[mythtv-users] systemd & mythbackend
Udo van den Heuvel
udovdh at xs4all.nl
Tue Jun 7 14:53:10 UTC 2011
On 2011-06-07 00:20, R. G. Newbury wrote:
> Thanks for this. From reading the systemd originators blog it appears
> that /etc/systemd/user is for 'user' services while /lib... is for
> actual system services. Since we *usually* want the BE to run for
> 'everyone' and it often runs are root, then maybe /lib is the correct place.
> But it appears it would not make much difference on a dedicated mythbox.
Even when running as 'mythtv' instead of 'root'...
> Might be differences on multi-use boxes however.
Indeed.
> That blog also points out that the 'elegant' method of running a servie
> is to have it talk to the system through dbus (instead of forking) so
> that the system 'knows' which PID is the parent of any child. However
> that requires knowing the 'name' by which dbus knows things...but how
> would it know about mythbackend at all?
By creating a dbus file that explains about mythbackend. (haven't done
that yet)
> I've never figured out what half the stuff running as threads are or
> what they do! And changing to LXDE exposes a completely different set of
> names!
> The mysteries are never actually revealed...just new ones exposed.
I read about the cgroup support that is needed in the kernel for
systemd. They can help find the PIDs that belong to mysql or mythbackend
or whatever since easch daemon/program is started in a separate cgroup
as I understood it.
mythbackend just start and runs forever so I do not see much benefit in
dbus-support there, yet.
Udo
More information about the mythtv-users
mailing list