You didn't answer my question in #42 above.
Type "man null" to learn how /dev/null works.
The ps command produced an error message. Assuming that it wasn't
mis-typed, that means that the modem-manager process wasn't running,
which is the correct result. That's also consistent with last line in
Tuhu, if you type the following three commands into a terminal window
what is printed after each command?
sudo stop network-manager
initctl status modemmanager
ps p $(pgrep modem-manager) 2>/dev/null
The third command should print something only if modem-manager is still
running. It shouldn't be,
The /DEBUG file shows that modem-manager is still running, and at line
114 you can see that the init process has /var/log/upstart/modemmanager
open for write. That explains the "mount: / is busy" message.
I would think that modem-manager should have exited before umountroot is
run. Looking at /e
Tuhu, no, I wasn't asking that you run the commands from tty1.
Now that you've added the ps and lsof commands to the umountroot script,
it should create the text file '/DEBUG' when the system is shut down.
Please attach the file /DEBUG.
The error message "mount: / is busy" is being printed by th
Tuhu, your ps output shows quite a lot still running. Did you execute
the command from a terminal in the desktop environment? To be helpful,
the ps and lsof commands should be run from the /etc/init.d/umountroot
script. See message #5 above.
Before adding debug commands to umountroot, you might
Oops, I sent my previous message before I saw yours saying you've fixed
things. Congratulations, and thanks for sharing the method - I'll have
to remember that.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
h
The perl script /usr/share/sysv-rc/saveconfig prints out the current
configuration as a series of update-rc.d commands. If you like, I can
send you a copy from a more-or-less vanilla 12.04 install. It can't be
completely vanilla without my doing a fresh install in a VM, and I won't
volunteer for t
Daniel, try:
$ sudo update-rc.d -f umountroot remove
$ sudo update-rc.d umountroot start 60 0 6 .
Note the period at the end of the 2nd command. And yes, my previous
suggestion of using mv won't work, you have to use update-rc.d, sorry.
When I used update-rc.d to put umountroot at 03 as you hav
Daniel,
I notice "/etc/rc6.d/S03umountroot stop" in your ps output. On my 12.04
installs I have S60umountroot in /etc/rc0.d and /etc/rc6.d. S03 sounds
awfully early to me.
Try "sudo mv /etc/rc6.d/S03umountroot /etc/rc6.d/S60umountroot" and then
do "sudo shutdown -H now" and see what happens.
--
After installing network-manager 0.9.4.0-0ubuntu4 from precise-proposed,
things are looking good. The root filesystem is clean on reboot even
after a reinstall of libc6. Many thanks to Mathieu!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscrib
Yes, yes, I understand all of that, there is no need to continue
repeating it. Your motivations don't change the fact that, in trying to
fix one problem, you've created another. Your changes are causing
umountroot to FAIL at shutdown time.
--
You received this bug notification because you are a
The underlying problem is that, at system shutdown time, dhclient isn't
given the opportunity to gracefully exit, closing any files it has open.
This causes /etc/init.d/umountroot to fail. When umountroot fails, the
filesystem must be recovered.
There is, to the best of my knowledge, nothing part
One last data point: I'm seeing the problem only with wired connections
when "Available to all users" has been checked for that connection
(right-click on the nm-applet icon, select "Edit Connections...",
select the connection and click "Edit..." then check/uncheck "Available
to all users" in the
Clint, I don't see the dhclient process die when network-manager is
stopped. But I think I was guilty of some fuzzy thinking in saying that
the problem is due to the pid file being held open; the problem is that
the dhclient pid file isn't deleted from /var/run/sendsigs.omit.d (so
/etc/init.d/sen
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/963106
Title:
NetworkManager causes orphaned inodes
Status in “network-manager” package in Ubuntu:
New
Bug description:
Dur
Public bug reported:
During system shutdown, NetworkManager neither kills dhclient nor does
it remove the dhclient pid file from the directory
/var/run/sendsigs.omit.d. As a result, dhclient continues to hold the
pid file open for write and when /etc/init.d/umountroot tries to remount
the root fi
16 matches
Mail list logo
