Simplify the codes that InspIRCd can exit with.

The custom codes that InspIRCd exits with are not very useful and can confuse init systems like systemd which assume that certain
exit codes mean certain things. INSPIRCD_BINARY_EXIT was a workaround
for this in v3 but considering thatsers have to check the logs anyway
so we may as well just use EXIT_SUCCESS and EXIT_FAILURE.

1 files changed, 0 insertions, 46 deletions

diff --git a/make/template/inspircd.1 b/make/template/inspircd.1
index 9ce7c178b..6ba4ee8d0 100644
--- a/make/template/inspircd.1
+++ b/make/template/inspircd.1
@@ -56,52 +56,6 @@ Allow the server to start as root (not recommended).
 .br
 Displays the InspIRCd version and exits.
 
-.SH "EXIT STATUS"
-.TP
-.B "0 (EXIT_STATUS_NOERROR)"
-.br
-The server exited cleanly.
-.TP
-.B "1 (EXIT_STATUS_DIE)"
-.br
-The server exited because the DIE command was executed.
-.TP
-.B "2 (EXIT_STATUS_CONFIG)"
-.br
-The server exited because of a configuration file error.
-.TP
-.B "3 (EXIT_STATUS_LOG)"
-.br
-The server exited because of a log file error.
-.TP
-.B "4 (EXIT_STATUS_FORK)"
-.br
-The server exited because it was unable to fork into the background.
-.TP
-.B "5 (EXIT_STATUS_ARGV)"
-.br
-The server exited because an invalid argument was passed to it on the command line.
-.TP
-.B "6 (EXIT_STATUS_PID)"
-.br
-The server exited because it was unable to write to the PID file.
-.TP
-.B "7 (EXIT_STATUS_SOCKETENGINE)"
-.br
-The server exited because it was unable to initialize the @SOCKETENGINE@ socket engine.
-.TP
-.B "8 (EXIT_STATUS_ROOT)"
-.br
-The server exited because the user tried to start as root without \fI--runasroot\fR.
-.TP
-.B "9 (EXIT_STATUS_MODULE)"
-.br
-The server exited because it was unable to load a module on first run.
-.TP
-.B "10 (EXIT_STATUS_SIGTERM)"
-.br
-The server exited because it received SIGTERM.
-
 .SH "SUPPORT"
 IRC support for InspIRCd can be found at ircs://irc.inspircd.org/inspircd.