server:running_the_server:signals
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
server:running_the_server:signals [2018/02/28 08:34] – created karl | server:running_the_server:signals [2025/04/18 13:08] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 12: | Line 12: | ||
==== 1 Hang Up [SIG]HUP ==== | ==== 1 Hang Up [SIG]HUP ==== | ||
- | This signal forces the crossfire server unfortunately not | + | This signal forces the crossfire |
- | to reload the configuration files, but should write a new log file, | + | to reload the configuration files, |
+ | but reopens the log file in append mode, | ||
if the logging output is not send to stderr ( of some terminal ) . | if the logging output is not send to stderr ( of some terminal ) . | ||
Syntax : '' | Syntax : '' | ||
+ | |||
+ | The whole path to the logfile is defined in // | ||
+ | * Windows : #define LOGFILE " | ||
+ | * #else : #define LOGFILE "/ | ||
+ | The // | ||
+ | The server may choke at start up, if the directory //var// or // / | ||
+ | |||
+ | The source code file // | ||
+ | in append mode inside the function //void LOG (LogLevel logLevel, const char *format, ...)// : | ||
+ | <code c>if ((logfile = fopen(settings.logfilename, | ||
+ | " | ||
+ | > | ||
+ | > created if it does not exist. | ||
+ | > end of the file. | ||
+ | From manual page [[http:// | ||
+ | |||
+ | FIXME It makes no sense to append to a logfile; I have a 55 MB logfile and would like the idea, to completely overwrite it, without the need to shut down the server entirely. \\ | ||
+ | In the case of a long-time running server like the [[: | ||
==== 2 Interrupt [SIG}INT ==== | ==== 2 Interrupt [SIG}INT ==== |
server/running_the_server/signals.1519828465.txt.gz · Last modified: (external edit)