[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: dtrace
From: |
Eli Zaretskii |
Subject: |
Re: dtrace |
Date: |
Thu, 16 Jan 2025 13:22:11 +0200 |
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: eller.helmut@gmail.com, emacs-devel@gnu.org, pipcet@protonmail.com
> Date: Thu, 16 Jan 2025 11:12:04 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Yes, I did, briefly, or something using a ffi. But I think both have the
> >> same problem that consuming DTrace requires root privileges, which I
> >> don't want to grant to Emacs.
> >
> > Then how does the Python front-end do this without needing root
> > privileges? If that's because it uses the libdtrace library, then so
> > could your module. Or what am I missing?
>
> Python faces the same problem. If it's just some .py using libdtrace,
> one would have to run that with sudo. If it's used in a Jupyter
> notebook, one would have to arrange for a root login, which I think is
> supported, judging from what Gemini told me, but that's still an open
> question for me.
Then dtrace will always need root privileges.
If we don't want to grant root privileges to Emacs, how about doing
granting them to a separate sub-process, also running Emacs, perhaps
via the async package?
Re: dtrace, Gerd Möllmann, 2025/01/16
- Re: dtrace, Helmut Eller, 2025/01/16
- Re: dtrace, Gerd Möllmann, 2025/01/16
- Re: dtrace, Eli Zaretskii, 2025/01/16
- Re: dtrace, Gerd Möllmann, 2025/01/16
- Re: dtrace, Eli Zaretskii, 2025/01/16
- Re: dtrace, Gerd Möllmann, 2025/01/16
- Re: dtrace,
Eli Zaretskii <=
- Re: dtrace, Gerd Möllmann, 2025/01/16
- Re: dtrace, Eli Zaretskii, 2025/01/16
- Re: dtrace, Gerd Möllmann, 2025/01/16
- Re: dtrace, Björn Bidar, 2025/01/18
- Message not available
- Re: dtrace, Gerd Möllmann, 2025/01/18
- Re: dtrace, Björn Bidar, 2025/01/20
- Message not available
- Re: dtrace, Gerd Möllmann, 2025/01/20
Re: dtrace, Richard Stallman, 2025/01/18
dtrace, Jordan Ellis Coppard, 2025/01/17