summaryrefslogtreecommitdiff
path: root/lib/Multi
diff options
context:
space:
mode:
authorYorhel <git@yorhel.nl>2009-11-17 22:30:55 +0100
committerYorhel <git@yorhel.nl>2009-11-17 22:30:55 +0100
commit09db8c10ff6ebcd23b8b5ab8a30c219ad298a1a0 (patch)
tree8836b8e4dc9150490aabebbb8cdb6a8a609cf19e /lib/Multi
parent1bddfcb5862be5f40d1a4e5595aa22d79b67b9cd (diff)
Multi::Core: Call $poe_kernel->has_forked() after forking
Normally this shouldn't be necessary as the forking is done before any POE::Kernel functions has been called. It seems, however, that the POE::Kernel is already started in the import() function, meaning that it's already running anyway. Not sure whether the import() has changed to start the kernel or that something else changed that I'm only seeing this now, ow well.
Diffstat (limited to 'lib/Multi')
-rw-r--r--lib/Multi/Core.pm1
1 files changed, 1 insertions, 0 deletions
diff --git a/lib/Multi/Core.pm b/lib/Multi/Core.pm
index 6388c924..28555e51 100644
--- a/lib/Multi/Core.pm
+++ b/lib/Multi/Core.pm
@@ -36,6 +36,7 @@ sub run {
pause();
exit 1;
}
+ $poe_kernel->has_forked();
# spawn our SQL handling session
my @db = @{$VNDB::O{db_login}};