Project

General

Profile

Bug #3300

Updated by tuxillo about 1 year ago

System environment: 

 <pre> 
 root@dragonflybsd /home/adrian # uname -a 
 DragonFly dragonflybsd.v-zone.lan.dac 6.0-RELEASE DragonFly v6.0.1-RELEASE #1: Thu Oct 14 18:25:27 CEST 2021 adrian@dragonflybsd.v-zone.lan.dac:/usr/obj/usr/src/sys/X86_64_GENERIC x86_64 
 </pre> 

 Running DragonFlyBSD inside a Debian KVM virtualization as a guest with hardware acceleration, 
 I can't run Xvnc (from the TigerVNC package) in WAIT mode using the INETD daemon supplied with the base system. 

 Running XVnc from INETD in NOWAIT mode works fine though! It is only about the WAIT mode, and I would like to use the WAIT mode, to have a long lasting Xorg session. 

 Here is my stanza from /etc/inetd.conf, to reproduce the error. 

 At first, the working stanza — in NOWAIT mode: 

 <pre> 
 5916              stream            tcp               nowait            adrian            /usr/libexec/tcpd                 /usr/local/bin/Xvnc       :16 -inetd -desktop dragonflybsd.v-zone.lan.dac:16 -query localhost -once -geometry 1680x1050 -depth 24 -rfbauth /home/adrian/.vnc/passwd -rfbport 5916 -Log *:syslog:30 
 </pre> 

 Now, the NOT working stanza, in WAIT mode: 

 <pre> 
 5916              stream            tcp               wait            adrian            /usr/libexec/tcpd                 /usr/local/bin/Xvnc       :16 -inetd -desktop dragonflybsd.v-zone.lan.dac:16 -query localhost -once -geometry 1680x1050 -depth 24 -rfbauth /home/adrian/.vnc/passwd -rfbport 5916 -Log *:syslog:30 
 </pre> 

 Running the second command through the INETD daemon, /var/log/messages gets flooded by the constantly restarting Xvnc with this: 
 <pre> 

 Oct 25 18:51:01 dragonflybsd Xvnc[10132]: warning: can't get client address: Socket is not connected 
 Oct 25 18:51:01 dragonflybsd inetd[9859]: /usr/libexec/tcpd[10132]: exited, status 1 
 Oct 25 18:51:01 dragonflybsd Xvnc[10133]: warning: can't get client address: Socket is not connected 
 Oct 25 18:51:02 dragonflybsd inetd[9859]: /usr/libexec/tcpd[10133]: exited, status 1 
 Oct 25 18:51:02 dragonflybsd Xvnc[10134]: warning: can't get client address: Socket is not connected 
 Oct 25 18:51:02 dragonflybsd inetd[9859]: /usr/libexec/tcpd[10134]: exited, status 1 
 Oct 25 18:51:02 dragonflybsd Xvnc[10135]: warning: can't get client address: Socket is not connected 
 Oct 25 18:51:02 dragonflybsd inetd[9859]: /usr/libexec/tcpd[10135]: exited, status 1 
 Oct 25 18:51:02 dragonflybsd Xvnc[10136]: warning: can't get client address: Socket is not connected 
 Oct 25 18:51:02 dragonflybsd inetd[9859]: /usr/libexec/tcpd[10136]: exited, status 1 
 Oct 25 18:51:02 dragonflybsd inetd[9859]: 5916/tcp server failing (looping), service terminated 
 </pre> 

 Removing /usr/libexec/tcpd in beforehand of Xvnc, the error is this: 

 <pre> 
 Oct 25 18:52:11 dragonflybsd :16[10424]: TcpSocket: unable to get peer name for socket 
 Oct 25 18:52:11 dragonflybsd :16[10424]: Connections: closed: ::0 
 Oct 25 18:52:11 dragonflybsd :16[10426]: TcpSocket: unable to get peer name for socket 
 Oct 25 18:52:11 dragonflybsd :16[10426]: TcpSocket: unable to get peer name for socket 
 Oct 25 18:52:11 dragonflybsd :16[10426]: Connections: accepted: ::0 
 Oct 25 18:52:11 dragonflybsd :16[10426]: TcpSocket: unable to get peer name for socket 
 Oct 25 18:52:11 dragonflybsd :16[10426]: TcpSocket: unable to get peer name for socket 
 Oct 25 18:52:11 dragonflybsd :16[10426]: Connections: closed: ::0 
 Oct 25 18:52:11 dragonflybsd :16[10439]: TcpSocket: unable to get peer name for socket 
 Oct 25 18:52:11 dragonflybsd :16[10439]: TcpSocket: unable to get peer name for socket 
 Oct 25 18:52:11 dragonflybsd :16[10439]: Connections: accepted: ::0 
 Oct 25 18:52:11 dragonflybsd :16[10439]: TcpSocket: unable to get peer name for socket 
 </pre> 

 As you can see, INETD is constantly respawning Xvnc. 

 Thank you for noticing this issue. 

 Sincerely, 

 Adrian Kieß 

Back