I've noticed that a few times before, but today I had a longer ISP
outage and I could look into that more closely.
When I don't have a working internet connection a compile with CC hangs
around doing nothing (it looks like it's waiting for a network timeout).
A quick truss showed this:
<snip>
423: time() = 1258538710
423: getpid() = 423 [422]
423: uname(0x08511628) = 1
423: open("/etc/netconfig", O_RDONLY) = 4
423: fstat64(4, 0x080461A0) = 0
423: fstat64(4, 0x080460B0) = 0
423: ioctl(4, TCGETA, 0x08046150) Err#25 ENOTTY
423: read(4, " # C D D L H E A D E".., 2560) = 2137
423: read(4, 0x086B77C4, 2560) = 0
423: llseek(4, 0, SEEK_CUR) = 2137
423: llseek(4, 0, SEEK_SET) = 0
423: read(4, " # C D D L H E A D E".., 2560) = 2137
423: read(4, 0x086B77C4, 2560) = 0
423: llseek(4, 0, SEEK_CUR) = 2137
423: close(4) = 0
423: open("/dev/udp", O_RDONLY) = 4
423: ioctl(4, SIOCGLIFNUM, 0x08046680) = 0
423: close(4) = 0
423: open("/dev/udp", O_RDONLY) = 4
423: ioctl(4, SIOCGLIFNUM, 0x08046680) = 0
423: close(4) = 0
423: getuid() = 101 [101]
423: mmap(0x00010000, 65536, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_ANON|MAP_ALIGN, -1, 0) = 0xC9640000
423: getuid() = 101 [101]
423: getuid() = 101 [101]
423: open64("/var/run/name_service_door", O_RDONLY) = 4
423: fcntl(4, F_SETFD, 0x00000001) = 0
423: door_info(4, 0xC9841F64) = 0
422: waitid(P_PGID, 421, 0x080461D0, WEXITED|WTRAPPED) (sleeping...)
423: door_call(4, 0x08046460) (sleeping...)
<hang>
Where is it trying to connect to? And can this be turned off? It's
very annoying when you don't have a working internet connection and you
even can't do local development because of network timeouts.
-- Christian
