Re: [systemd-devel] AmbientCapabilities working examples?

2017-09-04 Thread Kamil Jońca
Mantas Mikulėnas writes: > On Mon, Sep 4, 2017, 21:42 Kamil Jońca wrote: > > I try to configure my freeradius service with capabilities > (https://lists.debian.org/debian-devel/2017/09/msg00062.html) > > i can do with setting capabilities on

[systemd-devel] [Question] timezones in timers

2017-09-04 Thread Ivan Kurnosov
Hi, was it even considered initially to have proper timezones support in timers? Or perhaps it is somewhere in the roadmap? In particular, I'm speaking of `[Timer] OnCalendar` -- With best regards, Ivan Kurnosov ___ systemd-devel mailing list

Re: [systemd-devel] AmbientCapabilities working examples?

2017-09-04 Thread Mantas Mikulėnas
On Mon, Sep 4, 2017, 21:42 Kamil Jońca wrote: > > I try to configure my freeradius service with capabilities > (https://lists.debian.org/debian-devel/2017/09/msg00062.html) > > i can do with setting capabilities on freeradius binary. > But I headr about AmbientCapabilities

[systemd-devel] Permission/updating problems; different behaviour of two identical nspawn containers

2017-09-04 Thread Olaf the Lost Viking
[Sorry for not answering to Lennart's mail directly - it somehow got lost on my side so I have to copy/paste it from the archive.] >> I set up two (hopefully) identical debian containers in nspawn for a single >> service (DNS) on a debian host. Today's "apt upgrade" now throws >> permissions

[systemd-devel] AmbientCapabilities working examples?

2017-09-04 Thread Kamil Jońca
I try to configure my freeradius service with capabilities (https://lists.debian.org/debian-devel/2017/09/msg00062.html) i can do with setting capabilities on freeradius binary. But I headr about AmbientCapabilities directive and I tried to use it. Without success - freeradius dhcp server

Re: [systemd-devel] systemd.volatile=yes

2017-09-04 Thread Tobias Hunger
Hi Lennart, I probed a bit deeper: Apparently the openssh package is currently borked in arch linux:-/ I ended up with a slightly different version in the non systemd.volatile case which does work:-/ Sorry for the false alarm and wasting your time. Best Regards, Tobias PS: I did send the

[systemd-devel] Permission/updating problems; different behaviour of two identical nspawn containers

2017-09-04 Thread Olaf the Lost Viking
[Sorry for not answering to Lennart's answer directly - it somehow got lost so I have to copy/paste it from the archive.] >> I set up two (hopefully) identical debian containers in nspawn for a single >> service (DNS) on a debian host. Today's "apt upgrade" now throws >> permissions problem on

Re: [systemd-devel] systemd.volatile=yes

2017-09-04 Thread Tobias Hunger
Hi Lennart, On Mon, Sep 4, 2017 at 11:06 AM, Lennart Poettering wrote: > Hmm, mount.usr= should continue to be supported. It's documented in > the systemd-fstab-generator man page however, not in the > kernel-command-line one. We should fix that however, can you file a >

Re: [systemd-devel] systemd.volatile=yes

2017-09-04 Thread Lennart Poettering
f1;4803;0cOn So, 03.09.17 20:23, Tobias Hunger (tobias.hun...@gmail.com) wrote: > Hi, > > I have been running a system based on a tmpfs as '/' and with a > read-only /usr for a while now and am rather happy with that setup. I > added "mount.usr" and similar flags to systemd ages ago, so that I >

Re: [systemd-devel] [PATCH] shared: add statx(2) to @file-system syscall filter list

2017-09-04 Thread Lennart Poettering
On Sa, 02.09.17 19:47, Cristian Rodríguez (crrodrig...@opensuse.org) wrote: > --- > src/shared/seccomp-util.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/src/shared/seccomp-util.c b/src/shared/seccomp-util.c > index 29eb2b17d..0857f5907 100644 > --- a/src/shared/seccomp-util.c >