On 10/03/2015 08:18 AM, Lennart Poettering wrote:
> On Wed, 30.09.15 16:49, Steve Dickson (ste...@redhat.com) wrote:
>
>> Hello,
>>
>> Is there a way for systemd to monitor kernel process?
>
> To add to what Kay said:
>
> No. Kernel threads cannot really be tracked by userspace in any
> sensib
On 10/01/2015 03:50 PM, Kay Sievers wrote:
> On Thu, Oct 1, 2015 at 9:30 PM, Steve Dickson wrote:
>>
>>
>> On 10/01/2015 09:24 AM, Kay Sievers wrote:
>>> On Wed, Sep 30, 2015 at 10:49 PM, Steve Dickson wrote:
Is there a way for systemd to monitor kernel process?
By monitor I mean the
On Wed, 30.09.15 16:49, Steve Dickson (ste...@redhat.com) wrote:
> Hello,
>
> Is there a way for systemd to monitor kernel process?
To add to what Kay said:
No. Kernel threads cannot really be tracked by userspace in any
sensible manner. We won't get SIGCHLD for them, and they cannot be
moved o
On Thu, Oct 1, 2015 at 9:30 PM, Steve Dickson wrote:
>
>
> On 10/01/2015 09:24 AM, Kay Sievers wrote:
>> On Wed, Sep 30, 2015 at 10:49 PM, Steve Dickson wrote:
>>> Is there a way for systemd to monitor kernel process?
>>> By monitor I mean the existence.
>>
>> No, and there is no plan to do anyth
On 10/01/2015 09:24 AM, Kay Sievers wrote:
> On Wed, Sep 30, 2015 at 10:49 PM, Steve Dickson wrote:
>> Is there a way for systemd to monitor kernel process?
>> By monitor I mean the existence.
>
> No, and there is no plan to do anything like that.
>
> Kernel tasks are kernel internals, and use
On Wed, Sep 30, 2015 at 10:49 PM, Steve Dickson wrote:
> Is there a way for systemd to monitor kernel process?
> By monitor I mean the existence.
No, and there is no plan to do anything like that.
Kernel tasks are kernel internals, and userspace must not make any
assumptions about them. They can
