Re: [systemd-devel] remote-fs dependency/ordering on network

2015-06-23 Thread Lukáš Nykrýn
Jan Synacek píše v Út 23. 06. 2015 v 15:39 +0200:
 Lennart Poettering lenn...@poettering.net writes:
 
  On Mon, 22.06.15 14:49, Jan Synacek (jsyna...@redhat.com) wrote:
 
  Lukáš Nykrýn lnyk...@redhat.com writes:
  
   Jan Synáček píše v Čt 18. 06. 2015 v 15:41 +0200:
   Is remote-fs.target somehow dependent/ordered on network.target or
   network-online.target? I can't find anything that would suggest it
   actually is.
   
   Cheers,
  
   If I am not mistaken remote-fs.target should be after all netdev mounts
   and netdev mounts should be after network-online.target.
  
  I'm sure it should, but I don't see any evidence that it really is. My
  mnt-nfs.mount that was generated by the fstab generator is ordered
  before remote-fs.target, which is correct. However, I can't find any
  dependency between remote-fs.target, and network*. I'm quite puzzled how
  NFS mounts mounted on boot can actually work correctly right now.
 
  There's also remote-fs-pre.target. That's ordered before all NFS
  mounts, and that's what the online stuff should be ordered before.
 
 All seems to be in order when the system is booting up. However, during
 shutdown, the order in which network* and remote* are taken down seems
 to be incorrect. If you could take a look at [1], that would help a bit,
 since I'm really clueless right now.
 
 [1] https://bugzilla.redhat.com/show_bug.cgi?id=1214466
 
 Cheers,

There is something messed up on that system.

Jun 23 07:30:56 acer.greshko.com systemd[1523]: Fixing conflicting jobs
-.slice/start,-.slice/stop by deleting job -.slice/stop
Jun 23 07:30:56 acer.greshko.com systemd[1523]: Fixing conflicting jobs
shutdown.target/stop,shutdown.target/start by deleting job
shutdown.target/stop
Jun 23 07:30:56 acer.greshko.com systemd[1523]: Deleting job
-.slice/start as dependency of job shutdown.target/stop
Jun 23 07:30:56 acer.greshko.com systemd[1546]: Fixing conflicting jobs
shutdown.target/stop,shutdown.target/start by deleting job
shutdown.target/stop

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] remote-fs dependency/ordering on network

2015-06-23 Thread Jan Synacek
Lennart Poettering lenn...@poettering.net writes:

 On Mon, 22.06.15 14:49, Jan Synacek (jsyna...@redhat.com) wrote:

 Lukáš Nykrýn lnyk...@redhat.com writes:
 
  Jan Synáček píše v Čt 18. 06. 2015 v 15:41 +0200:
  Is remote-fs.target somehow dependent/ordered on network.target or
  network-online.target? I can't find anything that would suggest it
  actually is.
  
  Cheers,
 
  If I am not mistaken remote-fs.target should be after all netdev mounts
  and netdev mounts should be after network-online.target.
 
 I'm sure it should, but I don't see any evidence that it really is. My
 mnt-nfs.mount that was generated by the fstab generator is ordered
 before remote-fs.target, which is correct. However, I can't find any
 dependency between remote-fs.target, and network*. I'm quite puzzled how
 NFS mounts mounted on boot can actually work correctly right now.

 There's also remote-fs-pre.target. That's ordered before all NFS
 mounts, and that's what the online stuff should be ordered before.

All seems to be in order when the system is booting up. However, during
shutdown, the order in which network* and remote* are taken down seems
to be incorrect. If you could take a look at [1], that would help a bit,
since I'm really clueless right now.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1214466

Cheers,
-- 
Jan Synacek
Software Engineer, Red Hat


signature.asc
Description: PGP signature
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] remote-fs dependency/ordering on network

2015-06-22 Thread Lennart Poettering
On Mon, 22.06.15 14:49, Jan Synacek (jsyna...@redhat.com) wrote:

 Lukáš Nykrýn lnyk...@redhat.com writes:
 
  Jan Synáček píše v Čt 18. 06. 2015 v 15:41 +0200:
  Is remote-fs.target somehow dependent/ordered on network.target or
  network-online.target? I can't find anything that would suggest it
  actually is.
  
  Cheers,
 
  If I am not mistaken remote-fs.target should be after all netdev mounts
  and netdev mounts should be after network-online.target.
 
 I'm sure it should, but I don't see any evidence that it really is. My
 mnt-nfs.mount that was generated by the fstab generator is ordered
 before remote-fs.target, which is correct. However, I can't find any
 dependency between remote-fs.target, and network*. I'm quite puzzled how
 NFS mounts mounted on boot can actually work correctly right now.

There's also remote-fs-pre.target. That's ordered before all NFS
mounts, and that's what the online stuff should be ordered before.

Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] remote-fs dependency/ordering on network

2015-06-22 Thread Jan Synacek
Lukáš Nykrýn lnyk...@redhat.com writes:

 Jan Synáček píše v Čt 18. 06. 2015 v 15:41 +0200:
 Is remote-fs.target somehow dependent/ordered on network.target or
 network-online.target? I can't find anything that would suggest it
 actually is.
 
 Cheers,

 If I am not mistaken remote-fs.target should be after all netdev mounts
 and netdev mounts should be after network-online.target.

I'm sure it should, but I don't see any evidence that it really is. My
mnt-nfs.mount that was generated by the fstab generator is ordered
before remote-fs.target, which is correct. However, I can't find any
dependency between remote-fs.target, and network*. I'm quite puzzled how
NFS mounts mounted on boot can actually work correctly right now.

-- 
Jan Synacek
Software Engineer, Red Hat


signature.asc
Description: PGP signature
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


[systemd-devel] remote-fs dependency/ordering on network

2015-06-18 Thread Jan Synáček
Is remote-fs.target somehow dependent/ordered on network.target or
network-online.target? I can't find anything that would suggest it
actually is.

Cheers,
-- 
Jan Synacek
Software Engineer, Red Hat


signature.asc
Description: PGP signature
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] remote-fs dependency/ordering on network

2015-06-18 Thread Lukáš Nykrýn
Jan Synáček píše v Čt 18. 06. 2015 v 15:41 +0200:
 Is remote-fs.target somehow dependent/ordered on network.target or
 network-online.target? I can't find anything that would suggest it
 actually is.
 
 Cheers,

If I am not mistaken remote-fs.target should be after all netdev mounts
and netdev mounts should be after network-online.target.

Lukas

___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] remote-fs dependency/ordering on network

2015-06-18 Thread Lennart Poettering
On Thu, 18.06.15 15:46, Lukáš Nykrýn (lnyk...@redhat.com) wrote:

 Jan Synáček píše v Čt 18. 06. 2015 v 15:41 +0200:
  Is remote-fs.target somehow dependent/ordered on network.target or
  network-online.target? I can't find anything that would suggest it
  actually is.
  
  Cheers,
 
 If I am not mistaken remote-fs.target should be after all netdev mounts
 and netdev mounts should be after network-online.target.

yeah, pretty much.

Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel