[DTrace-devel] [PATCH 3/3] NEWS: mention the dtprobed daemon

[Kris Van Hees]

On Tue, Nov 01, 2022 at 09:30:11PM +0000, Nick Alcock via DTrace-devel wrote:
> Signed-off-by: Nick Alcock <nick.alcock at oracle.com>

Reviewed-by: Kris Van Hees <kris.van.hees at oracle.com>

> ---
>  NEWS | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/NEWS b/NEWS
> index 62040510805c..de51d180f8a0 100644
> --- a/NEWS
> +++ b/NEWS
> @@ -33,6 +33,16 @@ New features:
>     explicitly (by pid) in the probe script.  Argument mapping and wildcard
>     probe specifications are not supported yet.
>  
> +Upgrading:
> +
> + - The USDT implementation depends on an always-running daemon (dtprobed):
> +   the corresponding systemd dtprobed.service is be automatically started in

"is be" -> "is"

(applied in my copy)

> +   relatively early boot in non-rescue scenarios, but when DTrace is first
> +   installed, or if it is upgraded from a version before the daemon existed
> +   (before 2.0.0-1.11), any probes in programs that were already running
> +   before that point will not appear in DTrace's list of available probes
> +   until such programs are restarted.
> +
>  Bugfixes:
>  
>   - Arguments of sdt-provider probes are now correctly populated using the
> -- 
> 2.38.0.266.g481848f278
> 
> 
> _______________________________________________
> DTrace-devel mailing list
> DTrace-devel at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/dtrace-devel