On Fri, 02.10.15 14:00, Alessio Igor Bogani ([email protected]) wrote:
> I would prefer avoid PolicyKit. Moreover in the systemd 219's README
> PolicyKit is stated as optional (line 141). So I have rebuild systemd
> disabling policykit explicitly and it doesn't work:
>
> Oct 02 13:35:10
On 10/03/2015 08:18 AM, Lennart Poettering wrote:
> On Wed, 30.09.15 16:49, Steve Dickson ([email protected]) 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 Mon, 28.09.15 01:34, MohanR ([email protected]) wrote:
> Hi,
>
> Need help adding DHCP options/parameters in DHCPACK for PXE booting. I
> just populated dhcp.file[128] and dhcp.siaddr and I'm able to send
> gpxelinux.0 to PXE client[1]. But the PXE clients not able to download
> further files
On Mon, 28.09.15 14:05, David Timothy Strauss ([email protected]) wrote:
> On Wed, Sep 23, 2015, 18:14 Lennart Poettering
> wrote:
>
> > We are close to being sold out now, only 14 tickets are still
> > available now. If you intend to attend, make sure to register for the
> > conference *no
On Wed, 30.09.15 16:49, Steve Dickson ([email protected]) 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, 01.10.15 15:09, James ([email protected]) wrote:
> 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
>
