Bug#923137: chrony: system call filter (now enabled by default) conflicts not only with mailonchange, but also with log

2019-03-01 Thread Vincent Blut
Control: tags -1 pending On Thu, Feb 28, 2019 at 11:36:10PM +0100, Francesco Poli wrote: On Thu, 28 Feb 2019 21:11:48 +0100 Vincent Blut wrote: [...] On Wed, Feb 27, 2019 at 10:26:13PM +0100, Francesco Poli wrote: [...] >File chronyd_debug.txt is attached (gzipped). That correspond to what

Bug#923137: chrony: system call filter (now enabled by default) conflicts not only with mailonchange, but also with log

2019-02-28 Thread Francesco Poli
On Thu, 28 Feb 2019 21:11:48 +0100 Vincent Blut wrote: [...] > On Wed, Feb 27, 2019 at 10:26:13PM +0100, Francesco Poli wrote: [...] > >File chronyd_debug.txt is attached (gzipped). > > That correspond to what I’m seeing in my tests. Upstream have applied > the patch I submitted to fix this so

Bug#923137: chrony: system call filter (now enabled by default) conflicts not only with mailonchange, but also with log

2019-02-28 Thread Vincent Blut
Control: tags -1 - moreinfo Control: found -1 3.0-4+deb9u1 On Wed, Feb 27, 2019 at 10:26:13PM +0100, Francesco Poli wrote: On Wed, 27 Feb 2019 14:05:03 +0100 Vincent Blut wrote: [...] On Mon, Feb 25, 2019 at 10:07:28PM +0100, Francesco Poli wrote: [...] >Nothing is added to

Bug#923137: chrony: system call filter (now enabled by default) conflicts not only with mailonchange, but also with log

2019-02-27 Thread Francesco Poli
On Wed, 27 Feb 2019 14:05:03 +0100 Vincent Blut wrote: [...] > On Mon, Feb 25, 2019 at 10:07:28PM +0100, Francesco Poli wrote: [...] > >Nothing is added to /var/log/messages when chrony fails to start. > > Ok so I think I can reproduce this issue on a Debian Buster i386 virtual > machine.

Bug#923137: chrony: system call filter (now enabled by default) conflicts not only with mailonchange, but also with log

2019-02-27 Thread Vincent Blut
Hi Francesco, On Mon, Feb 25, 2019 at 10:07:28PM +0100, Francesco Poli wrote: On Mon, 25 Feb 2019 01:22:40 +0100 Vincent Blut wrote: On Sun, Feb 24, 2019 at 08:19:02PM +0100, Francesco Poli wrote: >On Sun, 24 Feb 2019 17:52:46 +0100 Vincent Blut wrote: > >> Please use `ps ax | grep chrony'

Bug#923137: chrony: system call filter (now enabled by default) conflicts not only with mailonchange, but also with log

2019-02-25 Thread Francesco Poli
On Mon, 25 Feb 2019 01:22:40 +0100 Vincent Blut wrote: > On Sun, Feb 24, 2019 at 08:19:02PM +0100, Francesco Poli wrote: > >On Sun, 24 Feb 2019 17:52:46 +0100 Vincent Blut wrote: > > > >> Please use `ps ax | grep chrony' (or ps -ef). `ps a' only lists > >> processes with a tty. > > > >You are

Bug#923137: chrony: system call filter (now enabled by default) conflicts not only with mailonchange, but also with log

2019-02-24 Thread Vincent Blut
On Sun, Feb 24, 2019 at 08:19:02PM +0100, Francesco Poli wrote: On Sun, 24 Feb 2019 17:52:46 +0100 Vincent Blut wrote: Please use `ps ax | grep chrony' (or ps -ef). `ps a' only lists processes with a tty. You are right, sorry: I wanted to simplify the command output, but I overplayed...

Bug#923137: chrony: system call filter (now enabled by default) conflicts not only with mailonchange, but also with log

2019-02-24 Thread Francesco Poli
On Sun, 24 Feb 2019 17:52:46 +0100 Vincent Blut wrote: > On Sun, Feb 24, 2019 at 05:05:58PM +0100, Francesco Poli wrote: > >On Sun, 24 Feb 2019 16:25:19 +0100 Vincent Blut wrote: > > > >[...] > >> On Sun, Feb 24, 2019 at 12:59:21PM +0100, Francesco Poli (wintermute) > >> wrote: > >[...] > >>

Bug#923137: chrony: system call filter (now enabled by default) conflicts not only with mailonchange, but also with log

2019-02-24 Thread Vincent Blut
On Sun, Feb 24, 2019 at 05:05:58PM +0100, Francesco Poli wrote: On Sun, 24 Feb 2019 16:25:19 +0100 Vincent Blut wrote: [...] On Sun, Feb 24, 2019 at 12:59:21PM +0100, Francesco Poli (wintermute) wrote: [...] >Everything seems to be fine, but: > > $ ps a | grep chrony > 10686 pts/1S+

Bug#923137: chrony: system call filter (now enabled by default) conflicts not only with mailonchange, but also with log

2019-02-24 Thread Francesco Poli
On Sun, 24 Feb 2019 16:25:19 +0100 Vincent Blut wrote: [...] > On Sun, Feb 24, 2019 at 12:59:21PM +0100, Francesco Poli (wintermute) > wrote: [...] > >Everything seems to be fine, but: > > > > $ ps a | grep chrony > > 10686 pts/1S+ 0:00 grep chrony > > > >the daemon is not running! >

Bug#923137: chrony: system call filter (now enabled by default) conflicts not only with mailonchange, but also with log

2019-02-24 Thread Vincent Blut
Control: tags -1 moreinfo Hi Francesco, On Sun, Feb 24, 2019 at 12:59:21PM +0100, Francesco Poli (wintermute) wrote: Package: chrony Version: 3.4-2 Severity: important Hello there! Thanks for maintaining this useful package. You’re welcome! I've just upgraded to version 3.4-2 and noticed

Bug#923137: chrony: system call filter (now enabled by default) conflicts not only with mailonchange, but also with log

2019-02-24 Thread Francesco Poli (wintermute)
Package: chrony Version: 3.4-2 Severity: important Hello there! Thanks for maintaining this useful package. I've just upgraded to version 3.4-2 and noticed that the daemon failed to restart, due to the mailonchange directive: $ grep -B 1 ^mailonchange /etc/chrony/chrony.conf # Warn root.