X-Git-Url: http://bilbo.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/aad6b6c4c7b1454dd284f822ba6f52e790f42c6e..512273b5dab057e0f93aaed9c09c79d0e4960b61:/docs/source/Modeling_howtos.rst diff --git a/docs/source/Modeling_howtos.rst b/docs/source/Modeling_howtos.rst index f6589f7c5c..0840ceec50 100644 --- a/docs/source/Modeling_howtos.rst +++ b/docs/source/Modeling_howtos.rst @@ -93,6 +93,10 @@ Another possibility is to use the functions take a profile, that can be a fixed profile exhaustively listing the events, or something else if you wish. +For further reading, you could turn to :ref:`this example ` +on how to react to communication failures, or :ref:`this one ` +on how to attach a state profile to hosts and react to execution failures. + .. _howto_multicore: Modeling multicore machines @@ -152,9 +156,9 @@ programs actually die and restart during a reboot. Since there are many ways to model it, SimGrid does not do any modeling choice for you but the most obvious ones. -Any actor running on a host that is shut down will be killed and all -its activities will be automatically canceled. If the actor killed was -marked as auto-restartable (with :cpp:func:`simgrid::s4u::Actor::set_auto_restart`), +Any actor running on a host that is shut down will be killed and all +its activities will be automatically canceled. If the actor killed was +marked as auto-restartable (with :cpp:func:`simgrid::s4u::Actor::set_auto_restart`), it will start anew with the same parameters when the host boots back up. By default, shutdowns and boots are instantaneous. If you want to