[Samba] Re: Trying to delay for oplocks twice
Daniel.Beschorner at facton.com
Wed Jan 4 20:26:15 GMT 2006
The question is whether blocking is well defined in this case (because lpd
hangs) or if it is an error that the file serving/locking services of the
smbd process hang altogether.
My print section looks like this:
printing = lprng
print command = lpr -r -P'%p' %s
lpq command = lpq -P'%p'
lprm command = lprm -P'%p' %j
lppause command = lpc hold '%p' %j
lpresume command = lpc release '%p' %j
queuepause command = lpc stop '%p'
queueresume command = lpc start '%p'
use client driver = No
default devmode = No
force printername = No
It's a Linux x64 system with lprng printing.
-----BEGIN PGP SIGNED MESSAGE-----
Beschorner Daniel wrote:
> Sorry, the second problem "just" seems to be related to an offline
> #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.
Please give me some more details on the server OS
and the outout from 'testparm -v'
More information about the samba