Modify ↓
Opened at 2008-06-25T23:48:19Z
Last modified at 2016-07-07T20:51:01Z
#427 new task
Some rough edges in ForkDaemon mode
Reported by: | wilmer | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | BitlBee | Version: | 1.2.1 |
Keywords: | Cc: | ||
IRC client+version: | Client-independent | Operating System: | Public server |
OS version/distro: |
Description
Currently, ForkDaemon child processes don't free() any/most of the not very useful stuff they inherit from the parent process. I was hoping that this wouldn't be a problem as long as nothing ever gets written there (copy on write?) but I may be wrong.
Try to free() as much as possible.
Also, it'd be nice to not silently drop dead IPC connections in some cases. For example, the master process should notice abnormal child process terminations (signals, etc) and notify operators, if any.
Attachments (0)
Change History (2)
comment:1 Changed at 2008-08-18T22:29:07Z by
comment:2 Changed at 2016-07-07T20:51:01Z by
Milestone: | 1.2.x |
---|
Note: See
TracTickets for help on using
tickets.
Actually these were mostly some memory leaks (that unfortunately weren't all that obvious in valgrind IIRC). Those are fixed, now I just want to do the last part (detection of unexpected child process deaths).