From owner-freebsd-stable@FreeBSD.ORG Fri Jul 26 18:37:22 2013 Return-Path: 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 552B861D for ; Fri, 26 Jul 2013 18:37:22 +0000 (UTC) (envelope-from artemb@gmail.com) Received: from mail-vb0-x233.google.com (mail-vb0-x233.google.com [IPv6:2607:f8b0:400c:c02::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 12E1F2A91 for ; Fri, 26 Jul 2013 18:37:22 +0000 (UTC) Received: by mail-vb0-f51.google.com with SMTP id x17so1459204vbf.38 for ; Fri, 26 Jul 2013 11:37:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=crAq4YqTrvawgMcvQCkUU7V/Xo1t9Dxqo5XdqIBlkLw=; b=u/b6xZwa400e7sW/qyaIEXnrMBGJi36ahXBlDHForoxaNiVMNgOeUzXjf/OUgeqfSa sSmoRWuF0vkwrwpUHcC6qQ+7DzPf7jPh+/vvqUOQjWRzMQByi0HBQSKkOh+YOblu+08p 8SZM2JC7v944jojPWY8jxoiKf2vrVRumdlCZ44/ljG15MbXdpS1hLhJ+/biocYled1W6 ruZJuuWyka4x+D9XA4wCd8FAfbXWwn+kZPL1B8mpJ5bmsiR++QHJ8v5w3npxcnWqc1uW kv05y3G8I3sI1PFBHIe+GZxJbmNBs8fDF2SNpnomzfc+CXwhV3IcjrurULGKw/sN0dWh GdQg== MIME-Version: 1.0 X-Received: by 10.220.201.138 with SMTP id fa10mr4071851vcb.18.1374863841128; Fri, 26 Jul 2013 11:37:21 -0700 (PDT) Sender: artemb@gmail.com Received: by 10.221.41.6 with HTTP; Fri, 26 Jul 2013 11:37:21 -0700 (PDT) In-Reply-To: <51F2AD8C.1000003@bsdforen.de> References: <51ED0060.2050502@bsdforen.de> <20130722100720.GI5991@kib.kiev.ua> <51F0DA4B.3000809@bsdforen.de> <20130725100037.GM5991@kib.kiev.ua> <51F2AD8C.1000003@bsdforen.de> Date: Fri, 26 Jul 2013 11:37:21 -0700 X-Google-Sender-Auth: NlBlkEYHyIXtDXo1lbwjXPa-OmE Message-ID: Subject: Re: stopping amd causes a freeze From: Artem Belevich To: Dominic Fandrey Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Konstantin Belousov , FreeBSD Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Jul 2013 18:37:22 -0000 On Fri, Jul 26, 2013 at 10:10 AM, Dominic Fandrey 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 > > 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. Strangely enough amd man page does not mention SIGHUP at all. amd/doc/am-utils.texi in the source tree does, but only when it talks about hlfsd or about 'type:=auto' maps with 'cache' option. Documentation on am-utils.org matches am-utils.texi. As far as I can tell 'amq -f' is the official way to tell amd that it should reload maps. --Artem > d) > It doesn't work at all, I only get: > # cd /media/ufs/FreeBSD_Install > /media/ufs/FreeBSD_Install: Too many levels of symbolic links. > > e) > A SIGKILL without load will terminate the process. A SIGKILL while > there is heavy file system load panics the system. > > I'll try a clean buildworld buildkernel and repeat. > > -- > 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? > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >