I'm not sure, if this isn't perhaps a bigger issue. This is definitely NOT FIXED. But most users won't notice it (until it's too late and the filesystem becomes more and more inconsistent). Comment posted on: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1061639
Sorry for the additionally comment here. But I really want to raise awareness of this issue, because –at least for my installations- it is so critically bad.
It has something to do with services (init-scripts), /etc/init.d/, networking. But it's not only dns-masq, because I added an additional "killall -9 dnsmasqd; sync; sync; sleep 3" in /etc/init.d/umountfs, and it says "no process: dnsmasq", and it makes no difference. Filesystem never gets unmounted cleanly.
I'm not sure, if this isn't perhaps a bigger issue. This is definitely NOT FIXED. But most users won't notice it (until it's too late and the filesystem becomes more and more inconsistent). Comment posted on: https:/ /bugs.launchpad .net/ubuntu/ +source/ ifupdown/ +bug/1061639
Sorry for the additionally comment here. But I really want to raise awareness of this issue, because –at least for my installations- it is so critically bad.
It has something to do with services (init-scripts), /etc/init.d/, networking. But it's not only dns-masq, because I added an additional "killall -9 dnsmasqd; sync; sync; sleep 3" in /etc/init. d/umountfs, and it says "no process: dnsmasq", and it makes no difference. Filesystem never gets unmounted cleanly.
Thanks and happy bug fixing!