Skip to content

env(1) forks, but must exec() directly #8361

@julian-klode

Description

@julian-klode

Forwarded from: https://bugs.launchpad.net/ubuntu/+source/rust-coreutils/+bug/2112491

Relevant comment:

This is a really major break in the env program: it doesn't re-execute with the subcommand, instead it forks! So then terminating the env process keeps the subcommand running. This affects all scripts whose shebang uses /usr/bin/env.

Reproduced on commit 2ba3a33, there do not seem to have been more recent commits to env after that.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions