o2o bug reporter (bugrepor...@one-2-one.pl) wrote: > The problem is that after quite random time of operation (at least 30 > minutes, usually few hours)- while daemon is not under heavy load (I would > even > say while it is almost not used) - it crashes, leaving it's PID file. Without > using 'gdb' it was impossible for me to get any clue why it bahaves so. > Daemon process has just been dissappearing at a time.
Hello, That sounds indeed like a bug, but I'm unable to reproduce this problem. I started a server like this: $ ttserver -port 1999 -ext expire.lua -extpc expire 1.0 -ld test.tct#idx=key:lex#idx=x:dec#idx=val:lex#dfunit=8 And then I inserted some keys: $ for i in `seq 1 60`; do tcrmgr put -port 1999 -sep '|' localhost "$i" "x|$((`date +%s`+i))"; done And to verify the keys, I did this: $ tcrmgr list -pv -port 1999 -sep '|' localhost I also tried sending HUP to it: $ kill -HUP `pgrep -f 'ttserver -port 1999'` Can you always reproduce this when SIGHUP is sent to the process? Or is it completely random? Regards, Örjan
signature.asc
Description: Digital signature
