We have a pretty basid samba setup. A Solaris 5.8 server running samba
2.2.3a that is logged-into by Win2K clients (non-encrypted) for file
access and printing. When a user double-clicks on a file in Windows
Explorer the appropriate application launches and then seems to freeze.
If I go to a console window on the Solaris box and do a 'ps -eaf | grep
smbd | grep USERNAME' and kill the processes, the application finishes
loading the file and works happily along. This sounds like the file
locking issue of samba 2.2.1 with Solaris, but that was supposed to be
fixed in this version...
I am currently running a 'ps -eaf | grep smbd | grep -v root' hourly and
killing off the processes I see as preventative maintenance.
BTW If a user doesn't kill off the process and instead kills the
Windows App, the process seems to just stick around, and the trouble
just gets worse as they then are told that the file is inaccessible,
etc...
Any ideas on where to start looking? I have been monitoring this list
and reading as much as I can, but I am new to samba (though learning
fast).
--
-Broderick Wood-
Analyst, Systems Support Group
Department of Computing Sciences
Athabasca Hall, Room 205
University of Alberta
Edmonton, Alberta, Canada
T6G 2E1
(780) 492-5018
"Failure is NOT an option;
It's bundled with your software."