Skip to content

return status doesn't indicate failure #1

@mwotton

Description

@mwotton

if the server can't start (for instance, there's already an instance on that port), because it's daemonised, the parent process doesn't report anything in the status. Might it make more sense to start listening first, then daemonise?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions