Filed bug 341084 to discuss usage of umount -i rather than umount in
umountnfs.sh. Please followup there.
Updating other status: Nothing to fix in samba or dhcdbd, something to
fix in network-manager, and maybe something to fix in wpasupplicant.
** Changed in: sysvinit (Ubuntu)
Status:
@toobuntu:
The _netdev option tells the system (if it doesn't already knows it from the
fstype) that the filesystem should be considered mounted on network (and
therefore be unmounted in umountnfs.sh rather than umountfs).
@Steve Greci (Seems when tracking down the cause of one bug, I encounter
Filed bug 341084 to discuss usage of umount -i rather than umount in
umountnfs.sh. Please followup there.
Updating other status: Nothing to fix in samba or dhcdbd, something to
fix in network-manager, and maybe something to fix in wpasupplicant.
** Changed in: sysvinit (Ubuntu)
Status:
@toobuntu:
The _netdev option tells the system (if it doesn't already knows it from the
fstype) that the filesystem should be considered mounted on network (and
therefore be unmounted in umountnfs.sh rather than umountfs).
@Steve Greci (Seems when tracking down the cause of one bug, I encounter
Thierry, please extend your approach to not kill wpasupplicant on
shutdown either. i think thats the problem that is left with your ppa
packages here as the ones reporting that your ppa package doesnt help
are using wireless.
Once you have that please request a merge for the 0.7.1 branch and if
Thierry, please extend your approach to not kill wpasupplicant on
shutdown either. i think thats the problem that is left with your ppa
packages here as the ones reporting that your ppa package doesnt help
are using wireless.
Once you have that please request a merge for the 0.7.1 branch and if
I think I also need to clarify something here.
If you use NetworkManager with per-user settings (i.e. without the
system setting checkbox checked) then the network connection is up
only during your session. When you log out from your Gnome session, the
network connection goes down. This is the
@Thierry Carrez:
For use case #3, isn't that what the '_netdev' mount option is for? In
my fstab, I always use '_netdev' for a network share; I think RedHat
considers it a best practice. One could also combine that with 'noauto'
and 'user'. The problem with gvfs-smb mounts is that non-gvfs
Thanks for the clarification Thierry. Unfortunately I cannot use it
wireless as a system wide setting due to bug #288963 which doesn't have
an intrepid backport. Seems when tracking down the cause of one bug, I
encounter 3 more to that need to be fixed in order to solve it. :)
Maybe I should
OK ... doing a little more investigation it gets interesting to see what
crazy things gnome does (you can also try clearing the dmesg log and
then doing echo 7 /proc/fs/cifs/cifsFYI before you logoff/umount and
see what cifs operations are in dmesg)
What I see is that the slow operations are
running without umount.cifs (which is not needed unless you are doing
user mounts), the unmount finishes quickly, and with no visible errors
(the tree disconnection request times out fairly fast, and the rest of
umount proceeds fast after that)
--
CIFS/SMBFS shares not unmounted before network
The easiest way to test this is to always do umount -i mnt-point
rather than umount mnt-point unless you are doing an umount as a
regular user of a user mount (-i prevents the unneeded helper program
from being called)
--
CIFS/SMBFS shares not unmounted before network is shut down
Hi Thierry,
Thierry Carrez wrote:
I am trying to solve the bug in the (2) case here. If you are in the
(3) case (and a lot of you probably are) you should either switch to
system setting mode or drop usage of CIFS mounts in favor of
Nautilus gvfs-smb mounts.
Thanks very much for the detailed
I think I also need to clarify something here.
If you use NetworkManager with per-user settings (i.e. without the
system setting checkbox checked) then the network connection is up
only during your session. When you log out from your Gnome session, the
network connection goes down. This is the
@Thierry Carrez:
For use case #3, isn't that what the '_netdev' mount option is for? In
my fstab, I always use '_netdev' for a network share; I think RedHat
considers it a best practice. One could also combine that with 'noauto'
and 'user'. The problem with gvfs-smb mounts is that non-gvfs
Thanks for the clarification Thierry. Unfortunately I cannot use it
wireless as a system wide setting due to bug #288963 which doesn't have
an intrepid backport. Seems when tracking down the cause of one bug, I
encounter 3 more to that need to be fixed in order to solve it. :)
Maybe I should
OK ... doing a little more investigation it gets interesting to see what
crazy things gnome does (you can also try clearing the dmesg log and
then doing echo 7 /proc/fs/cifs/cifsFYI before you logoff/umount and
see what cifs operations are in dmesg)
What I see is that the slow operations are
running without umount.cifs (which is not needed unless you are doing
user mounts), the unmount finishes quickly, and with no visible errors
(the tree disconnection request times out fairly fast, and the rest of
umount proceeds fast after that)
--
CIFS/SMBFS shares not unmounted before network
The easiest way to test this is to always do umount -i mnt-point
rather than umount mnt-point unless you are doing an umount as a
regular user of a user mount (-i prevents the unneeded helper program
from being called)
--
CIFS/SMBFS shares not unmounted before network is shut down
Hi Thierry,
Thierry Carrez wrote:
I am trying to solve the bug in the (2) case here. If you are in the
(3) case (and a lot of you probably are) you should either switch to
system setting mode or drop usage of CIFS mounts in favor of
Nautilus gvfs-smb mounts.
Thanks very much for the detailed
Thierry, I just installed your ppa network-manager packages on Intrepid,
and it's still hanging on shutdown (using wireless) with CIFS VFS
errors. A fairly fresh UMPC install on a Dell Mini 9.
I ran a continuous ping on the machine and network is unavailable nearly
immediately after selecting
Thierry Carrez wrote:
OK, I uploaded a network-manager upgrade for intrepid to my PPA:
https://launchpad.net/~ttx/+archive/ppa
This release (built on the latest network-manager in intrepid-proposed)
basically prevents network-manager from being shut down by sendsigs...
From my testing this
Hi Steve,
Steve Grecni wrote:
Thierry, I just installed your ppa network-manager packages on Intrepid,
and it's still hanging on shutdown (using wireless) with CIFS VFS
errors. A fairly fresh UMPC install on a Dell Mini 9.
I ran a continuous ping on the machine and network is unavailable
Hi Steve,
Steve French wrote:
A couple clarifications:
1) We really want the network file systems
to be unmounted (or at least synced) before the network goes away.
You do not want to risk losing file system data which has been cached
by the Linux memory management layer.
2) If there is
Bart Samwel wrote:
Would it help to sync before I reboot
from the GUI, so that all pending dirty data is flushed to the cifs fs?
For the record: nope, that doesn't help. Still hangs.
--
CIFS/SMBFS shares not unmounted before network is shut down
https://bugs.launchpad.net/bugs/211631
You
Things get even weirder, if I select logout from the gnome panel,
network goes away, so I log back in as the same user, and network comes
back as expected. But if I log out again, network stays up! Tried
logging out again, network still stays up.
I noticed, if I log out, and then back in, then
Thierry, I just installed your ppa network-manager packages on Intrepid,
and it's still hanging on shutdown (using wireless) with CIFS VFS
errors. A fairly fresh UMPC install on a Dell Mini 9.
I ran a continuous ping on the machine and network is unavailable nearly
immediately after selecting
Thierry Carrez wrote:
OK, I uploaded a network-manager upgrade for intrepid to my PPA:
https://launchpad.net/~ttx/+archive/ppa
This release (built on the latest network-manager in intrepid-proposed)
basically prevents network-manager from being shut down by sendsigs...
From my testing this
Hi Steve,
Steve Grecni wrote:
Thierry, I just installed your ppa network-manager packages on Intrepid,
and it's still hanging on shutdown (using wireless) with CIFS VFS
errors. A fairly fresh UMPC install on a Dell Mini 9.
I ran a continuous ping on the machine and network is unavailable
A couple clarifications:
1) We really want the network file systems to be unmounted (or at least synced)
before the network goes away. You do not want to risk losing file system data
which has been cached by the Linux memory management layer.
2) If there is cached write data, we do want the
Hi Steve,
Steve French wrote:
A couple clarifications:
1) We really want the network file systems
to be unmounted (or at least synced) before the network goes away.
You do not want to risk losing file system data which has been cached
by the Linux memory management layer.
2) If there is
Bart Samwel wrote:
Would it help to sync before I reboot
from the GUI, so that all pending dirty data is flushed to the cifs fs?
For the record: nope, that doesn't help. Still hangs.
--
CIFS/SMBFS shares not unmounted before network is shut down
https://bugs.launchpad.net/bugs/211631
You
Things get even weirder, if I select logout from the gnome panel,
network goes away, so I log back in as the same user, and network comes
back as expected. But if I log out again, network stays up! Tried
logging out again, network still stays up.
I noticed, if I log out, and then back in, then
Just refreshed my PPA (a security update superseded it), please test:
0.7~~svn20081018t105859-0ubuntu1.8.10.3~ppa1
@Max-Ulrich Farber:
I guess WICD has the same bug as NetworkManager (gets killed by sendsigs before
the network filesystems are unmounted). If testing shows that the solution for
Just refreshed my PPA (a security update superseded it), please test:
0.7~~svn20081018t105859-0ubuntu1.8.10.3~ppa1
@Max-Ulrich Farber:
I guess WICD has the same bug as NetworkManager (gets killed by sendsigs before
the network filesystems are unmounted). If testing shows that the solution for
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
OK, I uploaded a network-manager upgrade for intrepid to my PPA:
https://launchpad.net/~ttx/+archive/ppa
This release (built on the latest network-manager in intrepid-proposed)
basically prevents network-manager from being shut down by sendsigs...
From my testing this solves the CIFS hanging
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
Bugs, which is subscribed to Ubuntu.
--
Quick status update/summary on this bug, because this thread is long and
tends to discourage people that could solve it.
The bug occurs on shutdown if you mount a CIFS share (using mount or
/etc/fstab). In some cases, S31umountnfs.sh tries to unmount the network
file system *after* the network
smfrench:
Could you have a look at the CIFS timeout part ? Do you think it's possible to
have CIFS more gracefully handle the case where the network is being pulled out
from under it ? I can reproduce the issue with the current jaunty kernel, so
this wasn't fixed as of the 2.6.28 we use. Or
Quick status update/summary on this bug, because this thread is long and
tends to discourage people that could solve it.
The bug occurs on shutdown if you mount a CIFS share (using mount or
/etc/fstab). In some cases, S31umountnfs.sh tries to unmount the network
file system *after* the network
smfrench:
Could you have a look at the CIFS timeout part ? Do you think it's possible to
have CIFS more gracefully handle the case where the network is being pulled out
from under it ? I can reproduce the issue with the current jaunty kernel, so
this wasn't fixed as of the 2.6.28 we use. Or
This bug is causing usplash to crap-out on shutdown and display a nice screen
of vertical coloured lines, as reported in this bug:
https://bugs.launchpad.net/ubuntu/+source/usplash/+bug/301628
usplash shows the coloured lines at exactly the same time as the CIFS
error messages are shown in
This bug is causing usplash to crap-out on shutdown and display a nice screen
of vertical coloured lines, as reported in this bug:
https://bugs.launchpad.net/ubuntu/+source/usplash/+bug/301628
usplash shows the coloured lines at exactly the same time as the CIFS
error messages are shown in
This is disheartening to see that this bug has been around this long and
nothing has happened. I have been dealing with it for a while and
finally stumbled across it. I found a fix once before that I can't even
remember now and I can at least suspend only to find that when I wake my
laptop up on
This is disheartening to see that this bug has been around this long and
nothing has happened. I have been dealing with it for a while and
finally stumbled across it. I found a fix once before that I can't even
remember now and I can at least suspend only to find that when I wake my
laptop up on
One thing I only just figured out: if you are using the umountcifs script
linked above, you also need to set the network as a system setting, otherwise
it's pulled down when you exit KDE/Gnome and still leaves the umount hanging
during shutdown/reboot.
I made sure network-manager-gnome was
One thing I only just figured out: if you are using the umountcifs script
linked above, you also need to set the network as a system setting, otherwise
it's pulled down when you exit KDE/Gnome and still leaves the umount hanging
during shutdown/reboot.
I made sure network-manager-gnome was
@wolfi...@gmail.com
I agree of course. You just described the Ubuntu project!
The thing is people solve Launchpad Ubuntu bugs all the time. The problem is
the managers of the distro. The other problem is how hard it is to get a fix
committed.
This is not the only example of where I have done
I also did the right thing and reported this bug in one of the reports
that was marked as a duplicate. Yes it is frustrating to see bugs take
so long to get fixed, and ultimately lack of a positive result teaches
users to give up bothering to file bug reports. That's not a good
thing, as it
@bopb
I'm not sure that your closing point has much relevence to completing this bug.
It merely suggests you accept the mediocrity of the situation. Of course the
situation could be much worse than this, thats just stating the obvious. This
does not mean its acceptable.
Oh and there are many
Until this is fixed, what can we as a user community do to help
mitigate the annoyances caused by this bug? Would it be sufficient to
describe the issue and various workarounds in the relevant places in the
community documentation? Maybe here...
https://help.ubuntu.com/community/Fstab
@complainers:
Complaining about Ubuntu's bug-fixing process won't get this bug fixed any
quicker. It just fills people's inboxes with useless drivel. Let's keep the
discussion on-topic, shall we?
--
CIFS/SMBFS shares not unmounted before network is shut down
Let the inboxes be filled until it is committed!
--
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 in ubuntu.
--
@wolfi...@gmail.com
I agree of course. You just described the Ubuntu project!
The thing is people solve Launchpad Ubuntu bugs all the time. The problem is
the managers of the distro. The other problem is how hard it is to get a fix
committed.
This is not the only example of where I have done
I also did the right thing and reported this bug in one of the reports
that was marked as a duplicate. Yes it is frustrating to see bugs take
so long to get fixed, and ultimately lack of a positive result teaches
users to give up bothering to file bug reports. That's not a good
thing, as it
@bopb
I'm not sure that your closing point has much relevence to completing this bug.
It merely suggests you accept the mediocrity of the situation. Of course the
situation could be much worse than this, thats just stating the obvious. This
does not mean its acceptable.
Oh and there are many
Until this is fixed, what can we as a user community do to help
mitigate the annoyances caused by this bug? Would it be sufficient to
describe the issue and various workarounds in the relevant places in the
community documentation? Maybe here...
https://help.ubuntu.com/community/Fstab
@complainers:
Complaining about Ubuntu's bug-fixing process won't get this bug fixed any
quicker. It just fills people's inboxes with useless drivel. Let's keep the
discussion on-topic, shall we?
--
CIFS/SMBFS shares not unmounted before network is shut down
Let the inboxes be filled until it is committed!
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
And what if Networkmanager be protected from beeing killed in sendsig
and network beeing brought down at end of shutdown ?
--
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
Ok that's it; I'm done with this. Just a waste of time.. All talk 'n no action.
I'll just use one of the suggested fixes. If that doesn't work I'll have a big
sticky note saying Remember to unmount your Samba shares!.
The problem is known; Several solutions are known; but just keep dragging
And what if Networkmanager be protected from beeing killed in sendsig
and network beeing brought down at end of shutdown ?
--
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
Ok that's it; I'm done with this. Just a waste of time.. All talk 'n no action.
I'll just use one of the suggested fixes. If that doesn't work I'll have a big
sticky note saying Remember to unmount your Samba shares!.
The problem is known; Several solutions are known; but just keep dragging
So I've read through this entire thread and seen a lot of solutions. I have a
fully updated intrepid and this line appears at shutdown (take out the splash
line in your kernel command in grub to see it) :
CIFS VFS: No response for ..
basically the same as the original report.
CIFS VFS:
So I've read through this entire thread and seen a lot of solutions. I have a
fully updated intrepid and this line appears at shutdown (take out the splash
line in your kernel command in grub to see it) :
CIFS VFS: No response for ..
basically the same as the original report.
CIFS VFS:
Ubuntu - too many indians, no chiefs. Oh there are chiefs but they must
be too busy smoking crack.
--
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
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
Bugs, which is
Ubuntu - too many indians, no chiefs. Oh there are chiefs but they must
be too busy smoking crack.
--
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
Bugs, which is subscribed
I just think it's a laugh, a linux distribution that can't cope with
either NFS or CIFS mounts. See below for details:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/213444
Yes and I need to mount a resource both by NFS and CIFS . . .
It can't all be blamed on bug 1 - MS don't
I just think it's a laugh, a linux distribution that can't cope with
either NFS or CIFS mounts. See below for details:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/213444
Yes and I need to mount a resource both by NFS and CIFS . . .
It can't all be blamed on bug 1 - MS don't
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
@Max-Ulrich Farber
What Mathias Gug was suggesting may be a better solution however not the
current method that Ubuntu employs in its [shutdown] scripts.
Considering how hard it is to get the other fixes committed as a
solution (which do work, I have tested and so have others), I would
assume
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
@Max-Ulrich Farber
What Mathias Gug was suggesting may be a better solution however not the
current method that Ubuntu employs in its [shutdown] scripts.
Considering how hard it is to get the other fixes committed as a
solution (which do work, I have tested and so have others), I would
assume
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.
--
@Max-Ulrich Farber
I disagree and I don't think you can speak for others like that.
Considering the Linux kernel and Samba itself are shared between
hundreds of Linux distributions and that Samba is basically the same (in
this context) on other operating systems such as FreeBSD etc., it is
clear
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.
--
@Max-Ulrich Farber
I disagree and I don't think you can speak for others like that.
Considering the Linux kernel and Samba itself are shared between
hundreds of Linux distributions and that Samba is basically the same (in
this context) on other operating systems such as FreeBSD etc., it is
clear
Why isn't this fixed after so long? The big thing keeping me from
switching to Linux full time is that i run into these type of bugs, and
no sooner do i get them fixed and feel like i've made progress that
ANOTHER bug shows up. The more I want to do with my system, the more
bugs I need to find
I think the problem lies with the lack of action on behalf of people with power
to commit fixes such as Canonical sponsors.
I gave up on Ubuntu's management a long time ago. Where are the chiefs?
--
CIFS/SMBFS shares not unmounted before network is shut down
Why isn't this fixed after so long? The big thing keeping me from
switching to Linux full time is that i run into these type of bugs, and
no sooner do i get them fixed and feel like i've made progress that
ANOTHER bug shows up. The more I want to do with my system, the more
bugs I need to find
I think the problem lies with the lack of action on behalf of people with power
to commit fixes such as Canonical sponsors.
I gave up on Ubuntu's management a long time ago. Where are the chiefs?
--
CIFS/SMBFS shares not unmounted before network is shut down
@ 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
@ 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
@Mathias Gug
So, what do you suggest should happen now? Submit a bug report to samba
and wait for them?
--
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
@Mathias Gug
So, what do you suggest should happen now? Submit a bug report to samba
and wait for them?
--
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
Bugs, which is
In case anyone cares, my initial testing using this method has been very
successful so far, both shutdown/restart and suspend/resume are working
as I expect. Would be possible to have Canonical officially embrace and
include this script in the Ubuntu base packaging and close out this
issue once
The issue discussed here boils down to the fact that network interfaces
can be brought down *before* network filesystems are unmounted thus
leading to a long timeout.
One option proposed was to move the umountnfs script earlier in the
shutdown sequence. Doing leads to the possibility that running
In case anyone cares, my initial testing using this method has been very
successful so far, both shutdown/restart and suspend/resume are working
as I expect. Would be possible to have Canonical officially embrace and
include this script in the Ubuntu base packaging and close out this
issue once
The issue discussed here boils down to the fact that network interfaces
can be brought down *before* network filesystems are unmounted thus
leading to a long timeout.
One option proposed was to move the umountnfs script earlier in the
shutdown sequence. Doing leads to the possibility that running
For our network using Ubuntu 8.04, Sander Marechal's umountcifs script
works when symlinked as K15umountcifs (i.e. the key is that it is called
prior to K16dhcdbd).
$ sudo ln -s /etc/init.d/umountcifs /etc/rc0.d/K15umountcifs
$ sudo ln -s /etc/init.d/umountcifs /etc/rc6.d/K15umountcifs
--
For our network using Ubuntu 8.04, Sander Marechal's umountcifs script
works when symlinked as K15umountcifs (i.e. the key is that it is called
prior to K16dhcdbd).
$ sudo ln -s /etc/init.d/umountcifs /etc/rc0.d/K15umountcifs
$ sudo ln -s /etc/init.d/umountcifs /etc/rc6.d/K15umountcifs
--
** Attachment removed: umountcifs
http://launchpadlibrarian.net/19277243/umountcifs
** Attachment removed: umountcifs
http://launchpadlibrarian.net/19277241/umountcifs
--
CIFS/SMBFS shares not unmounted before network is shut down
https://bugs.launchpad.net/bugs/211631
You received this
The best solution to avoid messing up the unmounting issue for special cases as
described by Reinhard Tartler 5 posts ago is to use a special unmounting script
for cifs. People who have used the workaround described by luchio have never
used such a special case scenario. Therefore it is much
The best solution to avoid messing up the unmounting issue for special cases as
described by Reinhard Tartler 5 posts ago is to use a special unmounting script
for cifs. People who have used the workaround described by luchio have never
used such a special case scenario. Therefore it is much
The umountcifs script seems to solve the problem here (tested as
K12umountcifs). Of course, I had removed the other S14umountnfs.sh I
had added manually earlier.
It would be cleaner to do the symlinks as ../init.d/umountcifs like
other rc0.d scripts, instead of /etc/init.d. Otherwise, it
The best solution to avoid messing up the unmounting issue for special cases as
described by Reinhard Tartler 5 posts ago is to use a special unmounting script
for cifs. People who have used the workaround described by luchio have never
used such a special case scenario. Therefore it is much
The best solution to avoid messing up the unmounting issue for special cases as
described by Reinhard Tartler 5 posts ago is to use a special unmounting script
for cifs. People who have used the workaround described by luchio have never
used such a special case scenario. Therefore it is much
The best solution to avoid messing up the unmounting issue for special cases as
described by Reinhard Tartler 5 posts ago is to use a special unmounting script
for cifs. People who have used the workaround described by luchio have never
used such a special case scenario. Therefore it is much
1 - 100 of 158 matches
Mail list logo
