[SOLVED] startx delay

Gerard Lally · 05-28-2017, 12:23 PM

14.2 amd64 inittab runlevel 3 kde4

Why is there a delay with startx whenever the internet connection is down? Is kde configured by default to call home for some reason? Not sure it's relevant but I have X configured not to listen on tcp.

As soon as I log in netstat -a | grep tcp | grep -v domain returns this:

Code:

tcp        0      0 *:1714                  *:*                     LISTEN     
tcp        0      0 localhost:ipp           *:*                  LISTEN     
tcp        0      0 localhost:rndc          *:*                 LISTEN     
tcp6       0      0 ::1:ipp                 [::]:*                  LISTEN     
tcp6       0      0 ::1:rndc                [::]:*                  LISTEN

1714 is kde-connect
ipp is my printer, connected by ethernet to my router
rndc is named

Conrad_Troutman · 05-28-2017, 12:32 PM

It's caused by hostname being called with the -f option (line 159 in startx on slackware-current). When I've had this problem in the past I just changed that line to call `cat /etc/HOSTNAME` instead of the hostname command. It may not be a very smart solution, I don't know.

Gerard Lally · 05-28-2017, 01:10 PM

Quote:

Originally Posted by Conrad_Troutman

It's caused by hostname being called with the -f option (line 159 in startx on slackware-current). When I've had this problem in the past I just changed that line to call `cat /etc/HOSTNAME` instead of the hostname command. It may not be a very smart solution, I don't know.

That'll do me. Thank you.

GazL · 05-28-2017, 01:11 PM

I map the hostname to 127.1.1.1 in /etc/hosts to avoid this sort of thing.

Code:

# /etc/hosts ###########################################################
#
#   Hostname to address mappings for the TCP/IP subsystem. 
#

# loopback
127.0.0.1               localhost
::1                     localhost

# Hostname
127.1.1.1               ws1.my.domain ws1

# my.domain: gateway
192.168.0.1             gw.my.domain gw

# my.domain: static addresses
192.168.0.2             s1.my.domain s1

# my.domain: dhcp pool
192.168.0.201           d201.my.domain d201
192.168.0.202           d202.my.domain d202
192.168.0.203           d203.my.domain d203
192.168.0.204           d204.my.domain d204
192.168.0.205           d205.my.domain d205
192.168.0.206           d206.my.domain d206
192.168.0.207           d207.my.domain d207
192.168.0.208           d208.my.domain d208
192.168.0.209           d209.my.domain d209

######################################################## End of hosts. #

The wireless interface actually doing all the work will have one of the dhcp addresses assigned via wpa_supplicant/dhcpcd.

Gerard Lally · 05-28-2017, 01:55 PM

Quote:

Originally Posted by GazL

I map the hostname to 127.1.1.1 in /etc/hosts to avoid this sort of thing.

Code:

# /etc/hosts ###########################################################
#
#   Hostname to address mappings for the TCP/IP subsystem. 
#

# loopback
127.0.0.1               localhost
::1                     localhost

# Hostname
127.1.1.1               ws1.my.domain ws1

+1 for the suggestion. It's interesting, however, that the 127.1.1.1 address is not configured out of the box on NetBSD, as it is on Slackware.

NetBSD:

Code:

cajetan$ ping 127.1.1.1 
PING 127.1.1.1 (127.1.1.1): 56 data bytes
ping: sendto: Network is unreachable
ping: sendto: Network is unreachable

Slackware:

Code:

[gerard]$ ping 127.1.1.1
PING 127.1.1.1 (127.1.1.1) 56(84) bytes of data.
64 bytes from 127.1.1.1: icmp_seq=1 ttl=64 time=0.031 ms
64 bytes from 127.1.1.1: icmp_seq=2 ttl=64 time=0.035 ms