Re: [systemd-devel] firmware update check script

2016-08-04 Thread Lennart Poettering
On Thu, 04.08.16 09:45, Stéphane ANCELOT (sance...@free.fr) wrote: > You are right, but that's only systemd that is incompatible with > this feature (and some more). No, that has little to do with systemd. It's a systematic change how today's hardware works, and that probing is asynchronous and

Re: [systemd-devel] firmware update check script

2016-08-04 Thread Stéphane ANCELOT
You are right, but that's only systemd that is incompatible with this feature (and some more). As some people and some articles I have read on the web, it is time for myself switching my system to a professional initscript service. - Mail original - De: "Lennart Poettering"

Re: [systemd-devel] firmware update check script

2016-08-04 Thread Jóhann B . Guðmundsson
On 08/04/2016 07:45 AM, Stéphane ANCELOT wrote: You are right, but that's only systemd that is incompatible with this feature (and some more). Actually all initsystems are incompatible with this. As some people and some articles I have read on the web, it is time for myself switching my

Re: [systemd-devel] firmware update check script

2016-08-04 Thread Stéphane ANCELOT
Hi, I am already doing this with other init systems with modern usb , I am able doing this with my TV, soundbar... The only bad thing is that systemd has sprayed in some recent distributions (where are the benefits ?) Unfortunately in today's world, there are more commercial people than

[systemd-devel] Reacting to non-systemd mounts

2016-08-04 Thread Matteo Panella
Hi, sorry for bothering you with a fairly uncommon issue, but I haven't been able to find a solution so far and Google turned up empty. I have some CentOS 7.2 machines with systemd 219 which are members of an IBM GPFS cluster and need to start up some services only after a specific GPFS

Re: [systemd-devel] machined: after CPU offline then online, vcpupin KVM guest failed to start

2016-08-04 Thread Cedric Bosdonnat
Hi Lennart and Werner, On Wed, 2016-08-03 at 16:56 +0200, Lennart Poettering wrote: > On Wed, 03.08.16 14:46, Dr. Werner Fink (werner at suse.de) wrote: > > problem with v228 (and I guess this is also later AFAICS from logs of > > current git) that repeating CPU hotplug events (offline/online).

Re: [systemd-devel] Reacting to non-systemd mounts

2016-08-04 Thread Lennart Poettering
On Thu, 04.08.16 16:34, Matteo Panella (matteo.pane...@cnaf.infn.it) wrote: > Hi, > > sorry for bothering you with a fairly uncommon issue, but I haven't been > able to find a solution so far and Google turned up empty. > > I have some CentOS 7.2 machines with systemd 219 which are members of

Re: [systemd-devel] Reacting to non-systemd mounts

2016-08-04 Thread Lennart Poettering
On Thu, 04.08.16 22:00, Matteo Panella (matteo.pane...@cnaf.infn.it) wrote: > Hi, > > On 04/08/2016 16:43, Mantas Mikulėnas wrote: > > Then add an After= instead. Unit ordering is already specified > > separately from dependencies. > > That does not work, unfortunately: since the entry in

Re: [systemd-devel] Reacting to non-systemd mounts

2016-08-04 Thread Matteo Panella
Hi, On 04/08/2016 16:43, Mantas Mikulėnas wrote: > Then add an After= instead. Unit ordering is already specified > separately from dependencies. That does not work, unfortunately: since the entry in fstab is marked "noauto" systemd ignores the mount and fires up the service once the other

Re: [systemd-devel] Reacting to non-systemd mounts

2016-08-04 Thread Matteo Panella
Hi, On 04/08/2016 22:03, Lennart Poettering wrote: > How does GPFS suggest that apps wait for the mounts? It "grew" official support for systemd only in very recent releases, so up until now most people just threw a busy wait in rc.?d between S*gpfs and other services[1]. > You could probably