Nmap Development mailing list archives
Re: ioctl issue scanning /24 networks
From: Jacek Wielemborek <d33tah () gmail com>
Date: Fri, 06 Jun 2014 14:59:44 +0200
06/06/2014 14:47:29 Nicolas Greneche <nicolas.greneche@univ- paris13.fr>:
Does "--nsock-engine select" stands for a compilation option (but I didn't see it in ./configure --help) or an argument tu nmap command (not seen in nmap -h) ?
It's an nmap command line option. Surprisingly, it's not there in
nmap --help, but "man nmap" mentions it:
--nsock-engine epoll|kqueue|poll|select .
Enforce use of a given nsock IO
multiplexing engine. Only the
select(2)-based fallback engine is
guaranteed to be available on your
system. Engines are named after the name
of the IO management facility they
leverage. Engines currenty implemented
are epoll, kqueue, poll, and select, but
not all will be present on any platform.
Use nmap -V to see which engines are
supported.Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Sent through the dev mailing list http://nmap.org/mailman/listinfo/dev Archived at http://seclists.org/nmap-dev/
Current thread:
- ioctl issue scanning /24 networks Nicolas Greneche (Jun 06)
- Re: ioctl issue scanning /24 networks Daniel Miller (Jun 06)
- Re: ioctl issue scanning /24 networks Nicolas Greneche (Jun 06)
- Re: ioctl issue scanning /24 networks Jacek Wielemborek (Jun 06)
- Re: ioctl issue scanning /24 networks Nicolas Greneche (Jun 16)
- Re: ioctl issue scanning /24 networks Nicolas Greneche (Jun 06)
- Re: ioctl issue scanning /24 networks Daniel Miller (Jun 06)
