"Can't connect to 'log-socket': Connection refused

[Jakob Bohm]

On 6/6/2025 14:32:41, Werner Koch via Gnupg-users wrote:
> On Thu,  5 Jun 2025 21:14, aslamK said:
>
>> However, if 'log-file' is set in gpg.conf, then the following does not
>> override it; the output is written to the log-file but not to stderr:
>>
>> 	gpg --logger-fd 2 --verify file_to_verify.sig
> I guess file descriptor 2 has already been redirected and is no longer
> stderr inside the gpg process.  On Linux and someother OSes you may use
>
>    --log-file /dev/stderr
Does this work because gpg evaluates --log-file before --logger-fd ?,
or maybe some other parsing quirk ?, because on many GNU/Linux systems,
/dev/stderr is a symlink to /proc/self/fd/2, which in turn just
provides file descriptor 2 of the calling process at the time it tries
to "open" the symlink .

Enjoy

Jakob
-- 
Jakob Bohm, CIO, Partner, WiseMo A/S.  https://www.wisemo.com
Transformervej 29, 2860 Søborg, Denmark.  Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded