[mythtv-users] restricting mythpreviewgen?

[Alex Williamson]

On Tue, Jan 22, 2013 at 10:22 AM, Raymond Wagner <raymond at wagnerrp.com> wrote:
> On 1/22/2013 12:07, Alex Williamson wrote:
>>
>> Because I want different, isolated environments on a consolidated
>> system.
>
>
> Why not use chroot, or something like LXC?  Both offer isolated
> environments, allowing you to manage multiple system images without risk of
> interference from conflicting packages.

hdpvr requires kernel modules, including the ir module from the
staging tree.  That means a container doesn't really improve my
overall system uptime if I still have to reboot the host for a driver
glitch.

>> Isn't that why people generally use virtualization?
>
>
> No. They use virtualization because they need to run multiple separate
> operating systems (like Linux and Windows), are doing development and can't
> risk a kernel panic bringing down the whole thing, or can't risk one hacked
> server compromising the whole system.

Look, I'm pretty familiar with virtualization and I'm not looking for
an argument about why I've chosen this or that.  I have a slave that
is sufficient for the basic task of converting an hdpvr into a network
streaming device, but not cut out for compute tasks like
mythpreviewgen.  I can restrict other jobs to not run on this slave,
can or can I not restrict mythpreviewgen?  Thanks,

Alex