Check if NM 0.9.10's "files are no longer watched for changes by default" change affects us
See http://blogs.gnome.org/dcbw/2014/06/20/well-build-a-dream-house-of-net/. It might be that we need to run
nmcli con reload after bind-mounting the NM config persistent directory, for example.
Hint: start with writing a test case to check that a connection added with NM persistence enabled shows up after rebooting with persistence enabled. We already have some code to add NM connections, that's used in the
#7 Updated by intrigeri about 4 years ago
- Status changed from In Progress to Resolved
- Assignee deleted (
- % Done changed from 0 to 100
I could not run my draft test since the test suite is not functional enough on Jessie to go that far yet. In any case I think it's good to have an automated test for this, so I'll keep it around and will fix it later if needed (unless anonym is faster than me, which I would not mind :)
I tested this manually, and verified that we bind-mount the persistent NM connections directory before we start the NM service, so we're good here => closing.