Find and classify all the exit codes returned by etcdserver

描述

贡献者指南

技术栈

go

领域

backenddatabase

议题类型

documentation

难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。

3

预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。

1-3 hours

活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。

fresh

清晰度议题是否清楚说明期望改动、验收标准和下一步。

clear

前置要求

Go programmingbasic understanding of etcd architecture

新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。

80

研究方向

Start by searching the etcd codebase for all calls to os.Exit in the etcdserver package. Focus on the server/ directory, particularly files like server/etcdserver/server.go, server/etcdserver/bootstrap.go, and server/etcdserver/errors.go. Look for exit codes in the range 0-255 and note the context. The issue mentions a specific report where exit code 1 is returned; begin by tracing that path. After collection, compile a table mapping each exit code to its source location and reason. Consider also checking the main.go files in cmd/etcd and any wrapper scripts. The issue expects a PR to docs, so the final output should be a Markdown table ready for inclusion in the documentation.