Date: Sat, 17 Aug 2013 17:08:42 +0200 From: Dominic Fandrey <kamikaze@bsdforen.de> To: Daniel Braniss <danny@cs.huji.ac.il> Cc: Konstantin Belousov <kostikbel@gmail.com>, freebsd-stable@freebsd.org Subject: Re: stopping amd causes a freeze Message-ID: <520F91FA.8030806@bsdforen.de> In-Reply-To: <E1V3Mq8-000FLb-27@kabab.cs.huji.ac.il> References: <51ED0060.2050502@bsdforen.de> <20130722100720.GI5991@kib.kiev.ua> <51F0DA4B.3000809@bsdforen.de> <20130725100037.GM5991@kib.kiev.ua> <51F2AD8C.1000003@bsdforen.de> <51F385CE.1030606@bsdforen.de> <20130728062403.GD4972@kib.kiev.ua> <51F4D57E.4040002@bsdforen.de> <E1V3Mq8-000FLb-27@kabab.cs.huji.ac.il>
next in thread | previous in thread | raw e-mail | index | archive | help
On 28/07/2013 11:00, Daniel Braniss wrote: >> On 28/07/2013 08:24, Konstantin Belousov wrote: >>> On Sat, Jul 27, 2013 at 10:33:18AM +0200, Dominic Fandrey wrote: >>>> On 26/07/2013 19:10, Dominic Fandrey wrote: >>>>> On 25/07/2013 12:00, Konstantin Belousov wrote: >>>>>> On Thu, Jul 25, 2013 at 09:56:59AM +0200, Dominic Fandrey wrote: >>>>>>> On 22/07/2013 12:07, Konstantin Belousov wrote: >>>>>>>> On Mon, Jul 22, 2013 at 11:50:24AM +0200, Dominic Fandrey wrote: >>>>>>>>> ... >>>>>>>>> >>>>>>>>> I run amd through sysutils/automounter, which is a scripting solution >>>>>>>>> that generates an amd.map file based on encountered devices and devd >>>>>>>>> events. The SIGHUP it sends to amd to tell it the map file was updated >>>>>>>>> does not cause problems, only a -SIGKILL- SIGTERM may cause the freeze. >>>>>>>>> >>>>>>>>> Nothing was mounted (by amd) during the last freeze. >>>>>>>>> >>>>>>>>> ... Thank you everyone, after updating to stable/9 r254418 the problem has dissipated. -- 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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?520F91FA.8030806>