I think the reason that moving S31umountnfs.sh to K14umountnfs.sh
addresses the problem because there is now a dhcdbd script at K16dhcdbd
which takes DHCP connections down much earlier than it should.
So I believe that in addition to the wpasupplicant bug, we have a bug in
dhcdbd; both of these ru
I fix it on my system too changing the order umountnfs executes on inits
0 and 6 and think it may no have any problems as it says not root
neither top levels mounts are unmount (the ones system need to continue
shutdown properly):
# Short-Description: Unmount all network filesystems except the roo
I agree with flaccid: This perpetuating and ennoying bug should be fixed
as soon as possible!
That has even become more important with Hardy, since "smbfs" does not
exist as a workaround any more, "smbmount" being nothing more than a
wrapper for "mount.cifs".
The simple solution proposed in the l
Please fix this perpetuating bug, there are quite a few solutions noted,
the simplest being http://whereofwecannotspeak.wordpress.com/2007/12/25
/unmount-samba-filesystems-before-shutdown-or-reboot/
I believe there are also duplicate bugs.
--
CIFS/SMBFS issue (was not resolved on #207441)
https:
This is a very old and well known problem. See also
http://ubuntuforums.org/showthread.php?t=772774 and
http://ubuntuforums.org/showthread.php?t=293513&highlight=cifs+vfs
I wonder why this bug is not fixed yet!
It has been proposed to change S31umountnfs.sh to K14umountnfs.sh in
/etc/rc0.d and /e
This bug occurred for me on 7.04. Yesterday I upgraded to 8.04 through
7.10, and the problem still exists. Haven't yet tried the workaround I
mentioned, but I'm fairly sure it will work, since manual unmounting
fixes/works around it. FYI, my reports are just for logging off, haven't
seen any proble
I don't know if this bug is related to #212019, but the unmounting
problem exists for me on a machine with no wifi-capabilities. I'm about
to try http://ubuntuforums.org/showthread.php?t=293513 as a fix tonight,
but that sounds like a workaround rather than a solutioni.
--
CIFS/SMBFS issue (was n
I am commenting here to keep this thread alive, and wondering if any of
the wpasupplicant team are looking at it? More than happy to keep
experimenting and chatting about it! Thanks.
Hamish
--
CIFS/SMBFS issue (was not resolved on #207441)
https://bugs.launchpad.net/bugs/211631
You received this
Hi Steve
I have changed wpa-ifupdown to S41 for both rc0.d and rc6.d, but I still
get the problem.
[EMAIL PROTECTED]:/etc/rc0.d$ ls
K01gdm K30squidS30urandom
K01usplash K39ufw S31umountnfs.sh
K16dhcdbdK50alsa-utils
The last part of this is a wpasupplicant bug. The ordering of the
shutdown scripts is already well-established, and unmounting remote
filesystems takes place at S31 (S31umountnfs.sh). wpasupplicant needs
to be fixed to run its shutdown script later than this; probably at S35
or S36, which is the
Hi Chuck
I can umount and re- mount the shares using the command line (sudo
umount -a and sudo mount -a) and it works successfully. I get nautilus
sessions opening for each mounted drive every time I do this, which is
very annoying!
I can do the following:
[EMAIL PROTECTED]:~$ sudo mount -t cifs
Do you get the same error when you mount the share using the command
line?
chuck
--
CIFS/SMBFS issue (was not resolved on #207441)
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
lspci -vvnn
** Attachment added: "lspci -vvnn"
http://launchpadlibrarian.net/13194770/lspci.txt
--
CIFS/SMBFS issue (was not resolved on #207441)
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to s
...although I have included the error message in the original
description above:
CIFS VFS: server not responding
CIFS VFS: no response for cmd 50 mid
eventually after 2-3 minutes this times out and the computer restarts,
but it isn't really good enough
Hamish
--
CIFS/SMBFS issue (was not reso
dmesg
look for"
[ 62.697883] CIFS VFS: Error connecting to IPv4 socket. Aborting operation
[ 62.697948] CIFS VFS: cifs_mount failed w/return code = -101
then after that wlan0 is configured
i think the timing of these operations is the problem
how do i get the shutting down logs so I can s
/var/log/messages from last startup
[EMAIL PROTECTED]:~$ uname -r
2.6.24-15-generic
** Attachment added: "/var/log/messages"
http://launchpadlibrarian.net/13194682/messages%20log.txt
--
CIFS/SMBFS issue (was not resolved on #207441)
https://bugs.launchpad.net/bugs/211631
You received this b
Is there anything in the logs about your connection?
Thanks
chuck
** Changed in: samba (Ubuntu)
Status: New => Incomplete
--
CIFS/SMBFS issue (was not resolved on #207441)
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Ubuntu
Server
** Description changed:
I installed smbfs, and then put some entries into /etc/fstab, so they
automount on startup. An example of this is here:
/// /home/hamish/ cifs
credentials=/home/hamish/.smbcredentials,file_mode=0777,dir_mode=0777,uid=1000,gid=1000
0 0
** note the use of "ci
18 matches
Mail list logo
