Skip to content

React to SIGTERM exit code change #6526

Closed

Description

@Tratcher

dotnet/coreclr#21300 (comment)

CoreClr is changing the default behavior for SIGTERM exit codes from zero to non-zero. WebHost and GenericHost both block the ProcessExit event while attempting to shut down.

Proposal:
If the host does shut down gracefully then set the exit code to zero.

Activity

  1. tmds commented on Feb 21, 2019

    @tmds
    Member

    This change is in coreclr for 3.0. So maybe this should be 3.0 milestone?

  2. added a commit that references this issue on Mar 7, 2019
  3. self-assigned this
    on Mar 7, 2019
  4. added
    bugThis issue describes a behavior which is not expected - a bug.
    on Mar 7, 2019
  5. Tratcher commented on Mar 7, 2019

    @Tratcher
    MemberAuthor

    Note for generic host: We're going to have to port some of the Microsoft.AspNetCore.Server.IntegrationTesting infrastructure to Extensions to enable proper functional tests.

  6. added a commit that references this issue on Mar 19, 2019
  7. added this to the 3.0.0-preview4 milestone on Mar 20, 2019
  8. ghost locked as resolved and limited conversation to collaborators on Dec 3, 2019
  9. added
    area-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions
    and removed on Aug 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

DoneThis issue has been fixedarea-hostingIncludes Hostingarea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsbugThis issue describes a behavior which is not expected - a bug.

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions