Re: configuring tigervnc-standalone-server to listen on LAN

[Max Nikulin <manikulin@gmail.com>]

On 21/08/2024 03:42, Gary Dale wrote:
> $ systemctl status tigervncserver@:1.service
> ○ tigervncserver@:1.service - Remote desktop service (VNC)
>       Loaded: loaded (/usr/lib/systemd/system/tigervncserver@.service; 
> enabled; preset: enabled)
>       Active: inactive (dead) since Tue 2024-08-20 15:52:31 EDT; 1min 4s 
> ago
[...]
> However I can run vncviewer localhost:5901 and connect as my user.

I hope you have tried "systemctl status" after vncviewer to be sure that 
systemd socket activation is not involved. I suspected that it is 
systemd, not any tigervnc binary that accepts client connection.

I have no idea if "/usr/libexec/tigervncsession-start :1" allows to 
create instance-specific configuration files.

You can override instance-specific systemd parameters in 
/etc/systemd/system/tigervncserver@:1.service.d/*.conf files (I hope :1 
does not need escaping).

It is better to query systemd runtime configuration than to rely on 
"find" or "dpkg -L". The following commands might help to figure out 
which way tigervnc is started

systemctl list-sockets '*vnc*'
systemctl list-units '*vnc*'
systemd-cgls
ps axuwf

and of course (as root)

journalctl -b

I am in doubts if some executable may explicitly call "systemctl start 
tigervncserver@:1.service"

Nowadays I do not see advantages of crontab @reboot over a systemd unit.