** Changed in: network-manager (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/113095
Title:
nfs timeout on shutdown
To manage notifications about thi
Not a D-Bus bug
** Changed in: dbus (Ubuntu)
Status: New => Invalid
--
nfs timeout on shutdown
https://bugs.launchpad.net/bugs/113095
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
Fix is in my branch:
https://code.launchpad.net/~ttx/network-manager/sendsigs-protection
Test packages available in my PPA.
For this to work with wireless it also needs a fix (yet to come) in
wpasupplicant.
Also It won't work with n-m connections that are not set "for all users" as
Gnome will t
On Tue, Mar 03, 2009 at 12:49:31PM -, Thierry Carrez wrote:
> For testing purposes I uploaded a network-manager upgrade for intrepid to my
> PPA:
> https://launchpad.net/~ttx/+archive/ppa
>
> Let me know if it fixes this problem as well as bug 211631.
>
Can you plesae provide a patch agains
For testing purposes I uploaded a network-manager upgrade for intrepid to my
PPA:
https://launchpad.net/~ttx/+archive/ppa
Let me know if it fixes this problem as well as bug 211631.
--
nfs timeout on shutdown
https://bugs.launchpad.net/bugs/113095
You received this bug notification because you
This is linked to bug 211631.
CIFS mounts also trigger an annoying timeout at shutdown. A fix preventing NM
to be prematurely killed in sendsigs should fix both bugs.
--
nfs timeout on shutdown
https://bugs.launchpad.net/bugs/113095
You received this bug notification because you are a member of
I wonder whether we should ship a package managed link in
/lib/init/rw/ or do that in some postinst script? Would there be a
problem to just ship the "pid-file" link in package?
--
nfs timeout on shutdown
https://bugs.launchpad.net/bugs/113095
You received this bug notification because you ar
On Fri, Dec 26, 2008 at 5:26 PM, Alexander Sack wrote:
> the issue here would be that / and /usr still cannot be remote mounts right?
>
> will those cases be worse off before when using this patch?
I can do some testing of those cases next week, I suppose.
What should be clear, though, is that N
Dustin Kirkland wrote:
> I am experiencing this problem on all Intrepid machines on my network.
> It took me quite some time to diagnose, as I was chasing error messages
> related to acpid and sound, when it was ultimately NFS+NetworkManager
> that was causing my problem, as described above.
>
> Da
I am experiencing this problem on all Intrepid machines on my network.
It took me quite some time to diagnose, as I was chasing error messages
related to acpid and sound, when it was ultimately NFS+NetworkManager
that was causing my problem, as described above.
Daniel's patch solves the problem fo
No only the default i think: just loopback device there (- = newline):
auto lo - iface lo inet loopback - address 127.0.0.1 - netmask 255.0.0.0 -
#iface eth0 inet dhcp
There are two other devices, eth0 (wired) and eth1 (ipw2200 wireless) which are
autoconfigured via dhcp. The WAP key for eth
On Sat, Nov 01, 2008 at 04:22:26PM -, Jan Ericsen wrote:
> I have run into this problem after upgrading to Kubuntu 8.10. On
> reboot/shutdown it hangs after sendsigs "All processes ended within 2
> seconds." Daniels patch didnt help, but having the umountnfs.sh run
> before sendsigs like sugge
I have run into this problem after upgrading to Kubuntu 8.10. On
reboot/shutdown it hangs after sendsigs "All processes ended within 2
seconds." Daniels patch didnt help, but having the umountnfs.sh run
before sendsigs like suggested by Jörg fixed it for me.
--
nfs timeout on shutdown
https://bu
On Wed, Aug 27, 2008 at 09:44:48PM -, Daniel J Blueman wrote:
> Yes, if /usr were mounted over NFS, we'd experience this hang too.
>
> There are secondary implications of the NFS unmount not being seen by
> the NFS server, since the NFS server still has an mount entry for the
> client, which i
Yes, if /usr were mounted over NFS, we'd experience this hang too.
There are secondary implications of the NFS unmount not being seen by
the NFS server, since the NFS server still has an mount entry for the
client, which is no longer contactable. It tries to make a delegation
callback, which invar
i think one of the problems with NM being killed is the /usr mounted
over nfs use case. Would this patch improve that as well? do loaded
libs/binaries keep the device in use or wouldnt that be a problem?
--
nfs timeout on shutdown
https://bugs.launchpad.net/bugs/113095
You received this bug notif
I'm experiencing the same issue in Hardy and Intrepid (and before), with
NFSv4 homedir and been bumping into this really a lot.
To see what's actually happening, change VERBOSE to 'yes' in
/etc/default/rcS and boot without 'splash', as you'll already know;
there is a problem/race with your suggest
Hi,
the same here (Feisty ans Gutsy)
this does the trick for me:
rm /etc/rc*/S31umountnfs.sh
ln -s ../init.d/umountnfs.sh /etc/rc0.d/S17umountnfs.sh
ln -s ../init.d/umountnfs.sh /etc/rc6.d/S17umountnfs.sh
So nfs will be stopped before the network goes down.
--
nfs timeout on shutdown
https
** Changed in: dbus (Ubuntu)
Sourcepackagename: nfs-utils => dbus
--
nfs timeout on shutdown
https://bugs.launchpad.net/bugs/113095
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
I tried to stop dbus later in in the shutdown/restart process. It now
has K90dbus in both rc0.d and rc6.d. This solves the problem with the
long timeout but there is still some error messages on the screen.
Howe late is it recommended that dbus is stopped or how early is it
possible to stop NFS an
20 matches
Mail list logo
