Your message dated Mon, 30 Jul 2007 22:16:15 +0200
with message-id <[EMAIL PROTECTED]>
and subject line EOVERFLOW while accessing /dev/pts/256
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: screen
Severity: important
----- Forwarded message from William Lee Irwin III <[EMAIL PROTECTED]> -----
From: William Lee Irwin III <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: Marco d'Itri <[EMAIL PROTECTED]>
Subject: Re: EOVERFLOW while accessing /dev/pts/256
[...]
screen(1) wasn't properly compiled with -D_FILE_OFFSET_BITS=64; it
wouldn't see -EOVERFLOW for such if it used stat64. The minor < 256
check is only used in old_valid_dev(), which in turn is only used in
the non-stat64 syscall variants. new_valid_dev() always returns 1.
-- wli
----- End forwarded message -----
--
ciao, |
Marco | [7964 pefSok7ZYo1Rs]
--- End Message ---
--- Begin Message ---
Hi,
although I had taken no explicit measures to fix this bug in 4.0.3-1,
it seems to have gone away - screen handles pty master/slave pairs
above 255 just fine now. Furthermore strace shows no stat() calls at
all now, only stat64().
Regards,
Jan
signature.asc
Description: Digital signature
--- End Message ---
