From owner-freebsd-current@FreeBSD.ORG Sat Mar 3 01:57:23 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8219106564A; Sat, 3 Mar 2012 01:57:23 +0000 (UTC) (envelope-from rabgvzr@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6C8C08FC0A; Sat, 3 Mar 2012 01:57:23 +0000 (UTC) Received: by ggnk4 with SMTP id k4so1239832ggn.13 for ; Fri, 02 Mar 2012 17:57:22 -0800 (PST) Received-SPF: pass (google.com: domain of rabgvzr@gmail.com designates 10.236.79.193 as permitted sender) client-ip=10.236.79.193; Authentication-Results: mr.google.com; spf=pass (google.com: domain of rabgvzr@gmail.com designates 10.236.79.193 as permitted sender) smtp.mail=rabgvzr@gmail.com; dkim=pass header.i=rabgvzr@gmail.com Received: from mr.google.com ([10.236.79.193]) by 10.236.79.193 with SMTP id i41mr16884187yhe.16.1330739842864 (num_hops = 1); Fri, 02 Mar 2012 17:57:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Vo0Xkyqt3aQUDuAzd6Ov5otmyNgy7r5BZ7mF4dytmu8=; b=ehRDTTYQWoDRE+QdHvNVr4C2L5lOqqc0hOie1hEL6zaeRdk1JUjD0VS7yjIK+b07m0 /5T+0owZgNCHeDP3vDr/siLEQw0k7dxbaLOPmq6dhDTkgtDMRXL6wkcYY91UQBlo0tXv +HKY99frvPeo1sWwykUnV8g7KffrfMAyvnaI3rQgZbf5QwDUQWh+jw84IclUMEpJOL7i SYFDOvykeWeCNgQL6mb/k7aLHIfZkGx5HX+6hkn1h7gXUDU6ul5Bb335oKq2iUjKgP8Q MrtHr8r82Q2p4eWs8HfemIfv2YZRW2B7wOgq9AxEFQmKnYa2ryPPYz2kVqnvLY0OHwkb shcw== MIME-Version: 1.0 Received: by 10.236.79.193 with SMTP id i41mr13444791yhe.16.1330739842808; Fri, 02 Mar 2012 17:57:22 -0800 (PST) Received: by 10.236.144.130 with HTTP; Fri, 2 Mar 2012 17:57:22 -0800 (PST) In-Reply-To: <20120303002608.GB65949@in-addr.com> References: <20120302231645.GA65949@in-addr.com> <20120303002608.GB65949@in-addr.com> Date: Fri, 2 Mar 2012 20:57:22 -0500 Message-ID: From: Rotate 13 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: Gary Palmer Subject: Re: src.conf ignored; phantom named X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Mar 2012 01:57:24 -0000 On Fri, 02 Mar 2012 19:26:08 -0500, Gary Palmer wrote: > fstat only shows the inode number of the file, e.g. [...] Oops. I should have paid more attention (or installed sysutils/lsof) before piping around output of an unfamiliar tool... > I don't recall seeing in your original message - after the installworld, > did you reboot? Does "ps auxww | grep named" show that the process > predates your installworld? (The 9th column should show when the process > started, from memory) The system was rebooted twice since installworld, while testing different things. Unfortunately, the system panicked while I was digging around (seemed hardware-related; I do not think this was related to the original problem). When it came up, named was not running. I do need the machine to actually work, so I dumped the filesystems with system stuff (/usr, /var, /etc...) and started nuking/rebuilding a clean install. Maybe I will someday poke around the dumps and find something, but at this point I suspect it is either serious configuration error (PEBKAC) or something else not FreeBSD's fault. > I'm also curious as to why two instances of named appear to be running. > On the face of it that would appear to be broken as only one could bind > to port 53. You're not running jails or anything similar are you? No jails. dmesg had repeated messages about inability to bind ports - that's what gave me the clue that named was running in the first place. I was experimenting with a variety of dnsware, and dnsmasq was peacefully occupying 53 udp. So, neither named process was able to bind (no pun intended). And named was obviously started significantly after boot... Thanks for all the help. I wish this came out more usefully for the archives - but it seems to be wind up as a combination of "luser forgot to make delete-old" and "bizarre, unsolved UNIX mystery".