This worked the first time that I tried it, but there are cases when it 
does not work.  For example, if after mounting a Windows share the 
connection gets broken, the mount will not work, and you might see 
things like command-line lockups during directory listings, etc.  At 
this point, I believe you can successfully use a "umount -l" to unmount 
it.  When I tried it, the mount was not immediately removed from the 
list of mounted filesystems via the mount command.  I probably moved too 
fast trying to figure out what was going on, because I shot back to 
runlevel 1 (from 5), and it is from there that I noticed that the mount 
point was no longer listed with the "mount" command.

Now, if instead of immediately using "umount -l" after the network 
connection is broken you decide to restart the Samba server daemons, 
then you will be unable to use the "mount -l" command.  Here is a script 
output of what I see when I try this (runlevel 1 after Samba restart):

-----------------------------

bash-2.05# mount
/dev/hda1 on / type ext3 (rw)
none on /proc type proc (rw)
none on /dev type devfs (rw)
none on /dev/pts type devpts (rw,mode=0620)
none on /dev/shm type tmpfs (rw)
/dev/hda8 on /home type ext3 (rw)
/mnt/cdrom on /mnt/cdrom type supermount 
(ro,dev=/dev/hdc,fs=iso9660,--,iocharset=iso8859-1)
/mnt/floppy on /mnt/floppy type supermount 
(rw,sync,dev=/dev/fd0,fs=vfat,--,iocharset=iso8859-1,codepage=850)
/mnt/zip on /mnt/zip type supermount 
(rw,sync,dev=/dev/sdb4,fs=vfat,--,iocharset=iso8859-1,codepage=850)
/dev/sda5 on /opt type ext3 (rw)
/dev/hdb1 on /pub type ext3 (rw)
/dev/hda6 on /usr type ext3 (rw)
/dev/hda7 on /var type ext3 (rw)
none on /proc/bus/usb type usbdevfs (rw,devmode=0664,devgid=43)
//RGILLEN/shared on /home/borgille/mnt/RGILLEN/shared type smbfs (0)

bash-2.05# umount /home/borgille/mnt/RGILLEN/share
umount: /home/borgille/mnt/RGILLEN/share: not found

bash-2.05# umount -l /home/borgille/mnt/RGILLEN/share
umount: /home/borgille/mnt/RGILLEN/share: not found

-----------------------------

One note here that may not be evident is that the mount point did exist.

ROB


PlugHead wrote:

>I have this problem all the time:
>
>'umount /mount/point -l'
>
>should do the trick.
>
>-Jason
>
>(And once again, my first post on the topic was dropped... grr...)
>



Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com

Reply via email to