#warrior 2018-07-12,Thu

↑back Search

Time Nickname Message
01:35 🔗 Muad-Dib has quit IRC (Ping timeout: 260 seconds)
01:41 🔗 Muad-Dib has joined #warrior
01:42 🔗 svchfoo1 sets mode: +o Muad-Dib
05:46 🔗 Phoen1x_ has joined #warrior
05:50 🔗 Phoen1x has quit IRC (Ping timeout: 632 seconds)
06:12 🔗 Phoen1x has joined #warrior
06:16 🔗 Phoen1x_ has quit IRC (Ping timeout: 633 seconds)
07:07 🔗 kiska has quit IRC (Read error: Operation timed out)
07:09 🔗 jut I heve
07:11 🔗 jut i have an idea for the warior, if someone uses stop imidiatly the warior should tell the tracker to release its running items
07:26 🔗 Atom-- has joined #warrior
07:30 🔗 Atom has quit IRC (Read error: Operation timed out)
07:55 🔗 Flashfir_ has joined #warrior
07:55 🔗 Flashfir_ has quit IRC (Client Quit)
07:56 🔗 Flashfire has joined #warrior
08:03 🔗 kiska has joined #warrior
08:10 🔗 Flashfire has quit IRC (Quit: Bye)
08:12 🔗 Flashfire has joined #warrior
10:29 🔗 SilSte has quit IRC (Read error: Operation timed out)
10:31 🔗 SilSte has joined #warrior
10:56 🔗 Flashfire has quit IRC (Quit: Bye)
11:01 🔗 JAA Alternatively, the warrior could ping the tracker every minute to let it know which items it's still processing. If there is no ping received for an out item for a while, it's considered dead.
11:01 🔗 JAA That would also catch crashes, power outages, etc.
12:17 🔗 jut has quit IRC (Leaving)
12:19 🔗 jut has joined #warrior
15:29 🔗 sep332 has joined #warrior
16:33 🔗 SilSte has quit IRC (Read error: Operation timed out)
16:34 🔗 SilSte has joined #warrior
19:25 🔗 JonimusP has joined #warrior
19:25 🔗 swebb sets mode: +o JonimusP
19:28 🔗 tuluu_ has joined #warrior
19:30 🔗 Jonimoose has quit IRC (se.hub irc.underworld.no)
19:30 🔗 tuluu has quit IRC (se.hub irc.underworld.no)
19:30 🔗 hook54321 has quit IRC (se.hub irc.underworld.no)

irclogger-viewer