Bug#884994: systemd: shutdown does not send its warning messages when time is more than ten minutes

2020-01-31 Thread Michael Biebl
Control: forwarded -1 https://github.com/systemd/systemd/issues/14731 Control: severity -1 wishlist Control: tags -1 - moreinfo On Tue, 03 Sep 2019 10:25:33 +0200 Ansgar wrote: > Christoph Pleger writes: > >> Can you be more specific, how sysvinit behaved. > >> When exactly did sysvinit start

Bug#884994: systemd: shutdown does not send its warning messages when time is more than ten minutes

2019-09-03 Thread Ansgar
Christoph Pleger writes: >> Can you be more specific, how sysvinit behaved. >> When exactly did sysvinit start with the notification messages, what >> was >> the initial interval and how exactly did the interval change on each >> iteration. > > I am sorry, I do not remember more than I already

Bug#884994: systemd: shutdown does not send its warning messages when time is more than ten minutes

2019-09-03 Thread Christoph Pleger
Hello, Can you be more specific, how sysvinit behaved. When exactly did sysvinit start with the notification messages, what was the initial interval and how exactly did the interval change on each iteration. I am sorry, I do not remember more than I already wrote and unfortunately, I have

Bug#884994: systemd: shutdown does not send its warning messages when time is more than ten minutes

2019-09-02 Thread Michael Biebl
On Wed, 10 Jan 2018 10:08:26 +0100 Christoph Pleger wrote: > Hello, > > > Fwiw, this behaviour makes sense to me. > > If you start a scheduled login 2 days in advance, sending a shutdown > > message every minute would not be helpful. Restricting that to the last > > ten minutes seems reasonable.

Bug#884994: systemd: shutdown does not send its warning messages when time is more than ten minutes

2018-01-10 Thread Christoph Pleger
Hello, Fwiw, this behaviour makes sense to me. If you start a scheduled login 2 days in advance, sending a shutdown message every minute would not be helpful. Restricting that to the last ten minutes seems reasonable. How did sysvinit behave in that regard? As far as I remember, sysvinit

Bug#884994: systemd: shutdown does not send its warning messages when time is more than ten minutes

2018-01-09 Thread Michael Biebl
Am 08.01.2018 um 13:20 schrieb Christoph Pleger: > Hello, > >> >> This functionality has been reworked completely based on systemd-logind. >> >> Can you please test with a more recent version, like 232 from stable. > > at least, the problem does not occur in this form on a stretch machine, >

Bug#884994: systemd: shutdown does not send its warning messages when time is more than ten minutes

2018-01-08 Thread Christoph Pleger
Hello, This functionality has been reworked completely based on systemd-logind. Can you please test with a more recent version, like 232 from stable. at least, the problem does not occur in this form on a stretch machine, though I find it a disadvantage that no warning message is shown

Bug#884994: systemd: shutdown does not send its warning messages when time is more than ten minutes

2017-12-22 Thread Michael Biebl
Control: tags -1 moreinfo Control: severity -1 normal Am 22.12.2017 um 17:00 schrieb Christoph Pleger: > Package: systemd > Version: 215-17+deb8u7 > Severity: important > > Dear maintainers, > > The command 'shutdown -h +$time" does not send its repeated warning > messages to logged in users

Bug#884994: systemd: shutdown does not send its warning messages when time is more than ten minutes

2017-12-22 Thread Christoph Pleger
Package: systemd Version: 215-17+deb8u7 Severity: important Dear maintainers, The command 'shutdown -h +$time" does not send its repeated warning messages to logged in users when $time is greater than 10, but sends it only once - directly after entering the shutdown command. That is a