- priority: 5 --> 1
- status: open --> open-duplicate
I have just started looking at qmHandle, after
reading some reviews on it's power, and I'm
noticing a bug possibly?
******* Works *********
root@mail2:/usr/local/src# perl qmHandle -s
Messages in local queue: 0
Messages in remote queue: 9833
root@mail2:/usr/local/src#
******* Doesn't work ******
root@mail2:/usr/local/src# perl qmHandle -l
readline() on closed filehandle MSG at qmHandle
line 233, <MSG> line 6 (#1)
(W closed) The filehandle you're reading from
got itself closed sometime
before now. Check your control flow.
Use of uninitialized value in substr at qmHandle line
234, <MSG> line 6 (#2)
(W uninitialized) An undefined value was used
as if it were already
defined. It was interpreted as a "" or a 0, but
maybe it was a mistake.
To suppress this warning assign a defined value
to your variables.
To help you figure out what was undefined, perl
tells you what operation
you used the undefined value in. Note,
however, that perl optimizes your
program and the operation displayed in the
warning may not necessarily
appear literally in your program. For
example, "that $foo" is
usually optimized into "that " . $foo, and the
warning will refer to
the concatenation (.) operator, even though
there is no . in your
program.
readline() on closed filehandle MSG at qmHandle
line 243 (#1)