Your message dated Wed, 19 Nov 2008 03:55:06 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#367584: mmap man pages maybe warn of breaking
/dev/stdin
has caused the Debian Bug report #367584,
regarding mmap man pages maybe warn of breaking /dev/stdin
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 [EMAIL PROTECTED]
immediately.)
--
367584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367584
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: manpages-dev
Version: 2.25-3
Severity: minor
Maybe the mmap man pages should warn that this messes things like
Bug#367297: dpkg --merge-avail /dev/stdin doesn't work
> # ssh ...|dpkg --merge-avail /dev/stdin
> Updating available packages info, using /dev/stdin.
> Information about 0 package(s) was updated.
I guess this happens because we open the file with mmap.
Support for reading the available data from stdin would probably have to
be added seperatly.
up, or maybe this is all over my head.
--- End Message ---
--- Begin Message ---
Hi,
On Wed, 2006-05-17 at 09:38:18 -0400, Justin Pryzby wrote:
> On Wed, May 17, 2006 at 05:33:32AM +0800, Dan Jacobson wrote:
> > Package: manpages-dev
> > Version: 2.25-3
> > Severity: minor
> >
> > Maybe the mmap man pages should warn that this messes things like
> > Bug#367297: dpkg --merge-avail /dev/stdin doesn't work
> > > # ssh ...|dpkg --merge-avail /dev/stdin
> > > Updating available packages info, using /dev/stdin.
> > > Information about 0 package(s) was updated.
> > I guess this happens because we open the file with mmap.
> > Support for reading the available data from stdin would probably have to
> > be added seperatly.
> > up, or maybe this is all over my head.
This has nothing to do with the mmap man page, it's a dpkg
implementation detail, it just needs to be implemented. Thus closing
this invalid bug report.
> This probably fails because pipes aren't seekable; could you strace
> the process and report what happens between the open /dev/stdin and
> close of that fd? Why do you suggest that it is mmaped, anyway? I
> see this:
>
> |open64("/dev/stdin", 0, 01007404334) = 4
> |malloc(44) = 0x812a120
> |__fxstat64(3, 4, 0xbfdadd68) = 0
> |memset(0xbfdadcf4, '\000', 116) = 0xbfdadcf4
> |free(0x812a120) = <void>
> |free(NULL) = <void>
> |close(4) = 0
>
> ... |strace dpkg --merge-avail /dev/stdin 2>&1 |less
dpkg is not even trying to mmap, because the file size for /dev/stdin
is 0.
regards,
guillem
--- End Message ---
