mirror of
https://github.com/nmap/nmap.git
synced 2025-12-09 06:01:28 +00:00
Added a --nsock-engine option to nmap, nping and ncat to enforce use of a
given nsock IO engine. [Henri]
This commit is contained in:
@@ -2860,6 +2860,23 @@ worth the extra time.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><option>--nsock-engine
|
||||
epoll|select</option>
|
||||
<indexterm><primary><option>--nsock-engine</option></primary></indexterm>
|
||||
<indexterm><primary>Nsock IO engine</primary></indexterm>
|
||||
</term>
|
||||
<listitem>
|
||||
|
||||
<para>Enforce use of a given nsock IO multiplexing engine. Only the
|
||||
<literal>select(2)</literal>-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
|
||||
<literal>epoll</literal> and <literal>select</literal>.</para>
|
||||
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term>
|
||||
<option>-T
|
||||
|
||||
Reference in New Issue
Block a user