#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 14 years ago by
comment:2 Changed 14 years ago by
| Owner: | set to David Sommerseth |
|---|---|
| Status: | new → accepted |
comment:3 Changed 14 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
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 14 years ago by
| Milestone: | → beta 2.2 |
|---|
Originally posted to SF.net bug tracker by somebody (anonymous)