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
Thanks Kay - that jives with what I was thinking, as well. Is there a
good way to tell?
I've used systemd-analyze critical-chain to see if there is something
being kicked off by systemd before the network scripts can run, but
alas it appears that none of the systemd units are the culprit here.
I'
On Thu, Oct 1, 2015 at 7:21 PM, James wrote:
> Hello, just following up to see if there were any ideas on what may be
> causing this.
>
> Any thoughts appreciated.
>
> On Wed, Sep 23, 2015 at 10:17 PM, James wrote:
>> Hello,
>>
>> Hoping someone can point me in the right direction. I'm attempting
Hello, just following up to see if there were any ideas on what may be
causing this.
Any thoughts appreciated.
On Wed, Sep 23, 2015 at 10:17 PM, James wrote:
> Hello,
>
> Hoping someone can point me in the right direction. I'm attempting to
> change the interface name (eth0 -> wired) on one of m
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