From owner-freebsd-stable Tue Apr 17 4:44:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from pcwin002.win.tue.nl (pcwin002.win.tue.nl [131.155.71.72]) by hub.freebsd.org (Postfix) with ESMTP id 1027B37B424 for ; Tue, 17 Apr 2001 04:44:11 -0700 (PDT) (envelope-from stijn@pcwin002.win.tue.nl) Received: (from stijn@localhost) by pcwin002.win.tue.nl (8.11.3/8.11.3) id f3HBhts65652 for freebsd-stable@freebsd.org; Tue, 17 Apr 2001 13:43:55 +0200 (CEST) (envelope-from stijn) Date: Tue, 17 Apr 2001 13:43:55 +0200 From: Stijn Hoop To: freebsd-stable@freebsd.org Subject: delayed security email? Message-ID: <20010417134355.A58593@pcwin002.win.tue.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I recently installed a new machine for testing NFS mounts. Things worked great, so I went to attend to other things. I tested the NFS mounts with my work machine as the server. Now I regularly upgrade my work machine, so it gets reboot every couple of days. I forgot that the client still had /usr/ports (and only /usr/ports) mounted from my work machine, so I didn't unmount that first. In fact, I failed to look at the client for a few days. What I didn't notice at first was that the client failed to report its security status from then on. I didn't get any daily mail from that machine anymore. Today I found out that I had a stale mount hanging around on the client. After turning my work machine into an NFS server once again, my 'cd /usr/ports' got unstuck (of course). However, I instantaneously got all delayed security mails from last week onward, all of which had kernel log messages like this pcwin165.win.tue.nl kernel log messages: > nfs server pcwin002:/usr/ports: not responding > nfs server pcwin002:/usr/ports: is alive again Now, I know for sure that I only had /usr/ports mounted during the time. And I think it's very strange that the daily security check would fail to mail me when a mount of /usr/ports is failing. Can anyone explain why this would happen? I don't think the security mail should be delayed for a reason like this. FWIW, I don't have weekly_status_pkg_enable set, and I can't think of anything else in periodic that needs /usr/ports. The client is running FreeBSD 4.3-RC #0: Tue Apr 3 10:28:00 CEST 2001. I don't have anything interesting in rc.conf, but I'll gladly provide it if required. --Stijn -- Tact, n.: The unsaid part of what you're thinking. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message