I can reproduce it on Lucid and Maverick under the following conditions:
- the network is a WLAN
- the connection is made by Network Manager or WICD
I don't know what the condition "net-device-up IFACE!=lo" in
/etc/init/nmbd.conf is really needed for. Can it be recommended to leave
it out and t
Not fixed for wireless network with WICD too !
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
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
I absolutely do agree with Tom and varanasi. This is a serious usability
problem that should be fixed as soon as possible!
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received this bug notification beca
I had already mentioned above: It's not only a network-manager problem
because it is exactly the same with WICD.
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you a
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
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
This annoying bug is known for a very long time now. I wonder why
nothing has been done yet!
--
CIFS/SMBFS shares not unmounted before network is shut down
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
> mv /etc/rc0.d/S31umountnfs.sh /etc/rc0.d/S14umountnfs.sh
> mv /etc/rc6.d/S31umountnfs.sh /etc/rc6.d/S14umountnfs.sh
This fix is a rather old thing; it had been published more than two
years ago.
I had asked here if this solution was correct and really safe, but I did
not get any answer yet!
Public bug reported:
Binary package hint: samba
Folders in my home directory can not be shared with guest access
permission, even if the acces mode is set to 0777. That is the case with
net usershare as well as with shares in /etc/samba/smb.conf. The
automatic adding of permissions in Nautilus d
What do you actually mean by "configuration section"? The few lines for
the share only or the [global] part also?
[Gemeinsam]
path = /home/farber/Gemeinsam
available = yes
browsable = yes
public = yes
writable = yes
The share is not accessible at all even if /home/farber/Gemeinsam is
set to mode
@ luchio
We are already waiting for years, and nothing did really happen. It is a
shame.
Even if it is far from being a perfect solution, it is better to propose
a workaround like the script of Scott Severance than to do just nothing.
--
CIFS/SMBFS shares not unmounted before network is shut do
@ Mathias Gug
Is that what you did need?
Perhaps that can help you: Public shares inside a directory (in this
case it is "/home/farber/") are possible only if the access to the
*whole* directory is allowed for everyone. This is not normal. It should
be enough to allow access to the share. It had
I am afraid the problem is that in this case nobody really feels
responsible. Is it a problem of the shutdown sequence (Ubuntu problem),
of the cifs Kernel module (Linux general) or a Samba bug? Who has got to
fix it?
As long as nobody feels responsible there is not much hope indeed.
--
CIFS/SM
I am sorry. I never wanted to speak for others. It is my opinion, but it
would be better if I had said nothing at all.
>considering scripts existed already and were simply executed at the
wrong stage of the shutdown sequence
Do these scripts really fix the problem? Please read the posting of Math
I can't understand that the importance of this bug is still set to "low"
in samba after such a long time!
--
CIFS/SMBFS shares not unmounted before network is shut down
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Ubuntu
Server Team, which
I am surprised that the status of this bug report is still "incomplete".
The bug must be known by the samba crew, because it is fixed in samba
3.2.3 implemented in Intrepid.
What I am asking for is to fix it in Hardy too because Hardy is LTS!
--
Public shares not possible in home folder (Hardy
I was not at home last week. Sorry for not answering sooner.
Thierry Carrez is right; the bug seemes to be fixed now. I have done
nothing else but installing the usual updates, and public shares now do
work in Hardy as well as in Intrepid.
Thanks, Max
--
Public shares not possible in home folde
I have the same problem, but I had never used Network Manager. I always
use WICD.
--
CIFS/SMBFS shares not unmounted before network is shut down
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 i
Thanks for this status update.
As Thuerry Carrez proposed, I tried to avoid system wide CIFS mounts via
fstab by monting my cifs shares manually with "mount.cifs ..." in my
home folder. The shutdown problem is still the same.
Using GNOME vfs pseudomounts is not a solution for me because the cifs
An other important reason is that gvfs does not support "cifs UNIX
Extensions" yet.
--
Network is brought down before network filesystems are unmounted (CIFS timeout
at shutdown)
https://bugs.launchpad.net/bugs/211631
You received this bug notification because you are a member of Ubuntu
Server
20 matches
Mail list logo
