Dear list members,
After a print job is submitted to Samba, from a windows client, the job
file is created at /var/spool/samba, and immediately, it 'get's copied
to /var/spool/cups, as it's expected, but, and here is the problem, it's
also removed from /var/spool/samba although remaining in the to
be processed queue in Cups.
CUPS finally gets the job printed ok, but shouldn't the job remain in
Samba's spooler until Cups signals the job was finished?
This prevents windows clients from canceling their jobs after they
submit them (they don't have access to CUPS).
As a test i sent a print job to a suspended printer in Cups and i
verified with a watch that the job goes to /var/spool/samba, then almost
immediately (<1 sec), the job appears in /var/spool/cups and gets
deleted from /var/spool/samba. As the printer was suspended, the job
remained in the Cups spool directory.
My system is a Mandriva 2010.2.0 (kernel 2.6.33.7-server), configured
with Samba 3.5.10 and CUPS 1.4.3.
My "smb.conf":
[global]
interfaces = lo, eth0
max log size = 50
printcap cache time = 60
printing = cups
printcap name = cups
dns proxy = No
admin users = @adm
print command =
lpq command = %p
lprm command =
[printers]
comment = All Printers
path = /var/spool/samba
guest ok = Yes
printable = Yes
browseable = No
Thanks,
--
Hugo Lima.
Analista Programador.
Direcção de Sistemas de Informação
Universidade Católica Portuguesa
Palma de Cima
1649-023 Lisboa
Portugal
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
