On Fri, 05.08.16 10:26, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> > Everything happens asynchronously and systemd notices that the
> > filesystem has been mounted only through mountinfo.
>
> Yes, this is second real life case after ZFS which does not fit in
> rather simplistic model. We
Hi,
On 05/08/2016 09:26, Andrei Borzenkov wrote:
> In this case pragmatic solution is to order your service after mmfsd
> startup, assuming your filesystems are configured to be automounted
I already have such a dep in place, but due to the asynchronous nature
of GPFS the mount can (and does)
Отправлено с iPhone
> 4 авг. 2016 г., в 23:00, 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,
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
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
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
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