… | |
… | |
2 | TODO: keeping fork objects around after run - problems? |
2 | TODO: keeping fork objects around after run - problems? |
3 | TODO: many forks in a row fail to fork all |
3 | TODO: many forks in a row fail to fork all |
4 | TODO: $AnyEvent::Fork::Template vs. $TEMPLATE |
4 | TODO: $AnyEvent::Fork::Template vs. $TEMPLATE |
5 | TODO: $AnyEvent::Fork::Serve::OWNER expose somehow? |
5 | TODO: $AnyEvent::Fork::Serve::OWNER expose somehow? |
6 | |
6 | |
|
|
7 | TODO: document security of infomration passing |
7 | 1.32 Wed 26 Jan 2022 17:42:30 CET |
8 | 1.32 Wed 26 Jan 2022 17:42:30 CET |
8 | - new strategy for reaping children: as local $SIG{CHLD} will |
9 | - new strategy for reaping children: as local $SIG{CHLD} will |
9 | reset rather than restore signal handlers, we try to reap |
10 | reset rather than restore signal handlers, we try to reap |
10 | children manually in the fork server. This might cause zombies |
11 | children manually in the fork server. This might cause zombies |
11 | to stay around for a long time in case there is a race and |
12 | to stay around for a long time in case there is a race and |