| commit | 9836e2b33a90735f579ff2beb0cd2473661885cb | [log] [tgz] |
|---|---|---|
| author | Andrew Jeffery <andrew@aj.id.au> | Tue Feb 11 12:12:07 2020 +1030 |
| committer | Andrew Jeffery <andrew@aj.id.au> | Tue Feb 25 09:48:08 2020 +1030 |
| tree | 9ba967424948fae30d5763389e22ce5842c5b2b6 | |
| parent | 71e7a24961d038ced6bbea2b635fd2531e1c0b8e [diff] |
conf: Ship default configuration and systemd units Two configurations are supported: 1. A socket-activated, single-port client service arrangement, and 2. A port-templated client service systemd's template-unit constraints prevent us from mapping ports to a daemon configuration for the socket-activated case. To support multiple concurrent console servers we have to revert to a standard daemon arrangement where dropbear binds, listens and accepts its own connections. This brings with it immediate memory overhead of running dropbear before connections are received. As such configuration 2 is opt-in as there are very few systems that require it. Signed-off-by: Andrew Jeffery <andrew@aj.id.au> Change-Id: Ifbcac1b1ca75ab3ff08c73855d7ed2ebabc27c0a
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.