Re: [systemd-devel] Possible bug when a dummy service declares After= and/or Conflicts= a .mount unit?

2015-04-24 Thread Lennart Poettering
On Fri, 06.03.15 16:17, Michael Biebl (mbi...@gmail.com) wrote: 2015-03-06 11:20 GMT+01:00 Didier Roche didro...@ubuntu.com: It seems like tmp.mount unit was skipped as nothing declared any explicit dependency against it. What seems to confirm this is that if I add any enabled foo.service

Re: [systemd-devel] Possible bug when a dummy service declares After= and/or Conflicts= a .mount unit?

2015-03-07 Thread Michael Biebl
2015-03-06 17:09 GMT+01:00 Didier Roche didro...@ubuntu.com: Le 06/03/2015 16:17, Michael Biebl a écrit : 2015-03-06 11:20 GMT+01:00 Didier Roche didro...@ubuntu.com: It seems like tmp.mount unit was skipped as nothing declared any explicit dependency against it. What seems to confirm this

Re: [systemd-devel] Possible bug when a dummy service declares After= and/or Conflicts= a .mount unit?

2015-03-06 Thread Michael Biebl
2015-03-06 11:20 GMT+01:00 Didier Roche didro...@ubuntu.com: It seems like tmp.mount unit was skipped as nothing declared any explicit dependency against it. What seems to confirm this is that if I add any enabled foo.service which declares After=tmp.mount, or if I add the After= statement to

Re: [systemd-devel] Possible bug when a dummy service declares After= and/or Conflicts= a .mount unit?

2015-03-06 Thread Didier Roche
Le 06/03/2015 16:17, Michael Biebl a écrit : 2015-03-06 11:20 GMT+01:00 Didier Roche didro...@ubuntu.com: It seems like tmp.mount unit was skipped as nothing declared any explicit dependency against it. What seems to confirm this is that if I add any enabled foo.service which declares

Re: [systemd-devel] Possible bug when a dummy service declares After= and/or Conflicts= a .mount unit?

2015-03-06 Thread Didier Roche
Le 04/03/2015 13:40, Lennart Poettering a écrit : On Wed, 04.03.15 13:19, Didier Roche (didro...@ubuntu.com) wrote: Before=systemd-timesyncd.service foo.service local-fs.target umount.target systemd-timesyncd.service though is condition failed: Condition: start condition failed at Wed

Re: [systemd-devel] Possible bug when a dummy service declares After= and/or Conflicts= a .mount unit?

2015-03-05 Thread Lennart Poettering
On Thu, 05.03.15 08:36, Didier Roche (didro...@ubuntu.com) wrote: Le 04/03/2015 16:27, Michael Biebl a écrit : 2015-03-04 15:41 GMT+01:00 Lennart Poettering lenn...@poettering.net: Well, just removing the symlink is kinda pointless. It might still be pulled in by anything else that implicitly

Re: [systemd-devel] Possible bug when a dummy service declares After= and/or Conflicts= a .mount unit?

2015-03-05 Thread Lennart Poettering
On Wed, 04.03.15 16:27, Michael Biebl (mbi...@gmail.com) wrote: 2015-03-04 15:41 GMT+01:00 Lennart Poettering lenn...@poettering.net: Well, just removing the symlink is kinda pointless. It might still be pulled in by anything else that implicitly depepends on /tmp. What unit is supposed

Re: [systemd-devel] Possible bug when a dummy service declares After= and/or Conflicts= a .mount unit?

2015-03-04 Thread Didier Roche
Le 04/03/2015 16:27, Michael Biebl a écrit : 2015-03-04 15:41 GMT+01:00 Lennart Poettering lenn...@poettering.net: Well, just removing the symlink is kinda pointless. It might still be pulled in by anything else that implicitly depepends on /tmp. What unit is supposed to pull in tmp.mount

Re: [systemd-devel] Possible bug when a dummy service declares After= and/or Conflicts= a .mount unit?

2015-03-04 Thread Didier Roche
Just for the record: I didn't try on trunk yet, only systemd v219 that we ship in vivid. Cheers, Didier ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] Possible bug when a dummy service declares After= and/or Conflicts= a .mount unit?

2015-03-04 Thread Didier Roche
Hey, It seems that we discovered an issue if a service declares some relationship with a .mount unit. For instance, having tmp.mount disable (and nothing mounting /tmp as tmpfs in fstab): foo.service: [Unit] After=tmp.mount [Service] ExecStart=/bin/echo foo [Install]

Re: [systemd-devel] Possible bug when a dummy service declares After= and/or Conflicts= a .mount unit?

2015-03-04 Thread Andrei Borzenkov
On Wed, Mar 4, 2015 at 11:21 AM, Didier Roche didro...@ubuntu.com wrote: Hey, It seems that we discovered an issue if a service declares some relationship with a .mount unit. For instance, having tmp.mount disable (and nothing mounting /tmp as tmpfs in fstab): foo.service: [Unit]

Re: [systemd-devel] Possible bug when a dummy service declares After= and/or Conflicts= a .mount unit?

2015-03-04 Thread Didier Roche
Le 04/03/2015 09:29, Andrei Borzenkov a écrit : On Wed, Mar 4, 2015 at 11:21 AM, Didier Roche didro...@ubuntu.com wrote: tmpfs on /tmp type tmpfs (rw) status on tmp.mount: Loaded: loaded (/lib/systemd/system/tmp.mount; disabled; vendor preset: enabled) It says enabled here, although I'm

Re: [systemd-devel] Possible bug when a dummy service declares After= and/or Conflicts= a .mount unit?

2015-03-04 Thread Lennart Poettering
On Wed, 04.03.15 09:21, Didier Roche (didro...@ubuntu.com) wrote: Hey, It seems that we discovered an issue if a service declares some relationship with a .mount unit. For instance, having tmp.mount disable (and nothing mounting /tmp as tmpfs in fstab): tmp.mount is enabled statically via

Re: [systemd-devel] Possible bug when a dummy service declares After= and/or Conflicts= a .mount unit?

2015-03-04 Thread Didier Roche
Le 04/03/2015 12:49, Lennart Poettering a écrit : On Wed, 04.03.15 09:21, Didier Roche (didro...@ubuntu.com) wrote: Hey, It seems that we discovered an issue if a service declares some relationship with a .mount unit. For instance, having tmp.mount disable (and nothing mounting /tmp as tmpfs

Re: [systemd-devel] Possible bug when a dummy service declares After= and/or Conflicts= a .mount unit?

2015-03-04 Thread Lennart Poettering
On Wed, 04.03.15 13:19, Didier Roche (didro...@ubuntu.com) wrote: Le 04/03/2015 12:49, Lennart Poettering a écrit : On Wed, 04.03.15 09:21, Didier Roche (didro...@ubuntu.com) wrote: Hey, It seems that we discovered an issue if a service declares some relationship with a .mount unit. For

Re: [systemd-devel] Possible bug when a dummy service declares After= and/or Conflicts= a .mount unit?

2015-03-04 Thread Didier Roche
Le 04/03/2015 13:40, Lennart Poettering a écrit : On Wed, 04.03.15 13:19, Didier Roche (didro...@ubuntu.com) wrote: Le 04/03/2015 12:49, Lennart Poettering a écrit : On Wed, 04.03.15 09:21, Didier Roche (didro...@ubuntu.com) wrote: Hey, It seems that we discovered an issue if a service