Re: [systemd-devel] [PATCH] unit: When stopping due to BindsTo=, log which unit caused it

2015-04-24 Thread Lennart Poettering
On Wed, 22.04.15 16:55, Alban Crequy (al...@endocode.com) wrote: Thanks for the commits. They don't seem related to containers. I can reproduce my issue on git-master: sudo ~/git/systemd/systemd-nspawn --register=false --bind $HOME/tmp/vol -D debian-tree -b Then, in the container, make

Re: [systemd-devel] [PATCH] unit: When stopping due to BindsTo=, log which unit caused it

2015-04-24 Thread Lennart Poettering
On Fri, 24.04.15 17:10, Alban Crequy (al...@endocode.com) wrote: On Fri, Apr 24, 2015 at 12:45 PM, Lennart Poettering lenn...@poettering.net wrote: On Wed, 22.04.15 16:55, Alban Crequy (al...@endocode.com) wrote: Thanks for the commits. They don't seem related to containers. I can

Re: [systemd-devel] [PATCH] unit: When stopping due to BindsTo=, log which unit caused it

2015-04-24 Thread Alban Crequy
On Fri, Apr 24, 2015 at 12:45 PM, Lennart Poettering lenn...@poettering.net wrote: On Wed, 22.04.15 16:55, Alban Crequy (al...@endocode.com) wrote: Thanks for the commits. They don't seem related to containers. I can reproduce my issue on git-master: sudo ~/git/systemd/systemd-nspawn

Re: [systemd-devel] [PATCH] unit: When stopping due to BindsTo=, log which unit caused it

2015-04-24 Thread Alban Crequy
On Fri, Apr 24, 2015 at 5:34 PM, Lennart Poettering lenn...@poettering.net wrote: On Fri, 24.04.15 17:10, Alban Crequy (al...@endocode.com) wrote: On Fri, Apr 24, 2015 at 12:45 PM, Lennart Poettering lenn...@poettering.net wrote: On Wed, 22.04.15 16:55, Alban Crequy (al...@endocode.com)

Re: [systemd-devel] [PATCH] unit: When stopping due to BindsTo=, log which unit caused it

2015-04-22 Thread Alban Crequy
On Tue, Apr 21, 2015 at 10:35 PM, Zbigniew Jędrzejewski-Szmek zbys...@in.waw.pl wrote: On Tue, Apr 21, 2015 at 03:54:35PM +0200, Alban Crequy wrote: On Sat, Feb 28, 2015 at 5:40 PM, Lennart Poettering lenn...@poettering.net wrote: On Fri, 27.02.15 17:13, Lennart Poettering

Re: [systemd-devel] [PATCH] unit: When stopping due to BindsTo=, log which unit caused it

2015-04-21 Thread Alban Crequy
On Sat, Feb 28, 2015 at 5:40 PM, Lennart Poettering lenn...@poettering.net wrote: On Fri, 27.02.15 17:13, Lennart Poettering (lenn...@poettering.net) wrote: On Thu, 26.02.15 16:50, Martin Pitt (martin.p...@ubuntu.com) wrote: IMHO it would be prudent to skip adding the BindsTo= if at the time

Re: [systemd-devel] [PATCH] unit: When stopping due to BindsTo=, log which unit caused it

2015-04-21 Thread Zbigniew Jędrzejewski-Szmek
On Tue, Apr 21, 2015 at 03:54:35PM +0200, Alban Crequy wrote: On Sat, Feb 28, 2015 at 5:40 PM, Lennart Poettering lenn...@poettering.net wrote: On Fri, 27.02.15 17:13, Lennart Poettering (lenn...@poettering.net) wrote: On Thu, 26.02.15 16:50, Martin Pitt (martin.p...@ubuntu.com) wrote:

Re: [systemd-devel] [PATCH] unit: When stopping due to BindsTo=, log which unit caused it

2015-03-13 Thread Martin Pitt
Hey Lennart, Lennart Poettering [2015-02-28 17:40 +0100]: This is implemented now. Please check if this fixes this issue for you. This fixes the bad unmounts at boot, but also breaks the automatic cleanup of stale mounts after CD ejection. After inserting a medium, the .device looks ok: $

Re: [systemd-devel] [PATCH] unit: When stopping due to BindsTo=, log which unit caused it

2015-02-28 Thread Lennart Poettering
On Fri, 27.02.15 17:13, Lennart Poettering (lenn...@poettering.net) wrote: On Thu, 26.02.15 16:50, Martin Pitt (martin.p...@ubuntu.com) wrote: IMHO it would be prudent to skip adding the BindsTo= if at the time of creating the .mount unit the backing .device unit doesn't actually exist.

Re: [systemd-devel] [PATCH] unit: When stopping due to BindsTo=, log which unit caused it

2015-02-27 Thread Lennart Poettering
On Thu, 26.02.15 16:50, Martin Pitt (martin.p...@ubuntu.com) wrote: IMHO it would be prudent to skip adding the BindsTo= if at the time of creating the .mount unit the backing .device unit doesn't actually exist. In that case it's a mount which isn't managed by systemd, and we shouldn't touch

Re: [systemd-devel] [PATCH] unit: When stopping due to BindsTo=, log which unit caused it

2015-02-26 Thread Zbigniew Jędrzejewski-Szmek
On Tue, Feb 17, 2015 at 01:47:34PM -0500, Colin Walters wrote: I'm trying to track down a relatively recent change in systemd which broke OSTree; see https://bugzilla.gnome.org/show_bug.cgi?id=743891 Systemd started to stop sysroot.mount, and this patch should help me debug why at least.

Re: [systemd-devel] [PATCH] unit: When stopping due to BindsTo=, log which unit caused it

2015-02-26 Thread Martin Pitt
Hey Colin, Colin Walters [2015-02-24 15:05 -0500]: http://cgit.freedesktop.org/systemd/systemd/commit/?id=06e9783e2cc12eb6514e80c7f0014295f59b broke OSTree: https://bugzilla.redhat.com/show_bug.cgi?id=1195761#c1 I'm likely going to carry a revert downstream until I get a chance to

Re: [systemd-devel] [PATCH] unit: When stopping due to BindsTo=, log which unit caused it

2015-02-17 Thread Colin Walters
On Tue, Feb 17, 2015, at 01:47 PM, Colin Walters wrote: I'm trying to track down a relatively recent change in systemd which broke OSTree; see https://bugzilla.gnome.org/show_bug.cgi?id=743891 Systemd started to stop sysroot.mount, and this patch should help me debug why at least. Running

[systemd-devel] [PATCH] unit: When stopping due to BindsTo=, log which unit caused it

2015-02-17 Thread Colin Walters
I'm trying to track down a relatively recent change in systemd which broke OSTree; see https://bugzilla.gnome.org/show_bug.cgi?id=743891 Systemd started to stop sysroot.mount, and this patch should help me debug why at least. While we're here, break on the first unit we find that will