Cups 1.4.5<div><br></div><div>When a given printer is offline for awhile, I've noticed that the server may build up multiple socket:// processes, even for the same print job.</div><div><br></div><div><div>lp 7139 0.0 0.0 38636 2052 ? SN Mar14 0:00 socket://hp:9100 83696 bob smbprn.00000001 <a href="http://url/">http://url/</a> 1 job-originating-host-name=172.2.3.4 job-uuid=urn:uuid:05ba1e33-7260-3de7-79d9-ecb2f4e7dd9b time-at-creation=1299881442 time-at-processing=1300134839 AP_D_InputSlot=</div>
<div>lp 10971 0.0 0.0 38636 1596 ? SN Mar11 0:01 socket://hp:9100 83696 bob smbprn.00000001 <a href="http://url/">http://url/</a> 1 job-originating-host-name=172.2.3.4 job-uuid=urn:uuid:05ba1e33-7260-3de7-79d9-ecb2f4e7dd9b time-at-creation=1299881442 time-at-processing=1299886084 AP_D_InputSlot= /var/spool/cups/d83696-001</div>
<div>lp 17845 0.0 0.0 38636 1596 ? SN Mar14 0:00 socket://hp:9100 83696 bob smbprn.00000001 <a href="http://url/">http://url/</a> 1 job-originating-host-name=172.2.3.4 job-uuid=urn:uuid:05ba1e33-7260-3de7-79d9-ecb2f4e7dd9b time-at-creation=1299881442 time-at-processing=1300112358 AP_D_InputSlot=</div>
<div>lp 22299 0.0 0.0 38636 2040 ? SN 08:05 0:00 socket://hp:9100 83696 bob smbprn.00000001 <a href="http://url/">http://url/</a> 1 job-originating-host-name=172.2.3.4 job-uuid=urn:uuid:05ba1e33-7260-3de7-79d9-ecb2f4e7dd9b time-at-creation=1299881442 time-at-processing=1300201547 AP_D_InputSlot=</div>
</div><div><br></div><div><div>Process 7139 attached - interrupt to quit</div><div>restart_syscall(<... resuming interrupted call ...>) = 0</div><div>socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 5</div><div>setsockopt(5, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0</div>
<div>setsockopt(5, SOL_TCP, TCP_NODELAY, [1], 4) = 0</div><div>fcntl(5, F_SETFD, FD_CLOEXEC) = 0</div><div>connect(5, {sa_family=AF_INET, sin_port=htons(9100), sin_addr=inet_addr("172.2.3.5")}, 16) = -1 ETIMEDOUT (Connection timed out)</div>
<div>close(5) = 0</div><div>write(2, "DEBUG: Connection error: Connect"..., 46) = -1 EPIPE (Broken pipe)</div><div>--- SIGPIPE (Broken pipe) @ 0 (0) ---</div><div>write(2, "ERROR: recoverable: Unable to co"..., 78) = -1 EPIPE (Broken pipe)</div>
<div>--- SIGPIPE (Broken pipe) @ 0 (0) ---</div><div>rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0</div><div>rt_sigaction(SIGCHLD, NULL, {SIG_DFL, [], 0}, 8) = 0</div><div>rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0</div>
<div>nanosleep({30, 0}, 0x7fffc7116a70) = 0</div><div>socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 5</div><div>setsockopt(5, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0</div><div>setsockopt(5, SOL_TCP, TCP_NODELAY, [1], 4) = 0</div>
<div>fcntl(5, F_SETFD, FD_CLOEXEC) = 0</div><div>connect(5, {sa_family=AF_INET, sin_port=htons(9100), sin_addr=inet_addr("172.2.3.5")}, 16) = -1 ETIMEDOUT (Connection timed out)</div><div>close(5) = 0</div>
<div>write(2, "DEBUG: Connection error: Connect"..., 46) = -1 EPIPE (Broken pipe)</div><div>--- SIGPIPE (Broken pipe) @ 0 (0) ---</div><div>write(2, "ERROR: recoverable: Unable to co"..., 78) = -1 EPIPE (Broken pipe)</div>
<div>--- SIGPIPE (Broken pipe) @ 0 (0) ---</div><div>rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0</div><div>rt_sigaction(SIGCHLD, NULL, {SIG_DFL, [], 0}, 8) = 0</div><div>rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0</div>
<div>nanosleep({30, 0}, 0x7fffc7116a70) = 0</div></div><div><br></div><div>This seems odd. Shouldn't there only be one socket per job?</div><div><br></div>