Your message dated Sun, 1 Jun 2008 23:09:06 +0200 with message-id <20080601210906.GB6509@piware.de> and subject line Cleaning up old bug reports has caused the Debian Bug report #251391, regarding cupsys - lpd backend always reports timeout to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 251391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=251391 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: cupsys - lpd backend always reports timeout
- From: Bastian Blank <waldi@debian.org>
- Date: Fri, 28 May 2004 12:09:17 +0200
- Message-id: <20040528100917.GA379@wavehammer.waldi.eu.org>
Package: cupsys Version: 1.1.20final+cvs20040330-3 Severity: important The lpd backend always reports timeout if the remote host does not respond properly: | 12:02:47.249210 write(2, "INFO: Attempting to connect to h"..., 73) = 73 | 12:02:47.249273 getuid32() = 0 | 12:02:47.249321 socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 3 | 12:02:47.249376 bind(3, {sa_family=AF_INET, sin_port=htons(1023), sin_addr=inet_addr("0.0.0.0")}, 16) = -1 EADDRINUSE (Address already in use) | 12:02:47.249445 bind(3, {sa_family=AF_INET, sin_port=htons(1022), sin_addr=inet_addr("0.0.0.0")}, 16) = 0 | 12:02:47.249502 connect(3, {sa_family=AF_INET, sin_port=htons(515), sin_addr=inet_addr("192.168.202.81")}, 16) = 0 | 12:02:47.256825 write(2, "INFO: Connected to print1.blank."..., 42) = 42 | 12:02:47.256881 write(2, "DEBUG: Connected on ports 515 (l"..., 46) = 46 | 12:02:47.256951 stat64("/var/spool/cups/d01055-001", {st_mode=S_IFREG|0640, st_size=49782, ...}) = 0 | 12:02:47.257067 open("/var/spool/cups/d01055-001", O_RDONLY) = 4 | 12:02:47.257148 write(2, "DEBUG: lpd_command 02 lpt1\n", 27) = 27 | 12:02:47.257198 write(2, "DEBUG: Sending command string (6"..., 43) = 43 | 12:02:47.257255 send(3, "\2lpt1\n", 6, 0) = 6 | 12:02:47.257340 write(2, "DEBUG: Reading command status..."..., 33) = 33 | 12:02:47.257398 alarm(300) = 0 | 12:02:47.257462 recv(3, "", 1, 0) = 0 | 12:02:47.373063 write(2, "WARNING: Remote host did not res"..., 81) = 81 | 12:02:47.373147 alarm(0) = 300 | 12:02:47.373193 write(2, "DEBUG: lpd_command returning 98\n", 32) = 32 | 12:02:47.373325 exit_group(1) = ? Even if it may check for EINTR, it is not possible to decide if this is a SIGALRM. The only correct solution is to use non-blocking sockets and select/poll with timeout. Bastian -- ... bacteriological warfare ... hard to believe we were once foolish enough to play around with that. -- McCoy, "The Omega Glory", stardate unknownAttachment: signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
- To: 190135-done@bugs.debian.org, 201553-done@bugs.debian.org, 220642-done@bugs.debian.org, 280236-done@bugs.debian.org, 283581-done@bugs.debian.org, 284575-done@bugs.debian.org, 288784-done@bugs.debian.org, 353763-done@bugs.debian.org, 354579-done@bugs.debian.org, 354581-done@bugs.debian.org, 354590-done@bugs.debian.org, 369563-done@bugs.debian.org, 384448-done@bugs.debian.org, 414299-done@bugs.debian.org, 283484-done@bugs.debian.org, 189705-done@bugs.debian.org, 423943-done@bugs.debian.org, 116286-done@bugs.debian.org, 126170-done@bugs.debian.org, 130661-done@bugs.debian.org, 140673-done@bugs.debian.org, 162459-done@bugs.debian.org, 163051-done@bugs.debian.org, 166729-done@bugs.debian.org, 179349-done@bugs.debian.org, 188237-done@bugs.debian.org, 192905-done@bugs.debian.org, 193671-done@bugs.debian.org, 197200-done@bugs.debian.org, 208059-done@bugs.debian.org, 223465-done@bugs.debian.org, 235522-done@bugs.debian.org, 238757-done@bugs.debian.org, 245514-done@bugs.debian.org, 254747-done@bugs.debian.org, 257051-done@bugs.debian.org, 265817-done@bugs.debian.org, 271157-done@bugs.debian.org, 271874-done@bugs.debian.org, 289893-done@bugs.debian.org, 290346-done@bugs.debian.org, 293247-done@bugs.debian.org, 313416-done@bugs.debian.org, 319093-done@bugs.debian.org, 323795-done@bugs.debian.org, 323796-done@bugs.debian.org, 335391-done@bugs.debian.org, 342735-done@bugs.debian.org, 343509-done@bugs.debian.org, 343518-done@bugs.debian.org, 343535-done@bugs.debian.org, 351893-done@bugs.debian.org, 366674-done@bugs.debian.org, 370607-done@bugs.debian.org, 371740-done@bugs.debian.org, 372309-done@bugs.debian.org, 373281-done@bugs.debian.org, 373793-done@bugs.debian.org, 375254-done@bugs.debian.org, 375907-done@bugs.debian.org, 377079-done@bugs.debian.org, 381250-done@bugs.debian.org, 382499-done@bugs.debian.org, 382936-done@bugs.debian.org, 389240-done@bugs.debian.org, 400262-done@bugs.debian.org, 220611-done@bugs.debian.org, 291788-done@bugs.debian.org, 356468-done@bugs.debian.org, 251391-done@bugs.debian.org, 259774-done@bugs.debian.org, 301012-done@bugs.debian.org, 304136-done@bugs.debian.org, 344542-done@bugs.debian.org, 368019-done@bugs.debian.org, 370559-done@bugs.debian.org, 377604-done@bugs.debian.org, 380549-done@bugs.debian.org, 380640-done@bugs.debian.org, 381428-done@bugs.debian.org, 383290-done@bugs.debian.org, 386785-done@bugs.debian.org, 387201-done@bugs.debian.org, 390522-done@bugs.debian.org
- Subject: Cleaning up old bug reports
- From: Martin Pitt <mpitt@debian.org>
- Date: Sun, 1 Jun 2008 23:09:06 +0200
- Message-id: <20080601210906.GB6509@piware.de>
Dear bug submitter, This bug was reported against a very old version of cups (older than in the current stable Debian version "Etch"). About a year ago, Martin-Eric Racine asked for feedback whether the bug still applied to the current Debian Etch version, but we did not get any feedback. In order to not keep around old, hardware-specific, and inactive bugs around forever, I close this bug now. Please report back if you still experience the problem with the current version in Etch; if you can test Lenny/unstable, that would be highly appreciated, of course. I will reopen this bug then. Thank you for your report! Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)Attachment: signature.asc
Description: Digital signature
--- End Message ---