-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brecht Samyn wrote:
| A few weeks ago, I upgraded Samba 3.0.1x to 3.0.14a
| . After the upgrade, all completed printjobs on all
| 40 printers stayed in samba's print queue (they were removed
| from the unix-printqueue). When I installed 3.0.20rc2,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brecht Samyn wrote:
| A sample printer definition from smb.conf. We use lprng to spool the
| jobs to our lprng printserver.
|
| [poco]
|comment = Kleurprinter
|path=/var/spool/lp/samba
|printable = yes
|browseable = yes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brecht Samyn wrote:
> A few weeks ago, I upgraded Samba 3.0.1x to 3.0.14a .
> After the upgrade, all completed printjobs on all 40
> printers stayed in samba's print queue (they were removed
> from the unix-printqueue). When I installed 3.0.20rc2,
>
Yesterday evening, I installed the old 3.0.20rc2 files again (make revert).
When I first tested, printjobs were removed just fine from the windows
queue. But this morning, printerqueues were filling up again.
I don't see anything related in the logfiles.
Should I remove all the printer tdb fil
A few weeks ago, I upgraded Samba 3.0.1x to 3.0.14a . After the upgrade,
all completed printjobs on all 40 printers stayed in samba's print queue
(they were removed from the unix-printqueue). When I installed
3.0.20rc2, everything back to normal.
But since the upgrade this weekend to 3.0.20, t
