Bugzilla – Bug 5368
thinlocal should not wait for client to close connection before considering print job complete
Last modified: 2014-11-26 16:11:10
You need to
before you can comment on or make changes to this bug.
A customer reported that thanks to bug 3610, their entire thinlocal backend
stopped for all users. Thinlocal should be more aggressive in considering the
job sent when it has sent all data to the client to avoid cases where a single
user may lock the entire thinlocal queue for all users. A timeout for hanging
connections would also be nice, but printing a large file over a slow
connection is a valid use case for thinlocal.
*** This bug has been marked as a duplicate of bug 1456 ***