eiginn / coreemu

Automatically exported from code.google.com/p/coreemu
BSD 2-Clause "Simplified" License
0 stars 1 forks source link

datacollect and shutdown hooks not called from batch mode #187

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Using 'core -b' to start a scenario in batch mode, then 'core -c' to shutdown, 
hooks for the datacollect and shutdown states are not invoked.

Two different code paths:
1. For 'core -c' a Session Message is sent with the delete flag.
2. For the stop button (GUI), first a datacollect event is sent, then node and 
link delete messages, and cored decides when to enter the shutdown state.

Original issue reported on code.google.com by ahrenh...@gmail.com on 8 Mar 2013 at 3:48

GoogleCodeExporter commented 9 years ago
from this thread:
http://pf.itd.nrl.navy.mil/pipermail/core-users/2013-March/001178.html

Original comment by ahrenh...@gmail.com on 8 Mar 2013 at 3:49

GoogleCodeExporter commented 9 years ago
bug still exists in r538 (Boeing r1855)

datacollect hook script is invoked when 'core-gui -c' is used, but not the 
shutdown hook script

two code paths:
1. user presses stop -> handleNodeMessage (node delete) -> checkshutdown()
2. user shuts down session -> handleSessionMessage (session delete) -> 
session.shutdown()

#1 does not seem to invoke session.shutdown(), are session helper objects 
properly shut down?

for #2, it doesn't work to run session.checkshutdown() following 
session.shutdown() (session dir is removed) or before (need to wait for nodes 
to be destroyed)

Original comment by ahrenh...@gmail.com on 28 Jul 2014 at 4:17