This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [QUESTION] About the behavior when MAXACTION is exceeded
- From: Zexuan Luo <spacewanderlzx at gmail dot com>
- To: "Frank Ch. Eigler" <fche at redhat dot com>
- Cc: systemtap at sourceware dot org
- Date: Tue, 29 Jan 2019 11:20:07 +0800
- Subject: Re: [QUESTION] About the behavior when MAXACTION is exceeded
- References: <CAADJU11NvALaz+G1t96w_47PiqxLfuUT_T-pMTG12Y=1yhy2oQ@mail.gmail.com> <87tvhs5m7q.fsf@redhat.com>
Thank you for the reply.
However, is it acceptable to optionally consider 'MAXACTION exceeded'
as a recoverable error, and avoid aborting the script? Is there any
side-effect to do so?
Frank Ch. Eigler <fche@redhat.com> 于2019年1月29日周二 上午8:41写道：
>
> Zexuan Luo <spacewanderlzx@gmail.com> writes:
>
> > When MAXACTION is exceeded, the systemtap will exit. But as MAXACTION
> > is used to prevent a probe from running too much time, why not just
> > aborting the current probe instead of quitting the whole session?
>
> Aborting a probe running overtime is an error. Aborting a script when
> an error occurs is a separate policy and is configurable with
> -DMAXERRORS=NNN or --suppress-handler-errors.
>
> - FChE