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

[aslamK]

On 6/5/25 02:43, Werner Koch via Gnupg-users wrote:
> On Tue,  3 Jun 2025 22:27, aslamK said:
> 
>> The "Connection refused" message can be avoided by setting the
>> 'log-file' option to a file instead of the socket. This causes the
> 
> Or by not setting the log-file option at all.  If for some reason it is
> set in some config files you may override it with
> 
>    --logger-fd 2
> 
> To reestabish the default of writing to stderr.
> 

Thanks. Yes, after doing the following, the output does get written to 
stderr (to terminal in an interactive session):

	echo 'log-file:16:' | gpgconf --change-options gpg

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


$ gpg --version
gpg (GnuPG) 2.4.4
libgcrypt 1.10.3

-- 
aslamK