Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • 2
    Possible duplicate of How to understand the output of tracing running an external command in bash? Commented Mar 3, 2016 at 7:11
  • Have you read them, at least the titles? The other post is about running command directly, the post here is about running command in background, and comparing running command directly and in background. Commented Mar 3, 2016 at 7:12
  • Why is the shell executing /bin/sed? Do you have date defined as an alias or shell function? Commented Mar 3, 2016 at 10:44
  • This post is not about the prompt setting as the other post linked, but about how a command is run in background, in bash -c, and directly in bash shell in terms of execve() and clone(). The part of output for my prompt setting and possibly my second part of question might make some people think this post is a duplicate of the other one, while it isn't. Commented Mar 3, 2016 at 16:23
  • Remove the prompt setting part of the tracing output, to make the post concentrate on how a command is run in background. Commented Mar 3, 2016 at 17:35