cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Tweak DESCR to make it a bit clearer what the -net flavour of comms/conserver

Browse Source 
is for. (It's only needed when you have conserver(8) and console(1) on different
machines, or when you have conserver(8) on multiple machines clustered behind a
single front-end).
This commit is contained in:
sthen 2019-02-26 11:54:57 +00:00
parent da38c6870d
commit aa26be6cc0
2 changed files with 19 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
comms/conserver/Makefile
View File

@ -1,9 +1,9 @@
# $OpenBSD: Makefile,v 1.65 2019/02/25 19:53:16 sthen Exp $ # $OpenBSD: Makefile,v 1.66 2019/02/26 11:54:57 sthen Exp $
COMMENT= manage remote serial consoles via TCP/IP COMMENT= manage remote serial consoles via TCP/IP
V= 8.2.2 V= 8.2.2
REVISION= 3 REVISION= 4
DISTNAME= conserver-$V DISTNAME= conserver-$V
CATEGORIES= comms CATEGORIES= comms

30
comms/conserver/pkg/DESCR
View File

@ -1,19 +1,23 @@
This program provides a convenient way to manage many remote serial This program provides a convenient way to manage remote consoles.
consoles for machines. A server (conserver(1)) runs on each server
machine and it connects to the specified serial port. It can log,
provide shared access to remote consoles, etc. If there are multiple
machines running conserver(1), a master conserver(1) can be run to
connect to all the slave servers, providing a single point of access
to the entire cluster.
This is very handy for remote unattended OpenBSD servers. It can The conserver(8) daemon maintains persistent connections to consoles,
send serial break signals (if the driver supports it, cy(4) does not!) either to a local serial port, via a network connection to a terminal
which is useful for breaking into DDB on hung machines. server, via a UNIX domain socket, by running a command, or (with the
"ipmi" flavor) via IPMI serial-over-lan. It can also write logfiles,
and restrict access based on user/group (read, read/write, none).
User access is done with console(1) - this allows standard terminal
commands including sending BREAK signals, and can replay output from
before you connected.
By default conserver<>console connections are done via a unix-domain
socket, but in a larger installation, the "net" flavor can be used
to do this over a TCP+TLS connection to another host - in that case,
conserver(8) instances on multiple servers can be clustered.
Flavors: Flavors:
net - use network sockets rather than unix domain sockets net - use network sockets for conserver<>console and to allow
(as was previously the default). This is mainly useful when conserver<>conserver connections.
the conserver server is on a separate machine to the client.
ipmi - build with internal support for IPMI serial-over-lan ipmi - build with internal support for IPMI serial-over-lan