** Changed in: sysvinit (Debian)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before network filesystems are unmounted (CIFS
Unfortunately, the bug seems to be back in Ubuntu 16.04 (Xenial) now,
probably due to changements in the boot and shutdown sequences. See also
[bug 1577885].
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** No longer affects: dbus (Ubuntu Lucid)
** No longer affects: dbus (Ubuntu Natty)
** No longer affects: netbase (Ubuntu Lucid)
** No longer affects: netbase (Ubuntu Natty)
** No longer affects: network-manager (Ubuntu Lucid)
** No longer affects: network-manager (Ubuntu Natty)
** No longer
** No longer affects: dbus (Ubuntu Lucid)
** No longer affects: dbus (Ubuntu Natty)
** No longer affects: netbase (Ubuntu Lucid)
** No longer affects: netbase (Ubuntu Natty)
** No longer affects: network-manager (Ubuntu Lucid)
** No longer affects: network-manager (Ubuntu Natty)
** No longer
It's a slightly different problem, I guess, but in Kubuntu 13.10 the
shutdown does not complete for me. It stops with the message Stale NFS
file handle. I suppose this is a different bug because it involves
NFS, not CIFS.
--
You received this bug notification because you are a member of Ubuntu
Markus, your screenshot shows a network-manager error:
nm-dispatcher.action: Caught signal 15, shutting down...
This indicates that some part of NM is not being correctly guarded from
/etc/init.d/sendsigs, resulting in abnormal termination that breaks the
network connection before network
Steve, turns out, there already was such a bug report:
https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1066484/comments/11
Regarding the CIFS mounts: Today, I changed the auto cifs mounts during
startup to noauto,user mounts, which get mounted by my user using a script
after
Markus, your screenshot shows a network-manager error:
nm-dispatcher.action: Caught signal 15, shutting down...
This indicates that some part of NM is not being correctly guarded from
/etc/init.d/sendsigs, resulting in abnormal termination that breaks the
network connection before network
Steve, turns out, there already was such a bug report:
https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1066484/comments/11
Regarding the CIFS mounts: Today, I changed the auto cifs mounts during
startup to noauto,user mounts, which get mounted by my user using a script
after
Here's a screenshot of the last few lines visible before my notebook
shuts down. It's 13.04 as of May 27th.
** Attachment added: Shutdown messages
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/211631/+attachment/3688214/+files/IMG_20130527_192438.jpg
--
You received this bug
The problem is still there on a fresh Raring installation.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before network filesystems are
The problem is still there on a fresh Raring installation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before network filesystems are unmounted (CIFS
It affects me too, but the last 20 times I clicked on this link ( This
bug affects 119 people. Does this bug affect you? Edit ) since
yesterday, it gives me a time out error, please try again in a few
minutes
--
You received this bug notification because you are a member of Ubuntu
Server Team,
It affects me too, but the last 20 times I clicked on this link ( This
bug affects 119 people. Does this bug affect you? Edit ) since
yesterday, it gives me a time out error, please try again in a few
minutes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Th e problems continues on precise pangolin and quantal quetzal
short info:
(cisco vpn, mount.cifs of drives, when shutting down it takes about 2 minutes
because there a problem with the unmounting of the cifs drives; when manually
unmounting before shutting down there is no problem, shutdown
Th e problems continues on precise pangolin and quantal quetzal
short info:
(cisco vpn, mount.cifs of drives, when shutting down it takes about 2 minutes
because there a problem with the unmounting of the cifs drives; when manually
unmounting before shutting down there is no problem, shutdown
only info:
the vpn seems to work fine,
mvg,
G
On za, 2012-04-21 at 04:28 +, Clint Byrum wrote:
What type of VPN connection? If it is managed by NetworkManager, it
should be brought down when network manager is brought down, *after* all
network filesystems are brought down.
If not,
** Attachment added: unknown-KR3lma
https://bugs.launchpad.net/bugs/211631/+attachment/3121146/+files/unknown-KR3lma
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
only info:
the vpn seems to work fine,
mvg,
G
On za, 2012-04-21 at 04:28 +, Clint Byrum wrote:
What type of VPN connection? If it is managed by NetworkManager, it
should be brought down when network manager is brought down, *after* all
network filesystems are brought down.
If not,
** Attachment added: unknown-KR3lma
https://bugs.launchpad.net/bugs/211631/+attachment/3121146/+files/unknown-KR3lma
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is
I'll open a bug myself shortly for the VPN case; and reply here with the
bug number.
** No longer affects: network-manager
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
I'll open a bug myself shortly for the VPN case; and reply here with the
bug number.
** No longer affects: network-manager
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is
On Sat, Apr 21, 2012 at 04:47:40AM -, Mathieu Trudel-Lapierre wrote:
Well, that would normally be correct, but the VPN plugins depend on
vpnc, pptp, openvpn, etc. to be running to establish and keep the VPN
connection up for rekeying and such. Those don't get a pid file in
On Sat, Apr 21, 2012 at 04:47:40AM -, Mathieu Trudel-Lapierre wrote:
Well, that would normally be correct, but the VPN plugins depend on
vpnc, pptp, openvpn, etc. to be running to establish and keep the VPN
connection up for rekeying and such. Those don't get a pid file in
I have tried the cifs mount over VPN scenario and shutting down does still
take time. I think connected mounts at shutdown are fixed so they unmount,
but if the VPN is disconnected prior to shutdown the unmount will hang
still.
--
You received this bug notification because you are a member of
What type of VPN connection? If it is managed by NetworkManager, it
should be brought down when network manager is brought down, *after* all
network filesystems are brought down.
If not, that seems like a bug in whatever is running VPNs, but its
probably not *this* bug. I would suggest reporting
Well, that would normally be correct, but the VPN plugins depend on
vpnc, pptp, openvpn, etc. to be running to establish and keep the VPN
connection up for rekeying and such. Those don't get a pid file in
/run/sendsigs.omit.d yet, and so they would get killed by the sendsigs
script shortly before
I have tried the cifs mount over VPN scenario and shutting down does still
take time. I think connected mounts at shutdown are fixed so they unmount,
but if the VPN is disconnected prior to shutdown the unmount will hang
still.
--
You received this bug notification because you are a member of
What type of VPN connection? If it is managed by NetworkManager, it
should be brought down when network manager is brought down, *after* all
network filesystems are brought down.
If not, that seems like a bug in whatever is running VPNs, but its
probably not *this* bug. I would suggest reporting
Well, that would normally be correct, but the VPN plugins depend on
vpnc, pptp, openvpn, etc. to be running to establish and keep the VPN
connection up for rekeying and such. Those don't get a pid file in
/run/sendsigs.omit.d yet, and so they would get killed by the sendsigs
script shortly before
On vr, 2012-04-06 at 10:12 +, James wrote:
Steve Langasek - I have just tried to replicate in 12.04 beta and could
not reproduce the issue any more. I had a mounted a SMB share using
/etc/fstab which appeared to be successfully unmounted prior to shutdown
(or at least, it didn't hang for a
On vr, 2012-04-06 at 10:12 +, James wrote:
Steve Langasek - I have just tried to replicate in 12.04 beta and could
not reproduce the issue any more. I had a mounted a SMB share using
/etc/fstab which appeared to be successfully unmounted prior to shutdown
(or at least, it didn't hang for a
Steve Langasek - I have just tried to replicate in 12.04 beta and could
not reproduce the issue any more. I had a mounted a SMB share using
/etc/fstab which appeared to be successfully unmounted prior to shutdown
(or at least, it didn't hang for a minute or so, it shut down
immediately).
--
You
Steve Langasek - I have just tried to replicate in 12.04 beta and could
not reproduce the issue any more. I had a mounted a SMB share using
/etc/fstab which appeared to be successfully unmounted prior to shutdown
(or at least, it didn't hang for a minute or so, it shut down
immediately).
--
You
Come on, a fix can't be done for this 4 years on? With all the various
workarounds people have put in above comments, surely one of them can
work for everyone?!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
Come on, a fix can't be done for this 4 years on?
In fact, between dbus and network-manager now waiting for the
'deconfiguring-networking' event before shutting down, and NM
registering its child processes with /run/sendsigs.omit.d to fix bug
#869635, I believe this should resolve the problem
wpasupplicant no longer includes an init script at all, so this task can
also be considered fixed.
** Changed in: wpasupplicant (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
Come on, a fix can't be done for this 4 years on? With all the various
workarounds people have put in above comments, surely one of them can
work for everyone?!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Come on, a fix can't be done for this 4 years on?
In fact, between dbus and network-manager now waiting for the
'deconfiguring-networking' event before shutting down, and NM
registering its child processes with /run/sendsigs.omit.d to fix bug
#869635, I believe this should resolve the problem
wpasupplicant no longer includes an init script at all, so this task can
also be considered fixed.
** Changed in: wpasupplicant (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** No longer affects: null
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before network filesystems are unmounted (CIFS
timeout at shutdown)
** No longer affects: null
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before network filesystems are unmounted (CIFS
timeout at shutdown)
To manage
another note:
The cifs mount are avalaible through vpn (in this case cisco vpn),
whenever the vpn connection is gone/disconnect,
but the remote drives still appear as mounted in mtab,
then
$umount --a -t cifs -l -f
takes a lot of time
HTH
--
You received this bug notification because you are
On Wed, Nov 02, 2011 at 12:31:00PM -, Gonzals, S. wrote:
The cifs mount are avalaible through vpn (in this case cisco vpn),
whenever the vpn connection is gone/disconnect,
but the remote drives still appear as mounted in mtab,
then
$umount --a -t cifs -l -f
takes a lot of time
Yep,
another note:
The cifs mount are avalaible through vpn (in this case cisco vpn),
whenever the vpn connection is gone/disconnect,
but the remote drives still appear as mounted in mtab,
then
$umount --a -t cifs -l -f
takes a lot of time
HTH
--
You received this bug notification because you are
On Wed, Nov 02, 2011 at 12:31:00PM -, Gonzals, S. wrote:
The cifs mount are avalaible through vpn (in this case cisco vpn),
whenever the vpn connection is gone/disconnect,
but the remote drives still appear as mounted in mtab,
then
$umount --a -t cifs -l -f
takes a lot of time
Yep,
This bug is disappeared for me (it started reapppearing a week ago), with
the changes in /etc/init/dbus.conf still in effect.
Maybe this has to do with my reinstall of grub2; after that, my computer
shuts again. This possinly indicates it has to do with certain boot options?
--
You received
This bug is disappeared for me (it started reapppearing a week ago), with
the changes in /etc/init/dbus.conf still in effect.
Maybe this has to do with my reinstall of grub2; after that, my computer
shuts again. This possinly indicates it has to do with certain boot options?
--
You received
Is the solution described in comment #143 and comment #147 really the
correct one?
In short, that means dbus always stops on the event deconfiguring-
networking, which is emitted when /etc/init.d/networking stop is
called.
In other words, whenever /etc/init.d/networking stop is called, dbus gets
On Sat, Oct 29, 2011 at 04:31:21PM -, Alonso Andres wrote:
Is the solution described in comment #143 and comment #147 really the
correct one?
No, it isn't; it just seems to be the best workaround anyone has proposed so
far.
In short, that means dbus always stops on the event
Is the solution described in comment #143 and comment #147 really the
correct one?
In short, that means dbus always stops on the event deconfiguring-
networking, which is emitted when /etc/init.d/networking stop is
called.
In other words, whenever /etc/init.d/networking stop is called, dbus gets
On Sat, Oct 29, 2011 at 04:31:21PM -, Alonso Andres wrote:
Is the solution described in comment #143 and comment #147 really the
correct one?
No, it isn't; it just seems to be the best workaround anyone has proposed so
far.
In short, that means dbus always stops on the event
On Wed, 2011-10-26 at 22:09 +, Ernst wrote:
Since a week or so, the shutdown is delayed again (on Ubuntu 11.10), despite
the script in dbus.conf. Does anyone has a solution for this?
the same on 10.4
also changing the shutdown, reboot (halt and poweroff) and restart
in /sbin
only works for
On Wed, 2011-10-26 at 22:09 +, Ernst wrote:
Since a week or so, the shutdown is delayed again (on Ubuntu 11.10), despite
the script in dbus.conf. Does anyone has a solution for this?
the same on 10.4
also changing the shutdown, reboot (halt and poweroff) and restart
in /sbin
only works for
Since a week or so, the shutdown is delayed again (on Ubuntu 11.10), despite
the script in dbus.conf. Does anyone has a solution for this?
On Mon, Oct 24, 2011 at 16:03, Gonzals, S.
211...@bugs.launchpad.netwrote:
i'll try that,
but,
i have never putted trailing slashes in the mointpoints,
Since a week or so, the shutdown is delayed again (on Ubuntu 11.10), despite
the script in dbus.conf. Does anyone has a solution for this?
On Mon, Oct 24, 2011 at 16:03, Gonzals, S.
211...@bugs.launchpad.netwrote:
i'll try that,
but,
i have never putted trailing slashes in the mointpoints,
I have the same problem:
on
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 10.04.3 LTS
Release:10.04
Codename: lucid
none of the these options worked for me, short:
- dbus.conf
- K14 links
- S31 earlier
- a modprobe option
Off topic, but the multiple mount can be caused if you miss trailing
slashes off the mountpoint in fstab
/media/myfsbad
/media/myfs/ good
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
i'll try that,
but,
i have never putted trailing slashes in the mointpoints,
and the double moutings only occus for the cifs ro mounts
mvg,
G
On Mon, 2011-10-24 at 12:50 +, Steve Sutton wrote:
Off topic, but the multiple mount can be caused if you miss trailing
slashes off the mountpoint
I have the same problem:
on
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 10.04.3 LTS
Release:10.04
Codename: lucid
none of the these options worked for me, short:
- dbus.conf
- K14 links
- S31 earlier
- a modprobe option
Off topic, but the multiple mount can be caused if you miss trailing
slashes off the mountpoint in fstab
/media/myfsbad
/media/myfs/ good
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/211631
i'll try that,
but,
i have never putted trailing slashes in the mointpoints,
and the double moutings only occus for the cifs ro mounts
mvg,
G
On Mon, 2011-10-24 at 12:50 +, Steve Sutton wrote:
Off topic, but the multiple mount can be caused if you miss trailing
slashes off the mountpoint
@jonbonjovi, @c0l2e did say :)
Put it in /etc/init/dbus.conf. You'll probably find an existing pre-
start/end script section in it (I did in mine). Just paste all the
lines (including the pre-stop and end script lines) into that file,
after the existing end script, or before the line that
@ Steve Sutton:
done! it works!
Thanx!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before network filesystems are unmounted (CIFS
timeout
@jonbonjovi, @c0l2e did say :)
Put it in /etc/init/dbus.conf. You'll probably find an existing pre-
start/end script section in it (I did in mine). Just paste all the
lines (including the pre-stop and end script lines) into that file,
after the existing end script, or before the line that
@ Steve Sutton:
done! it works!
Thanx!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before network filesystems are unmounted (CIFS
timeout at shutdown)
To
found a better fix via /etc/init/dbus.conf
add the pre-stop script:
pre-stop script
trap TERM signal TERM
/bin/umount -a -t cifs -f -l
trap - TERM
end script
It works for me and few tested notebooks and desktop PC.
--
You received this bug notification because you are a member
@c0l2e : Wow, thanks man! I can confirm that your fix works great on all
all systems as well (lucid).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought
Please read : on all *my* systems as well
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before network filesystems are unmounted (CIFS
@c0l2e: could you please provide a step-by-step explanation about how to make
your solution work?
Where should I put that text?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
found a better fix via /etc/init/dbus.conf
add the pre-stop script:
pre-stop script
trap TERM signal TERM
/bin/umount -a -t cifs -f -l
trap - TERM
end script
It works for me and few tested notebooks and desktop PC.
--
You received this bug notification because you are a member
@c0l2e : Wow, thanks man! I can confirm that your fix works great on all
all systems as well (lucid).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before
Please read : on all *my* systems as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before network filesystems are unmounted (CIFS
timeout at shutdown)
@c0l2e: could you please provide a step-by-step explanation about how to make
your solution work?
Where should I put that text?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network
After months of attempts to fix this, I've finally found one that works
for Kubuntu 11.04 (Natty). The problem is that Kubuntu (and I believe
KDE more generally) starts the shutdown process in a way different than
Gnome/Ubuntu, so even the dbus / netbase fixes, the fix above in #158,
and using
After months of attempts to fix this, I've finally found one that works
for Kubuntu 11.04 (Natty). The problem is that Kubuntu (and I believe
KDE more generally) starts the shutdown process in a way different than
Gnome/Ubuntu, so even the dbus / netbase fixes, the fix above in #158,
and using
I got a desperate workaround, it's in this link:
(http://hardc0l2e.wordpress.com/2011/06/30/ubuntu-11-04-shutdown-and-
restart-problem-with-cifs/). It works, but not the best way to deal with
this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have had this problem for a long time, in different ubuntu versions,
but this is the first time (Ubuntu 11.04) that I am unable to find a
workaround.
Before, I used to create a script that would umount the network drives
and place it at /etc/network/if-down.d. It used to work for Ubuntu
10.10,
Your options are :
1. Use a wired connection
2. Avoid Samba/CIFS shares and configure your server for NFS instead
3. Use AutoFS to create your network shares.
In case 3, AutoFS replaces the need to configure anything in /etc/fstab.
Seems to work well enough with most connections, although
The Upstart file I posted on #153 +autofs5 installed(very important)
solves it for me on 10.10. over wifi. Autofs has to be installed, or the
bug will stay. Today i found this is the working combo for me. You might
want to try this with Natty, i was planning in the next few days, too
tired today.
I have two machines running 11.04 with a wireless connection. I was able
to get a clean shutdown on both by changing the link to
/etc/init.d/umountnfs.sh in /etc/rc0.d and /etc/rc6.d from
S31umountnfs.sh to K15umountnfs.sh. This is a workaround, not a fix, as
it simply starts the cifs/nfs file
I have had this problem for a long time, in different ubuntu versions,
but this is the first time (Ubuntu 11.04) that I am unable to find a
workaround.
Before, I used to create a script that would umount the network drives
and place it at /etc/network/if-down.d. It used to work for Ubuntu
10.10,
Your options are :
1. Use a wired connection
2. Avoid Samba/CIFS shares and configure your server for NFS instead
3. Use AutoFS to create your network shares.
In case 3, AutoFS replaces the need to configure anything in /etc/fstab.
Seems to work well enough with most connections, although
The Upstart file I posted on #153 +autofs5 installed(very important)
solves it for me on 10.10. over wifi. Autofs has to be installed, or the
bug will stay. Today i found this is the working combo for me. You might
want to try this with Natty, i was planning in the next few days, too
tired today.
I have two machines running 11.04 with a wireless connection. I was able
to get a clean shutdown on both by changing the link to
/etc/init.d/umountnfs.sh in /etc/rc0.d and /etc/rc6.d from
S31umountnfs.sh to K15umountnfs.sh. This is a workaround, not a fix, as
it simply starts the cifs/nfs file
Hello
I got this bug on my Kubuntu 10.10 and 11.04 machine
Adding this conf file solved the problem for me on Kubuntu 10.10, but on 11.04
the bug is present even though the upstart job kicks off( the NAS is mounted)
Other described solutions for the bug, which used to work on 10.10 does not on
Hello
I got this bug on my Kubuntu 10.10 and 11.04 machine
Adding this conf file solved the problem for me on Kubuntu 10.10, but on 11.04
the bug is present even though the upstart job kicks off( the NAS is mounted)
Other described solutions for the bug, which used to work on 10.10 does not on
I still have a hang on reboot / shutdown even after installing the more
recent netbase (4.45ubuntu3) and dbus (1.4.8-3ubuntu2) packages on my
Kubuntu 11.04 laptop. I have four cifs shares defined in fstab. If I
shutdown or reboot, I see network-manager caught signal 15, then a
message about
I still have a hang on reboot / shutdown even after installing the more
recent netbase (4.45ubuntu3) and dbus (1.4.8-3ubuntu2) packages on my
Kubuntu 11.04 laptop. I have four cifs shares defined in fstab. If I
shutdown or reboot, I see network-manager caught signal 15, then a
message about
On a functional level perhaps it is worth considering whether Network
Manager, on stopping, should simply leave the interfaces as currently
configured instead of taking them down. I can make the argument that
Network Manager is a tool to make it easy for the user to control
network interfaces,
Good point!
Den 24 maj 2011 22.54 skrev bdoe brian...@att.net:
On a functional level perhaps it is worth considering whether Network
Manager, on stopping, should simply leave the interfaces as currently
configured instead of taking them down. I can make the argument that
Network Manager is a tool
Excerpts from bdoe's message of Tue May 24 20:54:25 UTC 2011:
On a functional level perhaps it is worth considering whether Network
Manager, on stopping, should simply leave the interfaces as currently
configured instead of taking them down. I can make the argument that
Network Manager is a
On a functional level perhaps it is worth considering whether Network
Manager, on stopping, should simply leave the interfaces as currently
configured instead of taking them down. I can make the argument that
Network Manager is a tool to make it easy for the user to control
network interfaces,
Good point!
Den 24 maj 2011 22.54 skrev bdoe brian...@att.net:
On a functional level perhaps it is worth considering whether Network
Manager, on stopping, should simply leave the interfaces as currently
configured instead of taking them down. I can make the argument that
Network Manager is a tool
Excerpts from bdoe's message of Tue May 24 20:54:25 UTC 2011:
On a functional level perhaps it is worth considering whether Network
Manager, on stopping, should simply leave the interfaces as currently
configured instead of taking them down. I can make the argument that
Network Manager is a
** Also affects: dhcdbd (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: network-manager (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: samba (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: sysvinit (Ubuntu
@Clint Byrum
How about we fix the bug for the next release instead of marking it as invalid?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down
Bug was rasied on 2008-04-04 and has 14 duplicates, yet this is somehow invalid?
I don't even use Ubuntu anymore because of silly issues like this.
What do we need to do to get action on this?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Excerpts from flaccid's message of Mon May 23 06:27:57 UTC 2011:
Bug was rasied on 2008-04-04 and has 14 duplicates, yet this is somehow
invalid?
I don't even use Ubuntu anymore because of silly issues like this.
What do we need to do to get action on this?
flaccid, its not Invalid as a bug,
** Also affects: netbase (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/211631
Title:
Network is brought down before network
1 - 100 of 206 matches
Mail list logo
