On Tue, Oct 21, 2014 at 9:10 AM, Martin Lucina <[email protected]> wrote: > Hi, > > my project is now complete (at least for now) and at this point I'm just > tying up some loose ends. > > One of those is that I would like to shutdown a rump kernel cleanly at the > point when the application is done with it. This is not a necessity, as the > application doesn't do much else after that but I prefer to match my > malloc()s and free()s :-) > > Currently all I'm doing is this: > > rump_pub_etfs_remove ("/dev/image"); > rump_sys_sync (); > > If I change this to do: > > rump_sys_reboot (0x08 /* RB_HALT */, NULL); > > Then my calling thread hangs at that point. I guess I expected that, after > all I did ask it to "halt the processor". However, if I do: > > rump_sys_reboot (0, NULL); > > Then then calling thread appears to exit instead, which is not what I want > either. > > So, what is the preferred way to accomplish this? Should we have a > companion rump_term () to rump_init () for these use cases? > > I'm thinking ahead here, where someone might use this as part of library > functionality, which then gets re-used in unexpected ways.
The problem is that operating systems don't have a built in way to do this... You could run the rump kernel in a different process, if that works for your application. Justin ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
