Re: [systemd-devel] A question about the race condition between two service

On 11/05/2018 07:42 PM, Cristian Rodríguez wrote: > > > El 01-11-2018 a las 5:34, piliu escribió: > >> Any suggestion? >> > > Yeah. Don't..if poweroff fails reboot will too..please attack the root > cause of this problem.. why the machine fails to poweroff, is it a > service blocking poweroff

Re: [systemd-devel] Router Advertisement in systemd

Thank you. On Mon, Nov 5, 2018 at 11:36 AM Lennart Poettering wrote: > > On Mo, 05.11.18 11:09, Daniel Wang (wonder...@google.com) wrote: > > > Hi all, > > > > Recently I realized that systemd-networkd implements its own Router > > Advertisement and NDISC. While I am perfectly fine with using it,

Re: [systemd-devel] Add timer exception

On Mon, Nov 5, 2018 at 2:38 PM Lennart Poettering wrote: Note that you can combined OnCalendar= (i.e. calendar time events) and > OnUnitInactiveSec= and friends (i.e. monotonic time events) in a > single .timer unit. > Until this is implemented I think I will just do a `at -t 201901010325 syste

Re: [systemd-devel] Add timer exception

--On Monday, November 05, 2018 2:37 PM +0100 Lennart Poettering wrote: I would be great to add a concept for that, but so far nobody suggested a nice syntax and a patch for it yet. For prior art, take a look at the RRULE syntax in calendar files.

Re: [systemd-devel] Router Advertisement in systemd

On Mo, 05.11.18 11:09, Daniel Wang (wonder...@google.com) wrote: > Hi all, > > Recently I realized that systemd-networkd implements its own Router > Advertisement and NDISC. While I am perfectly fine with using it, I > wonder what motivated it given that the Linux kernel already > implemented bot

[systemd-devel] Router Advertisement in systemd

Hi all, Recently I realized that systemd-networkd implements its own Router Advertisement and NDISC. While I am perfectly fine with using it, I wonder what motivated it given that the Linux kernel already implemented both. Is it features? Flexibility? Stability? Also, what else in the ipv6 stack

Re: [systemd-devel] Question about hardware watchdog

On Mo, 05.11.18 16:21, Liu, Shuang (ADITG/ESM) (s...@de.adit-jv.com) wrote: > Hi, > > We are facing problem with hardware watchdog. > > To my understanding, the watchdog is pinged inside the manager_loop(), > which means, during e.g. systemctl daemon-reload, watchdog cannot be pinged. > > Here,

Re: [systemd-devel] [PATCH v2] hid2hci: Fix udev rules for linux-4.14+

On Wed, Jun 20, 2018 at 07:42:40PM +0300, Ville Syrjala wrote: > From: Ville Syrjälä > > Since commit 1455cf8dbfd0 ("driver core: emit uevents when > device is bound to a driver") the kernel started emitting > "bind" and "unbind" uevents which confuse the hid2hci > udev rules. > > The symptoms o

[systemd-devel] Question about hardware watchdog

Hi, We are facing problem with hardware watchdog. To my understanding, the watchdog is pinged inside the manager_loop(), which means, during e.g. systemctl daemon-reload, watchdog cannot be pinged. Here, perhaps other timeouts are involved in, e.g. generator timeout, dbus timeout, systemctl tim

Re: [systemd-devel] Add timer exception

On Mo, 05.11.18 10:58, Andy Pieters (syst...@andypieters.me.uk) wrote: > > OnUnitInactiveSec=24h (one day after the service FINISHED) > > > > In all those cases, since this is interval based, you would need a way to > > "prime the pump" I usually do this with > > > > OnStartupSec=15m (1/4h after t

Re: [systemd-devel] Add timer exception

On Mo, 05.11.18 09:36, Andy Pieters (syst...@andypieters.me.uk) wrote: > What can we do about this, please? Is there a better way to define a > timer to run every other day? Can we perhaps add an exception for a > specific date? A similar feature has been requested before: a way to configure bi-w

Re: [systemd-devel] A question about the race condition between two service

El 01-11-2018 a las 5:34, piliu escribió: Any suggestion? Yeah. Don't..if poweroff fails reboot will too..please attack the root cause of this problem.. why the machine fails to poweroff, is it a service blocking poweroff ? is there a kernel bug ?

Re: [systemd-devel] Add timer exception

On Mon, Nov 5, 2018 at 10:05 AM Jérémy Rosen wrote: > I would have my timer be duration-based instead of calandar based > (assuming that fits your need) > > You could use one of the following > > OnActiveSec=48h (two days after the timer last triggered > OnUnitActiveSec=48h (two days afte the uni

Re: [systemd-devel] Add timer exception

I would have my timer be duration-based instead of calandar based (assuming that fits your need) You could use one of the following OnActiveSec=48h (two days after the timer last triggered OnUnitActiveSec=48h (two days afte the unit was last started) Or slightly different OnUnitInactiveSec=24

[systemd-devel] Add timer exception

Dear Systemd list I have got a job that I want to execute every other day. The job is rather lengthy and takes more than 24 hours to complete but less than 48. So here are my criteria: Start today Start the day after tomorrow (t+2d)*1 Start the (t+2d)*2 Start 2 days after that (t+2d)*n My tim