From owner-freebsd-stable@FreeBSD.ORG  Sat Jul 27 08:17:54 2013
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id 946984F2;
 Sat, 27 Jul 2013 08:17:54 +0000 (UTC)
 (envelope-from kamikaze@bsdforen.de)
Received: from mail.server1.bsdforen.de (bsdforen.de [82.193.243.81])
 by mx1.freebsd.org (Postfix) with ESMTP id C44AE2C02;
 Sat, 27 Jul 2013 08:17:53 +0000 (UTC)
Received: from mobileKamikaze.norad
 (HSI-KBW-134-3-231-194.hsi14.kabel-badenwuerttemberg.de [134.3.231.194])
 (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.server1.bsdforen.de (Postfix) with ESMTPSA id D994286203;
 Sat, 27 Jul 2013 10:17:48 +0200 (CEST)
Message-ID: <51F3822C.3080905@bsdforen.de>
Date: Sat, 27 Jul 2013 10:17:48 +0200
From: Dominic Fandrey <kamikaze@bsdforen.de>
MIME-Version: 1.0
To: Artem Belevich <art@freebsd.org>
Subject: Re: stopping amd causes a freeze
References: <51ED0060.2050502@bsdforen.de> <20130722100720.GI5991@kib.kiev.ua>
 <51F0DA4B.3000809@bsdforen.de> <20130725100037.GM5991@kib.kiev.ua>
 <51F2AD8C.1000003@bsdforen.de>
 <CAFqOu6jrifTS404h3T0qeWtv-4PR5O4a8dG7z6t3yXkN4_+wDA@mail.gmail.com>
In-Reply-To: <CAFqOu6jrifTS404h3T0qeWtv-4PR5O4a8dG7z6t3yXkN4_+wDA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: Konstantin Belousov <kostikbel@gmail.com>,
 FreeBSD Stable <freebsd-stable@freebsd.org>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Jul 2013 08:17:54 -0000

On 26/07/2013 20:37, Artem Belevich wrote:
> On Fri, Jul 26, 2013 at 10:10 AM, Dominic Fandrey <kamikaze@bsdforen.de>wrote:
> 
>> Amd exhibits several very strange behaviours.
>>
>> a)
>> During the first start it writes the wrong PID into the pidfile,
>> it however still reacts to SIGTERM.
>>
>> b)
>> After starting it again, it no longer reacts to SIGTERM.
>>
> 
> amd does block off signals in some of its sub-processes. For instance amd
> process that works as NFS server and handles amd mount points does block
> off INT/TERM/CHLD/HUP. See /usr/src/contrib/amd/amd/nfs_start.c

Didn't know that. But so sending signals to the process in the pidfile,
used to work™.

>> c)
>> It appear to be no longer reacting to SIGHUP, which is required to
>> tell it that the amd.map was updated.
>>
>>
> Try using 'amq -f' which would ask amd to reload its maps via RPC and
> should work regardless of whether you know the right PID.

amq -m or amq -p just hang there and do nothing right now. As soon as amd
is unbroken this is good to know, though.

Sending a SIGINFO:
load: 0.58  cmd: amq 6071 [kqread] 4.71r 0.00u 0.00s 0% 2132k

-- 
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?