Opened 11 years ago

Closed 11 years ago

Last modified 11 years ago

#40 closed Bug / Defect (fixed)

Documentation bug in the manual: explicit-exit-notify

Reported by: Samuli Seppänen Owned by: David Sommerseth
Priority: major Milestone: beta 2.2
Component: Documentation Version: OpenVPN 2.1.0 / 2.1.1 (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords:
Cc:

Description

In the manuals for 2.0.9 and 2.1, the n parameter to --explicit-exit-notify is described as the number of *retries*, which is misleading.
One could think that when n=0, there is one try and no retries, but when n=0 there is no notification at all.

My suggestion is to replace 'retries' with 'tries'.

Change History (4)

comment:1 Changed 11 years ago by Samuli Seppänen

Originally posted to SF.net bug tracker by somebody (anonymous)

comment:2 Changed 11 years ago by David Sommerseth

Owner: set to David Sommerseth
Status: newaccepted

comment:3 Changed 11 years ago by David Sommerseth

Resolution: fixed
Status: acceptedclosed

Applied to bugfix2.1, to be merged into allmerged and beta2.2.

commit bbea5bb30f8148546bee0a72e409c6089b84b757
Author: David Sommerseth <dazo@…>
Date: Fri Nov 12 23:10:32 2010 +0100

Clarified --explicit-exit-notify man page entry


Reformulated parts of this entry to clarify that the OpenVPN
will not attempt notifying the server unless this option is used.


This misunderstanding was reported anonymously to the old SF.net
tracker.


Signed-off-by: David Sommerseth <dazo@…>
Trac-ticket: 40

comment:4 Changed 11 years ago by David Sommerseth

Milestone: beta 2.2
Note: See TracTickets for help on using tickets.