search for: smb_umount

...CatchSignal(SIGUSR1, &usr1_handler); pause(); @@ -350,6 +350,7 @@ DEBUG(2,("mount.smbfs: got signal, getting new socket\n")); #endif c = do_connection(service); + if(c==NULL) goto failed; } smb_umount(mount_point); --------------------------------------------------------------- --Anton P.S. Sorry for my bad English, but i am not a native speaker. P.P.S. Is it a known bug? Is there any other patches? --Anton mailto:anton@engec.ru ENGECON CC

(using samba-2.0.7 on Debian Linux 2.2.15) Hi, I'm wondering how do I get around the problem when you smbmount a share on a win32 machine and that machine reboots, the mount becomes a blackhole. If you attempt an 'ls', 'df' or anything that would access that mount point the program then goes into a state of void and cannot be killed, leaving the proc open until reboot

...ignal from smbfs ... but don't continue + until we actually get a new connection. */ + while (!c) { + CatchSignal(SIGUSR1, &usr1_handler); + pause(); + DEBUG(2,("mount.smbfs: got signal, getting new socket\n")); + c = do_connection(service); + } } smb_umount(mount_point); @@ -452,10 +468,12 @@ fprintf(stderr,"waitpid failed: Error was %s", strerror(errno) ); /* FIXME: do some proper error handling */ exit(1); - } + } if (WIFEXITED(status) && WEXITSTATUS(status) != 0) { fprintf(stderr,"smbmnt failed: %d\n", W...

...t to do? are you sure the mount and umount commands are in the path during pri and post-exec ? try using full path for mount and umount. Also try redirecting errors to a file : #preexec = /path/to/mount /cdrom >> /tmp/smb_mount.log 2>&1 #postexec = /path/to/umount /cdrom >> /tmp/smb_umount.log 2>&1 You'll probably find the source of the error in the logfile ;) bye Ahmed. Return-Path: <jeremy@valinux.com> Delivered-To: samba@us4.samba.org Received: from mail.valinux.com (mail.valinux.com [198.186.202.175]) by lists.samba.org (Postfix) with ESMTP id D1A844791 for...