Re: [Zenmap] Terminal Problem due to Nmap Runtime Interaction

[Jay Bosamiya <jaybosamiya () gmail com>]

Hi All!

Attached is a patch that sends a SIGTERM and polls every 0.5 seconds to
see if the process has terminated. If after 5 seconds, it hasn't
terminated yet then a SIGKILL is sent.

Feedback is welcome. :)

Cheers,
Jay

If that process steps out of line then it's KILL DASH NINE! :D
(http://www.youtube.com/watch?v=Fow7iUaKrq4)

On Monday 16 June 2014 03:48 PM, Jay Bosamiya wrote:
> Hi All!
>
> If I were to open Zenmap from terminal, and then Cancel a running
> scan, then the terminal is in an unusable state (typed characters are
> not echoed after closing Zenmap). I am forced to close the terminal
> and open a new one.
>
> This is caused because a SIGKILL is sent to Nmap when we cancel a
> scan. I think that this should be a SIGTERM so as to allow for a clean
> shutdown.
>
> Attached is a patch that does this.
>
> Note: There is runtime interaction when you run Zenmap from terminal.
> You can notice this by pressing keys on the terminal when a scan is
> running.
> I think that there should *not* be any runtime interaction in this
> case. Since not a lot of people run Zenmap from terminal, I think it'd
> be a low priority but should probably be done at some point of time in
> the future.
>
> Cheers,
> Jay

_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/