| commit | 93fd8a39d8d20cdf965490f594a2d6f6d90f506c | [log] [tgz] |
|---|---|---|
| author | Lei YU <mine260309@gmail.com> | Wed Mar 30 10:15:25 2022 +0800 |
| committer | Lei YU <yulei.sh@bytedance.com> | Thu Mar 31 20:41:05 2022 +0800 |
| tree | 3e5c1e0131b7939a565f73a80fa9bae2a7772250 | |
| parent | 467d3010344d974f3051162d29f13f49c0eb8ea3 [diff] |
log_trim: Rotate log instead of truncate
When the log buffer file's size exceeds, the log_trim() was using
moving the file's content and truncate it to a specific size.
This results in a behavior that the log file is always changing its
whole content when log_trim() is called.
It could be better to change the behavior like logrotate, that move the
original file to a new one, and create a new log file for log buffer.
This way it makes sure that the log file is always appended with new
content and thus is friendly to rsyslog.
Tested: Verify rsyslog could use imfile module to handle this log file
normally. Before this change, rsyslog will handle it incorrectly
when log_trim() is called.
Signed-off-by: Lei YU <mine260309@gmail.com>
Change-Id: I7647b8e21747ea98f68e4bc7c5bbf1339354bd75
Note: In addition to a toolchain and autoconf tools, this requires autotools-archive to be installed.
To build this project, run the following shell commands:
./bootstrap.sh
./configure ${CONFIGURE_FLAGS}
make
To fully clean the repository, run:
./bootstrap.sh clean
Running the server requires a serial port (e.g. /dev/ttyS0):
touch obmc-console.conf ./obmc-console-server --config obmc-console.conf ttyS0
To connect to the server, simply run the client:
./obmc-console-client
To disconnect the client, use the standard ~. combination.
This shows how the host UART connection is abstracted within the BMC as a Unix domain socket.
+--------------------------------------------------------------------------------------------+
| |
| obmc-console-client unix domain socket obmc-console-server |
| |
| +---------------------+ +------------------------+ |
| | client.2200.conf | +---------------------+ | server.ttyVUART0.conf | |
+---+--+ +---------------------+ | | +------------------------+ +--------+-------+
Network | 2200 +--> +->+ @obmc-console.host0 +<-+ <--+ /dev/ttyVUART0 | UARTs
+---+--+ | socket-id = "host0" | | | | socket-id = "host0" | +--------+-------+
| | | +---------------------+ | | |
| +---------------------+ +------------------------+ |
| |
| |
| |
+--------------------------------------------------------------------------------------------+
This supports multiple independent consoles. The socket-id is a unique portion for the unix domain socket created by the obmc-console-server instance. The server needs to know this because it needs to know what to name the pipe; the client needs to know it as it needs to form the abstract socket name to which to connect.