This is rather feature. Here is the scenario: 1) libsmbclient remember the network configuration on start of SMBNetFS. You suspend your notebook and resume it in another network environment. So you get the network configuration mismatch.
2) "fusermount -u" umount filesystem and send the signal "shutdown is required" for SMBNetFS. Delivering of the signal may wait for finish of periodic network scan. Usually it's not a problem, as the scan do not require large time. In this case (the network configuration mismatch) the network scan may run for a much longer time. Mikhail Kshevetskiy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
