# broctl restart --clean **URL:** \ **Category:** Development\ **Tags:** development\ **Created:** [May 15, 2015, 5:31pm UTC](https://community.zeek.org/t/broctl-restart-clean/3597 "2015-05-15T17:31:24Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Aashish\_Sharma1](https://avatars.discourse-cdn.com/v4/letter/a/a88e57/32.png) [@Aashish\_Sharma1](https://community.zeek.org/u/Aashish_Sharma1)\ **Post date:** [May 15, 2015, 5:31pm UTC](https://community.zeek.org/t/broctl-restart-clean/3597/1 "2015-05-15T17:31:24Z")
Just a thought, broctl restart --clean at present does operations in the following sequence: 1) Stop running bro 2) clean up nodes 3) check configurations 4) install new config 5) start bro. If scripts are buggy, this would fail at step (3) and now I am debugging scripts while bro is not running. I think restart --clean should first check configurations (step 3) and then if success, move further or stop. buggy/typo scripts are preffered to be debugged while bro is running. Aashsih ---
**Author:** ![Daniel\_Thayer](https://avatars.discourse-cdn.com/v4/letter/d/8dc957/32.png) [@Daniel\_Thayer](https://community.zeek.org/u/Daniel_Thayer)\ **Post date:** [May 15, 2015, 5:48pm UTC](https://community.zeek.org/t/broctl-restart-clean/3597/2 "2015-05-15T17:48:40Z")
To avoid user confusion, I think it would be good to simply remove the "--clean" option from the restart command. Then, one would just use the "deploy" command. It does a "check", "install", "stop", and "start" (in that order). If someone wants to do things differently, they can still use the individual ("check", "clean", "restart", etc.) commands. ---
**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\ **Post date:** [May 6, 2022, 3:42pm UTC](https://community.zeek.org/t/broctl-restart-clean/3597/3 "2022-05-06T15:42:40Z")