Modify ↓
Opened at 2010-07-25T16:36:55Z
Closed at 2010-07-28T00:08:33Z
#656 closed defect (fixed)
100% cpu when trying to stop/restart non-forked bitlbee
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | major | Milestone: | |
Component: | BitlBee | Version: | devel |
Keywords: | Cc: | ||
IRC client+version: | Client-independent | Operating System: | Linux |
OS version/distro: | Debian Lenny |
Description
From syslog:
Jul 25 19:30:25 fffu bitlbee[4707]: SIGTERM received, cleaning up process.
And that's it.
Attachments (0)
Change History (4)
comment:1 Changed at 2010-07-25T19:45:36Z by
comment:2 Changed at 2010-07-26T23:26:47Z by
Priority: | normal → major |
---|
I know more or less where this is but have to figure out how to fix it properly. May take a few more days. :-(
comment:4 Changed at 2010-07-28T00:08:33Z by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
Same happens when I send SIGTERM to forked bitlbee's child after /etc/init.d/bitlbee stop