Re: Can a configuration item be cleared in the server.conf file

Bo Berglund <[email protected]>
Newsgroups gmane.network.openvpn.user
Message-ID <[email protected]>
On Sun, 21 Jan 2024 21:59:01 +0000, tincantech via Openvpn-users
<[email protected]> wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA256
>
>Hi,
>
>On Sunday, January 21st, 2024 at 9:17 PM, Gert Doering <[email protected]> wrote:
>
>> Hi,
>> 
>> On Sun, Jan 21, 2024 at 09:08:01PM +0100, Bo Berglund wrote:
>> 
>> > Now I wonder if there is anything at all one can do on a server instance level
>> > to disable that setting such that the timestamps are returned to the logfiles?
>> > Like:
>> > "reset suppress-timestamps"
>> > or similar?
>> 
>> 
>> OpenVPN does not assume to be called from something that sets undesired
>> variables to be cleared again later on - which would make the config
>> handling even more complex than it is today.
>> 
>> Systemd assumes that the world behaves like systemd developers think
>> it should, so "no timestamps" and "all logs go to the systemd journal".
>
>If --suppress-timestamps use is aimed at systemd then perhaps options --log
>and --log-append, which both ultimately bypass systemd-journald, are in use
>then they could reset the --suppress-timestamps flag on use.
>
>If --suppress-timestamps is used after all --log* options then it would be in
>effect, like other options, whereby "last option wins!".
>
>Regards
>tct

My interest was started by your post in the other thread:

>> For posterity:
>> 
>> Server log --verb 4:
>> 
>> <verbatim>
>> 
>> 2024-01-21 03:06:59 us=764987 10.1.101.36:33510 [tct.66.c.w10.dan] Peer Connection Initiated with [AF_INET]10.1.101.36:33510
>> 2024-01-21 03:06:59 us=765204 MULTI: new connection by client 'tct.66.c.w10.dan' will cause previous active sessions by this client to be dropped.  Remember to >> use the --duplicate-cn option if you want multiple clients using the same certificate or username to concurrently connect.
>> 2024-01-21 03:06:59 us=765233 MULTI_sva: pool returned IPv4=10.126.66.121, IPv6=(Not enabled)
>> 2024-01-21 03:06:59 us=765311 OPTIONS IMPORT: reading client specific options from: tuns_12666u/CCD_subnet/tct.66.c.w10.dan
>> TEST --client-connect script
>> 
>> </verbatim>

The fact that your logs do not show the timestamp missing or using the
non-intuitive "seconds since 1970" or whatever it is that the
--suppress-timestamps gives you made me think I had somehow missed a setting...

Your timestamps is what I would like my logs to show.
And I specify a path to the logs inside the /etc/openvpn/log dir.

But your example might be from a system not using systemd?


-- 
Bo Berglund
Developer in Sweden
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.