From owner-freebsd-current@freebsd.org Fri Apr 22 08:26:00 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9619B170C1 for ; Fri, 22 Apr 2016 08:26:00 +0000 (UTC) (envelope-from dan_partelly@rdsor.ro) Received: from mail.rdsor.ro (mail.rdsor.ro [193.231.238.10]) by mx1.freebsd.org (Postfix) with ESMTP id 8DE2E1AF8; Fri, 22 Apr 2016 08:26:00 +0000 (UTC) (envelope-from dan_partelly@rdsor.ro) Received: from email.rdsor.ro (ftp.rdsor.ro [193.231.238.4]) by mail.rdsor.ro (Postfix) with ESMTP id 106EADC10F; Fri, 22 Apr 2016 11:25:53 +0300 (EEST) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Fri, 22 Apr 2016 11:26:00 +0300 From: dan_partelly To: David Chisnall Cc: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= , freebsd-current Subject: Re: devd limitations -- was [CFT] packaging the base system with pkg(8) In-Reply-To: References: <76093.1461096570@critter.freebsd.dk> <5716AD65.8070007@shrew.net> <5716FA70.4080604@freebsd.org> <571765BB.3050908@quip.cz> <79117ce18bd3332c7df3e55e12a161b4@rdsor.ro> <20160421095706.GA57206@brick> <30F6CCDE-E099-49EF-9A1A-68F147FBF50B@rdsor.ro> <20160421202023.GB33506@brick> <7F12F680-080B-4DB3-81A5-CC5282B78034@rdsor.ro> Message-ID: <65fc57974095a9fc90ceeb8244f0c219@rdsor.ro> X-Sender: dan_partelly@rdsor.ro User-Agent: RoundCube Webmail/0.4-beta X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 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: Fri, 22 Apr 2016 08:26:00 -0000 > Ideally, when the automounter daemon starts, it should > connect to devd via an IPC channel and request notification of the specific > events that it wants I was under the impression that devd.seqpacket.pipe accomplishes this. Am I right in assuming that the issue is that devd forwards ALL events to a client now, and the limitation is that we cannot specify a filter ? Or there is something else more deep and fundamental ? I am planning to use devd for a inhouse tool. >> though hopefully will appearat some point in the 11.x series. There are a lot of daemons IMO which would benefit from a tighter integration with devd, and abolishment of glue scripts or programs between devd and clients is desirable IMO. Fingers crossed.