Re: Client history

On Wed, 28 Feb 2024 14:07:13 +0100, Marc SCHAEFER <[email protected]> wrote:

>On Wed, Feb 28, 2024 at 12:52:17PM +0000, Peter Davis via Openvpn-users wrote:
>> # #!/bin/bash
>> # export script_type="client-connect"
>> # export common_name="CommonName"
>> # export trusted_ip="192.168.129.253"
>> # ./server-events.sh
>
>I did not follow the whole discussion, but why on earth are you assuming that
>your current directly is somewhere known?  This is what ./ means:
>run server-events.sh in the current directory.
>
>Put your script in /usr/local/OPENVPN/scripts and call it as
>/usr/local/OPENVPN/scripts/server-events.sh for example.
>
>> So, why is the script not working in OpenVPN?
>
>If the problem is locating ./server-events.sh it is *possible* that OpenVPN log
>itself (or syslog, or the systemd journal) has some stderr output.
>
>There are other possibly problems, such as access rights (depending on what
>user the script is run on, possibly root).

I am running *all* openvpn scripts from within /etc/openvpn/scripts and I use
the *full path* to the scripts in the conf files calls.

I also keep all of the custom logs (as defined in the conf file) below
/etc/openvpn/log, which is also perfectly accessile by tye openvpn service.

I can for the life of me not understan why someone is hell bent on complicating
the issues here by wandering around in circles in all kinds of strange locations
like:
LOG_FILE="/tmp/Connections.log"

It is like using /var/log and hoping for the best....

It never turns out as you want...


-- 
Bo Berglund
Developer in Sweden