[Samba] Samba as PDC vs. XP-SP1 profile storage

ddkh at libero.it ddkh at libero.it
Sun Nov 17 01:15:00 GMT 2002


I experienced some problem with the logout procedure which
involves profile saving on a BSD machine running Samba 2.2.6a. In 
fact, although permissions are rightly set (mode 700/600 for 
dirs/files) for the user profile path, the SMB connection seems to 
broke unexpectedly.
As a consequence, an error message (that appears in winxp) informed me 
that some file could not be stored (but not all files, infact some of 
them were saved) because network name was no more available.

The same configuration (I mean smb.conf, of course) works correctly on 
win2k and/or win98 computers, so I suppose that the problem relies in 
some "particular" new feature of winxp-sp1.

This is the log file for the client:

[2002/11/16 14:09:01, 3] lib/util.c:unix_clean_name(387)
  unix_clean_name [/home/Profiles/justme/SendTo/prf4.tmp]
[2002/11/16 14:09:01, 3] smbd/oplock.c:initial_break_processing(526)
  initial_break_processing: called for dev = 27400, inode = 145210
file_id = 1623
  Current oplocks_open (exclusive = 4, levelII = 0)
[2002/11/16 14:09:01, 0] smbd/oplock.c:oplock_break(684)
  oplock_break: ERROR: oplock_break already sent for file
SendTo/prf4.tmp (dev = 27400, inode = 145210, file_id = 1623)
[2002/11/16 14:09:01, 0] smbd/open.c:open_mode_check(599)
  open_mode_check: FAILED when breaking oplock (3) on file
/home/Profiles/justme/SendTo/prf4.tmp, dev = 27400, inode = 145210
[2002/11/16 14:09:01, 2] smbd/open.c:open_file(245)
  justme opened file /home/Profiles/justme/SendTo/prf4.tmp read=Yes
write=No (numopen=5)
[2002/11/16 14:09:01, 3] lib/util.c:unix_clean_name(387)
  unix_clean_name [/home/Profiles/justme/SendTo/prf5.tmp]
[2002/11/16 14:09:01, 3] smbd/oplock.c:initial_break_processing(526)
  initial_break_processing: called for dev = 27400, inode = 145211
file_id = 1624
  Current oplocks_open (exclusive = 4, levelII = 0)
[2002/11/16 14:09:01, 0] smbd/oplock.c:oplock_break(699)
  ABORT : ABORT : recursion in oplock_break !!!!!

Has anybody else ever experienced this kind of error?

Cheers :)




More information about the samba mailing list