[systemd-devel] [PATCH] fstab-generator: add x-systemd.{after, requires-mounts-for}=

[Karel Zak]

On Wed, May 13, 2015 at 06:35:58AM +0300, Andrei Borzenkov wrote:
> В Tue, 12 May 2015 20:37:15 +0200
> Karel Zak <kzak at redhat.com> пишет:
> 
> > On Tue, May 12, 2015 at 07:29:33PM +0300, Andrei Borzenkov wrote:
> > > В Tue, 12 May 2015 18:04:50 +0200
> > > Karel Zak <kzak at redhat.com> пишет:
> > > 
> > > > Currently we have no way how to specify dependencies between fstab
> > > > entries (or another units) in the /etc/fstab. It means that users are
> > > > forced to bypass fstab and write .mount units manually.
> > > > 
> > > 
> > > Actually we have.
> > > 
> > > mkdir -p /etc/systemd/system/path-to-mount-point.mount.d
> > > cat > /etc/systemd/system/path-to-mount-point.mount.d/deps.conf << EOF
> > > [Unit]
> > > After=xxx
> > > Before=xxx
> > > Wants=xxx
> > > Requires=xxx
> > > EOF
> > 
> > You miss the point -- keep all in fstab.
> > 
> 
> I admit I do. Why? We want to keep in fstab bits and pieces that are
> common with other utilities. Which other tool needs to know systemd
> dependencies?

 Did you read the reference in the patch? It's not about systemd
 dependences, but about dependences between mount points. The fstab
 has been originally (by mount -a) serialized during boot. Now it's
 parallelized and in some cases it's bad thing and without extra
 configuration systemd is not able to understand the dependencies in
 fstab. It's admins' nightmare to require additional file somewhere in 
 /etc/systemd to fix systemd fstab interpretation.

 BTW, we already have x-systemd stuff in fstab...

    Karel


-- 
 Karel Zak  <kzak at redhat.com>
 http://karelzak.blogspot.com