* [QUESTION] About the behavior when MAXACTION is exceeded
@ 2019-01-22 7:48 Zexuan Luo
2019-01-29 0:41 ` Frank Ch. Eigler
0 siblings, 1 reply; 4+ messages in thread
From: Zexuan Luo @ 2019-01-22 7:48 UTC (permalink / raw)
To: systemtap
Hi, guys.
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?
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [QUESTION] About the behavior when MAXACTION is exceeded
2019-01-22 7:48 [QUESTION] About the behavior when MAXACTION is exceeded Zexuan Luo
@ 2019-01-29 0:41 ` Frank Ch. Eigler
2019-01-29 3:20 ` Zexuan Luo
0 siblings, 1 reply; 4+ messages in thread
From: Frank Ch. Eigler @ 2019-01-29 0:41 UTC (permalink / raw)
To: Zexuan Luo; +Cc: systemtap
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [QUESTION] About the behavior when MAXACTION is exceeded
2019-01-29 0:41 ` Frank Ch. Eigler
@ 2019-01-29 3:20 ` Zexuan Luo
2019-01-29 3:49 ` Frank Ch. Eigler
0 siblings, 1 reply; 4+ messages in thread
From: Zexuan Luo @ 2019-01-29 3:20 UTC (permalink / raw)
To: Frank Ch. Eigler; +Cc: systemtap
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [QUESTION] About the behavior when MAXACTION is exceeded
2019-01-29 3:20 ` Zexuan Luo
@ 2019-01-29 3:49 ` Frank Ch. Eigler
0 siblings, 0 replies; 4+ messages in thread
From: Frank Ch. Eigler @ 2019-01-29 3:49 UTC (permalink / raw)
To: Zexuan Luo; +Cc: systemtap
Hi -
> 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?
Setting -DMAXERRORS=NNN is one way of making this error non-fatal.
We don't have a flag for turning this particular error into a warning,
but would consider merging such a patch.
- FChE
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2019-01-29 3:49 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-22 7:48 [QUESTION] About the behavior when MAXACTION is exceeded Zexuan Luo
2019-01-29 0:41 ` Frank Ch. Eigler
2019-01-29 3:20 ` Zexuan Luo
2019-01-29 3:49 ` Frank Ch. Eigler
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).