Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cli/exit: new package to replace direct uses of os.Exit #9659

Closed
jseldess opened this issue Jan 29, 2021 · 1 comment
Closed

cli/exit: new package to replace direct uses of os.Exit #9659

jseldess opened this issue Jan 29, 2021 · 1 comment
Assignees
Milestone

Comments

@jseldess
Copy link
Contributor

jseldess commented Jan 29, 2021

Jesse Seldess commented:

Backported from 21.1 to 20.2.

From release notes:

- Some specific situations now have dedicated exit status codes. The following codes are defined:

    Code | Description
    -----|------------
    0 | Process terminated without error.
    1 | An unspecified error was encountered. Explanation should be present in the stderr or logging output.
    2 | Go runtime error, or uncaught panic. Likely a bug in CockroachDB. Explanation may be present in logging output.
    3 | Server process interrupted gracefully with Ctrl+C / SIGINT.
    4 | Command-line flag error.
    5 | A logging operation to the process' stderr stream failed (e.g. stderr has been closed). Some details may be present in the file output, if enabled.
    6 | A logging operation to file has failed (e.g. log disk full, no inodes, permission issue, etc). Some details may be present in the stderr stream.
    7 | Server detected an internal error and triggered an emergency shutdown.
    8 | Logging failed while processing an emergency shutdown.
    [#56574][#56574]

Jira Issue: DOC-958

@jseldess jseldess added this to the 20.2.x milestone Jan 29, 2021
@jseldess jseldess modified the milestones: 20.2.x, 20.2 May 25, 2021
@rmloveland
Copy link
Contributor

We also have 10 - Disk Full via cockroachdb/cockroach#66893 which I am mentioning in an upcoming PR to fix #11156

This implies the existence of a 9 - Foo but IDK what it is

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants