[Samba] Re: Trying to delay for oplocks twice
Beschorner Daniel
Daniel.Beschorner at facton.com
Wed Jan 4 18:42:17 GMT 2006
Sorry, the second problem "just" seems to be related to an offline printer:
#0 0x00002aaaab3e76d4 in waitpid () from /lib64/tls/libc.so.6
#1 0x00000000005963c0 in smbrun ()
#2 0x000000000058a8e1 in print_run_command ()
#3 0x000000000058accf in generic_job_submit ()
#4 0x00000000005bbb20 in print_job_end ()
#5 0x00000000004f5f9a in _spoolss_enddocprinter_internal ()
#6 0x00000000004f073a in api_spoolss_enddocprinter ()
#7 0x000000000051eaf1 in api_rpcTNP ()
#8 0x000000000051ee75 in api_pipe_request ()
#9 0x000000000051b975 in write_to_internal_pipe ()
#10 0x00000000004510f1 in api_fd_reply ()
#11 0x0000000000451b70 in reply_trans ()
#12 0x0000000000497128 in switch_message ()
#13 0x00000000004973e9 in process_smb ()
#14 0x000000000049810f in smbd_process ()
#15 0x000000000060f1ff in main ()
After the job was printed some hours later all went fine.
--------------------------------------------
We have a lot of
[2006/01/04 18:44:40, 0] smbd/open.c:open_file_ntcreate(1355)
Trying to delay for oplocks twice
in the logs. Do they harm in general?
And only in one single case I got this, don't know if I ever will get it
reproduced, so maybe not related and happened by accident:
Samba version 3.0.21a
PID Username Group Machine
------------------------------------------------------
8231 testuser users ws24(192.168.1.24)
8673 testuser users ws24(192.168.1.24)
3822 testuser users ws24(192.168.1.24)
Service pid machine Connected at
--------------------------------------------
IPC$ 3822 ws24 Wed Jan 4 17:33:14 2006
IPC$ 8231 ws24 Wed Jan 4 17:35:02 2006
testuser 3822 ws24 Wed Jan 4 07:50:41 2006
Projects 8673 ws24 Wed Jan 4 18:44:40 2006
3822 DENY_WRITE 0x2019f RDWR NONE outlook/rsc.pst Wed Jan 4 17:20:40
2006
8673 DENY_NONE 0x20089 RDONLY NONE outlook/rsc.pst Wed Jan 4 18:49:38
2006
Windows complained about "Cannot access rcs.pst, in use by another process".
More information about the samba
mailing list