On 07/19/2018 06:26 AM, Juanjo Presa wrote:
I wonder which ways are to run last systemd versions? nowadays Im
running Centos 7 with systemd facebook backports
(https://github.com/facebookincubator/rpm-backports). But maybe you
guys have another way, NixOs? Archlinux?
Tyvm.
_
On 07/18/2018 03:26 PM, Juanjo Presa wrote:
> I wonder which ways are to run last systemd versions? nowadays Im
> running Centos 7 with systemd facebook backports
> (https://github.com/facebookincubator/rpm-backports). But maybe you guys
> have another way, NixOs? Archlinux?
You could always check
Hi Casey,
Thanks you for you prompt response.
On Wed, Aug 1, 2018 at 5:32 PM Casey Schaufler wrote:
>
> On 8/1/2018 3:18 AM, Martin Townsend wrote:
> > Hi,
> >
> > I have a service running with a SmackProcessLabel that uses the
> > supervisory watchdog feature, ie calls sd_notify(). The Watchdog
On Wed, Aug 1, 2018 at 7:18 PM Francis Moreau
wrote:
> Hello,
>
> I have a question regarding the default value of NamePolicy= defined
> in 99-default.link.
>
> The value is "NamePolicy=kernel database onboard slot path"
>
> Could someone explain me why "onbard" is preferred over "slot" which
> i
On 8/1/2018 3:18 AM, Martin Townsend wrote:
> Hi,
>
> I have a service running with a SmackProcessLabel that uses the
> supervisory watchdog feature, ie calls sd_notify(). The Watchdog
> keeps resetting the service and I get the following in the journal
>
> Jul 27 11:36:11 kernel: audit: type=1400
Hello,
I have a question regarding the default value of NamePolicy= defined
in 99-default.link.
The value is "NamePolicy=kernel database onboard slot path"
Could someone explain me why "onbard" is preferred over "slot" which
is preferred over "path" ?
Thanks.
--
Francis
___
Hi,
I have a service running with a SmackProcessLabel that uses the
supervisory watchdog feature, ie calls sd_notify(). The Watchdog
keeps resetting the service and I get the following in the journal
Jul 27 11:36:11 kernel: audit: type=1400 audit(1532691371.270:34):
lsm=SMACK fn=smack_unix_may_s
On Mi, 01.08.18 09:31, Liu, Shuang (ADITG/ESM) (s...@de.adit-jv.com) wrote:
> Hi,
>
> Does somebody has clue on the below issue?
> Ubuntu 16.04, systemd 229, D-Bus 1.10.6
> Thanks.
You turned on debug logging. If you do not you won't see it. It just
means that systemd tried to send a bus message
Hi,
Does somebody has clue on the below issue?
Ubuntu 16.04, systemd 229, D-Bus 1.10.6
Thanks.
Shuang
systemd: Failed to send signal.
[ 3.137257] systemd[1]: Failed to send job remove signal for 109: Connection
reset by peer
[ 3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit cha
