This particular issue has been fixed. If you still experience the issue,
it's probably bug 211631. Please continue discussion there.
** Changed in: sysvinit (Ubuntu)
Status: Confirmed = Fix Released
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
Strange
Upgraded to Karmic and the issue is Gone for me.
Now I have a new bug never present before Karmic, From time to time the cifs
responds something about memory error and I have to restart the Windows 7
server :(
On Fri, Jan 8, 2010 at 7:51 AM, Dicr li...@dicr.org wrote:
This bug
This bug affect me too since I using wireless connections and permanent cifs
mounts in fstab.
But I think we need to fix it in upstart, not init.d.
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification
Fresh install of Karmic and the issue is still here.
Running on a wireless network.
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
In my fresh installation of Ubuntu Karmic the message isn't show, so i think
that was fixed.
But comment #58 need more investigation...
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are
I don't get the message CIFS VFS server not responding on shutdown any
more on the Ubuntu PC that I have upgraded to Karmic (and which have
cifs lines in /etc/fstab). So the bug seems to be fixed...
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
I did two clean installs with 9.10 karmic. In one of them, the problem
is solved, in the other one, the problem is still present. Since they
are both clean installs (no upgrades), it's ver odd. Maybe it has
something to do with the sequence in which fstab is modified and the
updates are downloaded
This bug is still affecting Karmic Alpha 4 with network-manager
0.8~a~git.20090804t185522.4bab334-0ubuntu1
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs, which
I'd just like to confirm that this is still an issue.
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
** Changed in: sysvinit (Debian)
Status: Fix Released = Confirmed
** Changed in: sysvinit (Debian)
Status: Confirmed = Fix Released
** Changed in: sysvinit (Ubuntu)
Status: New = Confirmed
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
** Changed in: sysvinit (Ubuntu)
Assignee: Martin Pitt (pitti) = (unassigned)
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
i'm using 9.04 and i get the same error
however the bug is still marked as Fix released and the original bug brought
VPN into account. i don't use VPN. just a samba shared mounted on /etc/fstab
from another ubuntu box
should we open a new bug report?
--
Symlinks for umountnfs / sendsigs wrong:
This has not been fixed
** Changed in: sysvinit (Ubuntu)
Status: Fix Released = New
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
Confirming here to.
Release:9.04
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
Problem still exists in Jaunty (9.04) with CIFS mounts.
Renaming the links from S to K solved it for me (maintaining the same order
number).
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you
i get cifs vfs server not responding on shutdown of my system with
cifs lines in fstab, in 9.04
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
I'm running Jaunty 9.04 now, and I just followed what I followed for
intrepid
(https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/42121/comments/44),
and the manual hack/fix works fine still for me.
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
NOTE: As keppy has mentioned, I can confirm that the bug is still
present for 9.04.
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
Confirming still present in UNR 9.04. If it helps any, none of the
proposed fixes work for me. Moving S31umountnfs.sh to K31umountnfs.sh
or S14umountnfs.sh does not work. Please let me know if any info more
info is needed.
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
Bug still present in Jaunty Jackalope. It doesn't unmount my CIFS shares
when I am shutting down my laptop.
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs,
Is this definitely the same bug as #153444 ?
This claims to have a fix released, but I've also just reproduced it in
Intrepid. Perhaps they are separate bugs, and #153444 is really the one
I'm experiencing as it contains the message that I'm seeing?
--
Symlinks for umountnfs / sendsigs wrong:
Confirmed. This bug still exists in the final release of Intrepid Ibex
(8.10).
Followed the helpful tips from:
http://www.jejik.com/articles/2007/07/automatically_mounting_and_unmounting_samba_windows_shares_with_cifs/
to resolve.
However, of course, this needs to be fixed in the main so that
I've got the same problem as psypher here on a Intrepid machine. What
shall we do? The time out isn't fixed by the umountcifs script called at
K01, K12,K19 or K20. (At least not *always*).
@psypher Did you already file a new report?
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown /
On Tue, 2008-11-11 at 05:37 +, psypher wrote:
Scott, what does fix released mean when this bug is still present in the
latest version of intrepid?
It means that while you might be seeing similar symptoms, it is not the
same as this bug - and you should file a new one.
Scott
--
Scott
ok but what is the exact problem then, since the symptoms are exactly
the same and have not changed since gutsy. how do i figure out where the
problem is when the same solution that has worked for 3 different
editions of ubuntu is still the solution?
--
Symlinks for umountnfs / sendsigs wrong:
On Mon, 2008-11-10 at 10:06 +, psypher wrote:
more than 2 years and 3 different editions of ubuntu and this bug is
STILL!!! present.
This bug is marked Fix Released.
Scott
--
Scott James Remnant
[EMAIL PROTECTED]
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
SERIOUSLY?!?!?!?!
more than 2 years and 3 different editions of ubuntu and this bug is
STILL!!! present.
I can confirm that daniel ellis' script fixes it.
this makes me VERY worried about the direction Ubuntu is going. Every
new version all these fancy new things are added (gvfs pulseaudio...
This is the same issue as reported in Bug #211631. Reinhard Tartler
says there that he may not have fully understood the problem, so his Fix
Committed here may not be addressing the issue reported here.
See Mathias Gug's comments in Bug #211631:
The issue discussed here boils down to the fact
Scott, what does fix released mean when this bug is still present in the
latest version of intrepid?
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
This is still a bug, but it's not in sysvinit. Renaming S31umountnfs to
K31umountnfs might help not because S31umountnfs is called with start
(everything is called with stop for rc0.d and rc6.d), but because it
simply happens earlier in the shutdown sequence.
This is most probably a problem with
Re-opening due to reports that the bug is still present.
** Changed in: sysvinit (Ubuntu)
Status: Fix Released = Confirmed
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a
Bug is stilll present in Intrepid Beta dated 2008-10-24.
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
Correction, the workaround is not working after all. Still hangs on
shutdown with the CIFS Server not responding error
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of
I can confirm both this bug and the workaround in intrepid beta:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/42121/comments/26
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you
Apparently K is coming first then S. I've it with K12 now, but still not
working
lrwxrwxrwx 1 root root 13 2008-05-21 18:18 K01gdm - ../init.d/gdm
lrwxrwxrwx 1 root root 17 2007-01-19 03:20 K01usplash - ../init.d/usplash
lrwxrwxrwx 1 root root 22 2008-07-26 14:19 K12umountcifs -
To eliminate CIFS mounts you only have to do this:
cd /etc/rc6.d
ls -la
Type:
sudo mv S31umountnfs.sh S14umountnfs.sh
then cd to rc6.0
type the same line as before.
That should fix the problem.
That 2 steps is the ONLY thing you have to do after installing ubuntu.
Daniel
On Sat, Jul 26,
I've done that on both rc0.d and rc6.d, it doesn't work for me
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
oo I just see you mentioned S14 and not K14, what's the difference btw?
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
I'm confused :-) I do have S14 and not S14...still it's not working. I
also don't konw the difference to S and K
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs,
On Sun, Jul 27, 2008 at 1:39 PM, Ralph Wabel [EMAIL PROTECTED] wrote:
I'm confused :-) I do have S14 and not S14...still it's not working. I
also don't konw the difference to S and K
I moved from S31 or 32, whichever it was, to K13 in rc0.d/ and rc6.d/
Works fine for me, Ubuntu Feisty and
I've now tried all possibilities I've found on forums and by googling,
still I always get this error message and my pc is not
shutting/restarting. I need to poweroff my pc.
When I start the script manually, it unmounts my cifs and I can
successfully restart or shutdown my pc
Quote:
[EMAIL
I am not sure how this will fix the issue on a default Ubuntu 8.04
installation. Both my desktop and my laptop suffer from not shutting
down after adding a cifs mount. I have been using the following script
to patch my 7.10 and 8.04 installations and the machines shutdown fine:-
This bug was fixed in the package sysvinit - 2.86.ds1-56ubuntu1
---
sysvinit (2.86.ds1-56ubuntu1) intrepid; urgency=low
* Merge with Debian unstable (first time since Dapper!). Debian adopted most
of our changes, sometimes with slight modifications. Adopt to the Debian
Yes, totally agree, also, I reported this bug a while ago, when hardy was in
beta stage, this could had being easily patched, there are a lot of us that
are using cifs shares, this is not a minor issue.
On Thu, May 8, 2008 at 5:39 PM, Peter Schneider [EMAIL PROTECTED]
wrote:
I can confirm this
The fix provided Teih Han Hui quicky fix it for me (hardy heron final),
it's a shame it wans't included being so easy to implement, just a change in
the RC order.
On Wed, May 7, 2008 at 1:29 AM, Laurent Dinclaux [EMAIL PROTECTED]
wrote:
problem still present in hardy at time of writing
--
I can confirm this was still an issue for me on my laptop with Hardy
final. I fixed this by renaming S31umountnfs.sh to S18umountnfs.sh in
/etc/rc6.d and /etc/rc0.d. It would have been nice if this could have
been included in the final release, since a quick google search shows
this is still
problem still present in hardy at time of writing
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
This looks like a more promising fix:
http://blog.avirtualhome.com/2008/03/10/ubuntu-shutdown-problem-cifs-
related/
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
I did not experienced any boot problems after applying the Patch.
The problem is more serious without the Patch than with it, because
basically, if you do not apply this patch, shutdown hangs waiting and you
have to manually shut down the pc or reset which is dangerous.
It should be an
Sorry, got confused with another bug number
I was referring to THIS patch
https://bugs.launchpad.net/bugs/153444
I did not try the sysvinit
the aparent problem with closing network CIFS shares is present here:
https://bugs.launchpad.net/bugs/153444
The problem seems related to the way
@Reinhard : How are we to apply the patch/fix you provided to sysvinit
in Hardy if it conflicts with upstart?
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs,
I have also observed this bug a few times when trying to hibernate with
a share that has dropped without being unmounted first. Because of the
long delay during whatever process is happening to generate the error
messages, hibernate fails due to processes not shutting down.
(Hibernate will work
Confirming this is still also a bug in Ubuntu Hardy Beta and related to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/153444
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a
Confirming the bug in Kubuntu Hardy Heron Beta.
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
Confirming that this is still an issue in Ubuntu Hardy Alpha 5 (i386).
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
Did this fix make hardy? Putting a failure message up after usplash
stops doesn't seem too user friendly.
BTW, my main network connection is wireless, so I fixed it on my system
by unmounting cifs and smbfs filesystems just before S15wpa-ifupdown
runs by creating a script based on S40umountfs
bug #181541 contains a patch which could give the base for fixing this
bug.
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
I am eperiencing the same issue, but only if the network has been
started in runlevel 5 by Network Manager or Wicd. If the network has
been configured manualy and therefore is started in runlevel 2, there is
no shutdown problem even with cifs mounts.
--
Symlinks for umountnfs / sendsigs wrong:
I can confirm this bug is still present in Ubuntu 7.10 Gutsy.
However, a minute or so after the message the computer usually shuts down
anyway.
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because
** Changed in: sysvinit (Debian)
Status: Unknown = Fix Released
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
** Summary changed:
- Looks like symlinks for umountnfs and umoutfs is wrong
+ Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
--
Symlinks for umountnfs / sendsigs wrong: hang on shutdown / reboot
https://bugs.launchpad.net/bugs/42121
You received this bug notification
61 matches
Mail list logo
