You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given the reliability issues I'm seeing in #15, it would be nice if rho wrote out the report occasionally so that if the tool needs to be killed due to hanging, some amount of reporting would still be available.
Or catch ^C and generate a report at abnormal exit.
Some of the subnets I need to scan are quite large and having to scan the repeatedly as I debug issues is not friendly to our subnets :). In many cases a partial report would be good enough. (or as in #15, the scan is actually done, rho just won't exit due to zombie ssh threads.)
Periodic would probably only work with the --output option -- not stdout.
The text was updated successfully, but these errors were encountered:
You may wish to look at my other issues I've reported -- there are some flaws (leaked paramikio threads) that keep rho from exiting. I have also seen cases where authentication hangs within paramiko on some unknown devices, and then rho never finishes.
In the end, I used nmap to find all of my nodes that had ssh open, then created a one-off rho config for each ip address, then concatenated all the results. gnu-parallel might be useful to you for paralleling the single-ip rho runs.
Given the reliability issues I'm seeing in #15, it would be nice if rho wrote out the report occasionally so that if the tool needs to be killed due to hanging, some amount of reporting would still be available.
Or catch ^C and generate a report at abnormal exit.
Some of the subnets I need to scan are quite large and having to scan the repeatedly as I debug issues is not friendly to our subnets :). In many cases a partial report would be good enough. (or as in #15, the scan is actually done, rho just won't exit due to zombie ssh threads.)
Periodic would probably only work with the --output option -- not stdout.
The text was updated successfully, but these errors were encountered: