Conversation with #inferno at Mon Sep 5 18:09:18 2011 on powerman-asdf@irc.freenode.net (irc) (20:22:04) bvalek2 left the room (quit: Ping timeout: 252 seconds). (20:32:57) bvalek2 [588058b0@gateway/web/freenode/ip.88.128.88.176] entered the room. (20:42:39) acmeuser [~acmeuser@97-64-177-74.client.mchsi.com] entered the room. (20:42:57) acmeuser left the room (quit: Remote host closed the connection). (22:27:21) bvalek2 left the room (quit: Quit: Page closed). (23:10:28) KBme left the room (quit: Ping timeout: 260 seconds). (23:12:26) KBme [~KBme@2001:470:cabe:666:666:666:666:666] entered the room. (23:24:32) Fish- [~Fish@9fans.fr] entered the room. (23:59:07) Fish- left the room (quit: Quit: WeeChat 0.3.5). (08:11:57) vsrinivas left the room (quit: Ping timeout: 240 seconds). (08:13:25) vsrinivas [U2FsdGVkX1@batman.acm.jhu.edu] entered the room. (08:29:51) robot12 [~kazzhilki@proxy10.ts.fujitsu.com] entered the room. (10:32:30) powerman-asdf: I've found why RST packets wasn't sent: they was blocked by GrSecurity in my kernel because of enabled feature CONFIG_GRKERNSEC_BLACKHOLE :-/ (10:35:29) robot12: powerman-asdf: hello ! :) (10:35:40) powerman-asdf: robot12: hi (10:38:34) powerman-asdf: if anyone remember my project iobuf (http://code.google.com/p/inferno-contrib-iobuf/source/browse/doc/2/iobuf.txt), I'm now think about adding feature to set write timeout (10:39:13) powerman-asdf: but I'm not sure is it good idea, because for now this module do only one thing - manage in/out buffers (10:39:38) powerman-asdf: but to support timeouts it will need to spawn processes and use timers module (10:41:03) powerman-asdf: from other view, that's only way to get timeout error just like any other i/o errors - as exception raised by WriteBuf.write() (10:45:28) powerman-asdf: keeping in mind RST packets may not be sent (because of grsec blackhole or if remote host was power off) timeout on write is only way to detect broken connections (10:57:54) robot121 [~kazzhilki@proxy10.ts.fujitsu.com] entered the room. (10:58:54) robot12 left the room (quit: Ping timeout: 245 seconds). (11:24:05) bvalek2 [c3e41484@gateway/web/freenode/ip.195.228.20.132] entered the room. (11:40:10) bvalek2_ [c3e41484@gateway/web/freenode/ip.195.228.20.132] entered the room. (11:40:14) bvalek2 left the room (quit: Disconnected by services). (11:40:19) bvalek2_ is now known as bvalek2 (11:59:08) robot12 [~kazzhilki@proxy10.ts.fujitsu.com] entered the room. (12:02:28) robot121 left the room (quit: Ping timeout: 264 seconds). (12:14:10) fgudin left the room (quit: Remote host closed the connection). (12:18:20) bvalek2 left the room (quit: Ping timeout: 252 seconds). (12:22:08) bvalek2 [58805290@gateway/web/freenode/ip.88.128.82.144] entered the room. (14:23:23) KBme left the room (quit: Ping timeout: 260 seconds). (14:25:52) KBme [~KBme@2001:470:cabe:666:666:666:666:666] entered the room. (15:40:22) bvalek2 left the room (quit: Ping timeout: 252 seconds). (16:14:21) robot12 left the room (quit: Quit: Leaving.). (17:36:27) __20h__ left the room (quit: Ping timeout: 258 seconds). (17:44:33) __20h__ [~some_one@r-36.net] entered the room. (18:08:04) The account has disconnected and you are no longer in this chat. You will be automatically rejoined in the chat when the account reconnects.