fcca4f3466
With this change, init becomes able to respond to config changes by restarting the scenario with the new config. To make this feature useful in practice, init must not fail under any circumstances. Even on conditions that were considered as fatal previously and led to the abort of init (such as ambiguous names of the children or misconfiguration in general), init must stay alive and responsive to config changes. |
||
|---|---|---|
| .. | ||
| linux | ||
| config.explicit_routing | ||
| config.wildcard | ||
| main.cc | ||
| pd_args.cc | ||
| target.mk | ||