* python2.4 and logging
@ 2005-05-26 20:28 Ryan Harper
2005-06-19 16:54 ` Mark Williamson
0 siblings, 1 reply; 3+ messages in thread
From: Ryan Harper @ 2005-05-26 20:28 UTC (permalink / raw)
To: xen-devel
Any one else seeing this output from xend?
ValueError: I/O operation on closed file
Traceback (most recent call last):
File "/usr/lib/python2.4/logging/handlers.py", line 62, in emit
if self.shouldRollover(record):
File "/usr/lib/python2.4/logging/handlers.py", line 132, in shouldRollover
self.stream.seek(0, 2) #due to non-posix-compliant Windows feature
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: python2.4 and logging
2005-05-26 20:28 python2.4 and logging Ryan Harper
@ 2005-06-19 16:54 ` Mark Williamson
2005-06-20 14:04 ` Ryan Harper
0 siblings, 1 reply; 3+ messages in thread
From: Mark Williamson @ 2005-06-19 16:54 UTC (permalink / raw)
To: xen-devel; +Cc: Ryan Harper
> Any one else seeing this output from xend?
>
> ValueError: I/O operation on closed file
> Traceback (most recent call last):
> File "/usr/lib/python2.4/logging/handlers.py", line 62, in emit
> if self.shouldRollover(record):
> File "/usr/lib/python2.4/logging/handlers.py", line 132, in
> shouldRollover self.stream.seek(0, 2) #due to non-posix-compliant Windows
> feature
Yes, incessantly.
I haven't heard anything about it for a while - did you ever solve this?
Cheers,
Mark
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: python2.4 and logging
2005-06-19 16:54 ` Mark Williamson
@ 2005-06-20 14:04 ` Ryan Harper
0 siblings, 0 replies; 3+ messages in thread
From: Ryan Harper @ 2005-06-20 14:04 UTC (permalink / raw)
To: Mark Williamson; +Cc: xen-devel, Ryan Harper
* Mark Williamson <mark.williamson@cl.cam.ac.uk> [2005-06-20 08:58]:
> > Any one else seeing this output from xend?
> >
> > ValueError: I/O operation on closed file
> > Traceback (most recent call last):
> > File "/usr/lib/python2.4/logging/handlers.py", line 62, in emit
> > if self.shouldRollover(record):
> > File "/usr/lib/python2.4/logging/handlers.py", line 132, in
> > shouldRollover self.stream.seek(0, 2) #due to non-posix-compliant Windows
> > feature
>
> Yes, incessantly.
Good to hear I'm not the only one.
>
> I haven't heard anything about it for a while - did you ever solve this?
No, it became less annoying, though still unresolved, now that it only
writes that to /var/log/xend-debug.log instead of to stdout/stderr.
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-06-20 14:04 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-05-26 20:28 python2.4 and logging Ryan Harper
2005-06-19 16:54 ` Mark Williamson
2005-06-20 14:04 ` Ryan Harper
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.