On Sun, Mar 13, 2011 at 3:15 AM, Tim Allen wrote:
> On Sat, Mar 12, 2011 at 02:33:45PM +0200, Pandelis Theodosiou wrote:
> > On Sat, Mar 12, 2011 at 3:32 AM, Tim Allen wrote:
> > > Of course, if you flush after every disk read, your program will run
> > > a bit more slowly and with more I/O... f
On Sat, Mar 12, 2011 at 02:33:45PM +0200, Pandelis Theodosiou wrote:
> On Sat, Mar 12, 2011 at 3:32 AM, Tim Allen wrote:
> > Of course, if you flush after every disk read, your program will run
> > a bit more slowly and with more I/O... for an application where
> > reliability is more important th
Tim,
Just a quick note to answer your questions:
I have _proc_msg separated out as I'll be adding some additional
functionality on later (adding ACK messages for certain types of log
messages). I do like the way you handled the _new_msg func. I'll probably
do that instead ... but with a couple
Hello,
Thanks for the help. Adding a timerservice that calls .flush() on the files
every minute (and before rotating the logs) seems to have helped.
Appreciate the quick response and feedback.
Thanks again!
SDR
___
Twisted-Python mailing list
Twisted
On Sat, Mar 12, 2011 at 3:32 AM, Tim Allen wrote:
> On Fri, Mar 11, 2011 at 01:15:47PM -0600, SIC FS LIST wrote:
> > So far I have a "working" implementation ... but I'm noticing that if I
> do
> > the following:
> > -- log when a message is received
> > -- that for that message it "might" show u
On Fri, Mar 11, 2011 at 01:15:47PM -0600, SIC FS LIST wrote:
> So far I have a "working" implementation ... but I'm noticing that if I do
> the following:
> -- log when a message is received
> -- that for that message it "might" show up in the file a pretty lengthy
> period of time later
Assuming
Hello,
I am trying to write a UDP based logging server.
Generically speaking it looks somewhat like syslog except I needed a bit
more flexibility that syslog can provide (or at least that I think it can
provide).
What I'm trying to accomplish is:
-- receive UDP packet
-- parse UDP packet
-- writ
