Hangups of Samba 2.0.5.a PDC

Dr. Dieter Becker db at med-in.uni-sb.de
Mon Oct 25 13:26:53 GMT 1999


Sirs,

2.0.5a is running on our Sparc / Solaris 2.6 generally without problems. But
sometimes there is a total
use of the network capacity and CPU by one client. It was a long way to find
this "dog" but now I
identified it. There is a "endless" list of entries in the log file:

[1999/10/25 08:12:05, 0] smbd/oplock.c:initial_break_processing(664)
  initial_break_processing: cannot find open file with dev = 1540001, inode
= 558849 allowing break to succeed.
[1999/10/25 08:12:05, 0] smbd/oplock.c:initial_break_processing(664)
  initial_break_processing: cannot find open file with dev = 1540001, inode
= 558849 allowing break to succeed.
[1999/10/25 08:12:05, 0] smbd/oplock.c:initial_break_processing(664)
  initial_break_processing: cannot find open file with dev = 1540001, inode
= 558849 allowing break to succeed.
[1999/10/25 08:12:05, 0] smbd/oplock.c:initial_break_processing(664)
  initial_break_processing: cannot find open file with dev = 1540001, inode
= 558849 allowing break to succeed.
[1999/10/25 08:12:08, 1] smbd/service.c:close_cnum(557)

What can I do to prevent further breakdown of the system. Till now I don't
know wether it's allways
the same client who disturbs samba. But nevertheless there should be any
prevention to steel full
server capacity by one client.

Dieter

Dr. med. dipl.-math Dieter Becker
Medizinische Universitaets- und Poliklinik
Innere Medizin III
D - 66421 Homburg / Saar
###########################################
Tel.: (0 / +49) 6841 - 16 3046
Fax.: (0 / +49) 6841 - 16 3043
Email: db at med-in.uni-sb.de






More information about the samba-ntdom mailing list