[PATCH v5 1/3] Introduce -l/--syscall-limit option

Kossi GLOKPOR hotkatz32 at gmail.com
Fri Mar 31 14:30:05 UTC 2023


Hi,
 I was thinking about enabling it automatically. If the user enabled one of
the daemonization options, we use it but if he isn't using one, we set
--daemonize=grandchild and emit a warning telling the user we did so. Do
you think this can do the trick?

Regards,
Kossi

On Fri, Mar 31, 2023, 11:33 Dmitry V. Levin <ldv at strace.io> wrote:

> Hi,
>
> On Fri, Mar 31, 2023 at 12:14:13PM +0530, Sahil Siddiq wrote:
> > On Friday, 31 March 2023 03:17:40 IST Kossi GLOKPOR wrote:
> > > Hi,
> > > What do you think about using the --daemonize options ? For example
> > > with --daemonize=grandchild, the shell will be the parent of the
> > > tracee, and detaching & stopping strace will have no incidence on it.
> > > When we set an auto stop condition, we assume that strace can have to
> > > stop while the tracee is still running, and enabling tracer
> > > daemonization seems like a good way to prevent any issues with the
> > > tracee when strace stops.
> > >
> > > Regards,
> > > Kossi
> >
> > Thank you for the suggestion. I have tested this out and it gives the
> results
> > that I was looking for. We could let "--syscall-limit" be enabled only
> when using
> > it with the -D or -p options and disable it otherwise.
>
> To be honest, although using --syscall-limit along with --daemonize makes
> perfect sense, I'm not sure it is necessary to make this combination, or
> combination of --syscall-limit with -p, mandatory.
>
>
> --
> ldv
> --
> Strace-devel mailing list
> Strace-devel at lists.strace.io
> https://lists.strace.io/mailman/listinfo/strace-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.strace.io/pipermail/strace-devel/attachments/20230331/2ac9e526/attachment.htm>


More information about the Strace-devel mailing list