Hi,
I am writing a daemon script which uses sd_notify watchdog. This works fine,
system will kill the if the process doesn't notify.
However, I have seen in 1 occasion where, due to a programming error, the
script got stuck in a read and was not killed where it should have been.
So my question
On Fri, Jan 11, 2019 at 08:03:45AM +, Sietse van Zanen wrote:
> Hi,
>
>
>
> I am writing a daemon script which uses sd_notify watchdog. This works fine,
> system will kill the if the process doesn’t notify.
>
>
>
> However, I have seen in 1 occasion where, due to a programming error,
Hello,
I have no problems using this with Debian testing:
# /etc/systemd/system/systemd-journald.service.d/override.conf
[Service]
CapabilityBoundingSet=~CAP_MAC_OVERRIDE CAP_SYS_PTRACE
InaccessiblePaths=-/dev/pts -/dev/shm -/dev/mqueue -/dev/hugepages
-/setuid -/boot -/tmp -/var/tmp -/bin
Team plan with unlimited private repos and unlimited collaborators is free
for open source teams.
On Wed, Jan 9, 2019 at 11:41 PM Michael Biebl wrote:
>
> Am Mi., 9. Jan. 2019 um 21:24 Uhr schrieb Michael Biebl :
> >
> > https://blog.github.com/2019-01-07-new-year-new-github/
> >
> > might be of
Hi Lennart, all,
On Sun, Jan 6, 2019 at 6:40 PM Lennart Poettering
wrote:
>
> On Fr, 04.01.19 09:39, Giacinto Cifelli (gciof...@gmail.com) wrote:
>
> > Hi,
> >
> > I would like to give my DBus parameters names other than the default
> > arg_X for the introspection.
> >
> > Is it ok if I post
