Opened 3 years ago

Last modified 3 years ago

#884 accepted Bug / Defect

client-disconnect script not passed any arguments

Reported by: hvenev Owned by: Gert Döring
Priority: major Milestone:
Component: Configuration Version: OpenVPN 2.4.0 (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords:


No arguments seem to be passed to the client-disconnect script. According to the documentation it should be passed the same file given to client-connect.

Change History (2)

comment:1 Changed 3 years ago by tincantech

You might choose to enhance your question with some details. eg: configs/logs etc

comment:2 Changed 3 years ago by Gert Döring

Owner: set to Gert Döring
Status: newaccepted

This is a man page bug. It is very clear in stating that...

              The  --client-disconnect  command is passed the same pathname as
              the corresponding --client-connect command as its last argument.
              (after any arguments specified in cmd ).

but since there is no need for such a file (there is nothing that could be configured here, the client instance goes away right this moment), the code does not do it. No idea why the man page says so.

The man page change was done by Jonathan K. Bullard in commit d62859980c30362b36b7338fc99fe76e4ecb2cbd (cleaning up documentation in general), but I think the part about disconnect is just wrong. Since I ACKed the change, seems I'll have to fix it :-)

Note: See TracTickets for help on using tickets.