From owner-freebsd-current@freebsd.org Tue Aug 9 06:58:19 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 11F59BB3647 for ; Tue, 9 Aug 2016 06:58:19 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CAC1E1A41 for ; Tue, 9 Aug 2016 06:58:18 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1bX0zQ-001jhM-V5>; Tue, 09 Aug 2016 08:58:16 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=freyja.zeit4.iv.bundesimmobilien.de) by inpost2.zedat.fu-berlin.de (Exim 4.85) for freebsd-current@freebsd.org with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1bX0zQ-001TSj-Lu>; Tue, 09 Aug 2016 08:58:16 +0200 Date: Tue, 9 Aug 2016 08:58:09 +0200 From: "O. Hartmann" To: freebsd-current Subject: r303869: dmesg: sysctl kern.msgbuf: Operation not permitted Message-ID: <20160809085809.621667ef@freyja.zeit4.iv.bundesimmobilien.de> Organization: FU Berlin X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.29; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 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: Tue, 09 Aug 2016 06:58:19 -0000 On recent 12.0-CURRENT FreeBSD 12.0-CURRENT #36 r303869, I see apart from serious performance issues and stuck ZFS rsync synchronisations this on the console, when typing "dmesg" in theshell from a user which is member of group "wheel": dmesg: sysctl kern.msgbuf: Operation not permitted Is this a feature or a bug? Trying to sync a poudriere built ports collection to a automounted ZFS filesystem on a remote server, the rsync gets stuck very quickly, stopping and never resume. I did the last synchronisation on July, 20th with CURRENT without problems the very same way. Kind regards, Oliver