| #
9a8f30ec |
| 01-May-2023 |
Andrew Jeffery <andrew@aj.id.au> |
obmc-console: Introduce console-id, deprecate socket-id
The name `socket-id` exposes too much detail about the implementation.
Really the tag identifies the console, so name it as such.
Maintain ba
obmc-console: Introduce console-id, deprecate socket-id
The name `socket-id` exposes too much detail about the implementation.
Really the tag identifies the console, so name it as such.
Maintain backwards compatibility until we've converted all the in-tree
OpenBMC users over to `console-id`. Once that's done we can drop support
for `socket-id`.
Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
Change-Id: I5aa2ba84835d64901e459b42bfe7be59043466c7
show more ...
|
| #
9836e2b3 |
| 10-Feb-2020 |
Andrew Jeffery <andrew@aj.id.au> |
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 clien
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
show more ...
|