From owner-freebsd-dtrace@FreeBSD.ORG Wed Jun 4 10:35:16 2014 Return-Path: Delivered-To: freebsd-dtrace@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 ESMTPS id 10060302; Wed, 4 Jun 2014 10:35:16 +0000 (UTC) Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 68F7520A6; Wed, 4 Jun 2014 10:35:15 +0000 (UTC) Received: by mail-ob0-f170.google.com with SMTP id uy5so7407713obc.15 for ; Wed, 04 Jun 2014 03:35:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2tT2Pn8M2+u7Z+5B7vnxbj+h9MeaFwhu1Px2a//J64A=; b=qk8XJyGaG5KhFAOdbQRHHwUvbx/I+tnTioZ2ftdxoHxuBR1nJOCWg6Hc8TnWsOYJbr ezFazKvxfQUZbDTCXleGr326UJge4iSELGASUI+TzUm+a5vLmOJ6vgYnqlI0hAOAhnTM L8f1Kq8w6p/rV1jhBAt7mS78+sSGIoLz30lSmPAKEeI7L0+RXwmbb+rkMQ/so3NH/q3+ tjWxngUCI9pLR6QXKXLC8x0kSy07CnnnpBs1tOjzX6Q1bwjjrjwtSoqhJQkhGFZpVSex 640Nau2vZXtq6LqkuI5ATnhLoW401x+poGqjp95a7elNtmUla5YUTUZbBeA0Prks16KE 2nIw== MIME-Version: 1.0 X-Received: by 10.182.34.167 with SMTP id a7mr4256938obj.3.1401878114496; Wed, 04 Jun 2014 03:35:14 -0700 (PDT) Received: by 10.76.18.45 with HTTP; Wed, 4 Jun 2014 03:35:14 -0700 (PDT) In-Reply-To: References: Date: Wed, 4 Jun 2014 11:35:14 +0100 Message-ID: Subject: Re: Postgresql provider no longer working From: "Sevan / Venture37" To: Mark Johnston Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-dtrace@freebsd.org" X-BeenThere: freebsd-dtrace@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "A discussion list for developers working on DTrace in FreeBSD." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jun 2014 10:35:16 -0000 On 4 June 2014 02:45, Mark Johnston wrote: > Hi, > > I can't reproduce this using postgres 9.3.4 on r267033 (current). As > usual, it was necessary to first kldload dtraceall and make sure > postgres could access /dev/dtrace/helper (in my case I've added the > pgsql user to the wheel group). It's also necessary to build with > dtraceall loaded (otherwise dtrace -G will fail I think). With that, > the probes show up as expected. > > Do other ports create probes successfully? lang/php5 has a DTrace > option and manages to create probes when I run it. If it doesn't in > your environment, could you try running it with the > DTRACE_DOF_INIT_DEBUG environment variable set to "1" and pass along > the output? > > Thanks, > -Mark Hi Mark, As previous, adjusting the permissions on /dev/dtrace/helper resolved the issue. What threw me was that I did try PHP & netatalk before posting & the probes for those two did appear. Revisiting those again now I see that they have a master process which runs as root hence not being locked out of access to /dev/dtrace/helper. Moving forward, what's your opinion on the adition of a new system group called dtrace, & the devfs rules own dtrace/helper root:dtrace perm dtrace/helper 0660 Postgresql can be made a member of this group if it's installed with dtrace support & things work from the start. Happy to raise the patch, just running it past you as I'm unsure what ideas there are for delegating access in the future. Sorry about the false alarm. Sevan / Venture37