We're having the same problem, although ours is a bit worse. Sometimes
some of our Win95 clients don't connect properly, getting the
"Can't find
sharename" message. This also starts a smbd process and leaves it running.
Unfortunately, we're using PAM to authenticate with a pam_ldap module for
authenticating against our LDAP database. Whenever the smbd process is
left running it also ties up the pam_ldap module, not allowing ANYTHING to
use it (telnet, ftp, whatever), until I kill the offending process. I
haven't played with the dead time parameter, so maybe I should look into
it, but I'm not sure it will help. this has been extremely frustrating and
some in my department are beginning to question the use of Samba if it
keeps doing this, because weve committed to using LDAP. Anyway, any help
anyone else has in the matter would be appreciated.
-jay
>When a PC crashes the smb process does not die. If that smb process is
>holding a lock on a file, the file is locked until I, the sysadmin,
>kill it.
>
>Some of our smb processes are owned by the user, but most are owned by
>root, so the user cannot kill it themselves.
>
>I am thinking about writing a small script that will, for a given
>user, search out all smb processes and kill them. Maybe someone has
>already done this?
>
>Of course, I would rather this happen automatically - when a pc
>crashes, the smb process dies too. Maybe I just have to know what
>config parameters to use.
>
>I have considered using the dead time parameter, but we turned that
>off more than a year ago for reasons I no longer remember. Should I
>reconsider that decision?
>
>Can anyone offer any suggestions?
>
>Kind regards,
>Larry
____________________________________________________________________
Jay Christner Office: UN-019
Technical Services Phone:(219)-535-7640
Residential Computer Technician
Goshen College
____________________________________________________________________
