don't log to syslog when testing

This commit is contained in:
yrutschle committed 2022-03-18 18:02:32 +01:00
1 parent 91d148f66c
commit 1e0578c082
9 files changed
+86 -66

No files matched your search

+6 -8
View File
@@ -23,8 +23,6 @@ Makefile.
* [libcap](http://packages.debian.org/source/unstable/libcap-dev), in package `libcap-dev`. You can compile with or without it using USELIBCAP in the Makefile
* [libev](http://software.schmorp.de/pkg/libev.html), in package `libev-dev`. It is only required to build `sslh-ev`, so you don't need if you only build `sslh-fork` and/or `sslh-select`.
* libbsd, to enable to change the process name (as shown in
`ps`, so each forked process shows what protocol and what
connection it is serving),
@@ -73,8 +71,8 @@ of the Makefile:
Binaries
--------
The Makefile produces three different executables: `sslh-fork`,
`sslh-select` and `sslh-ev`:
The Makefile produces two different executables: `sslh-fork`
and `sslh-select`:
* `sslh-fork` forks a new process for each incoming connection.
It is well-tested and very reliable, but incurs the overhead
@@ -91,10 +89,10 @@ If you are going to use `sslh` on a "medium" setup (a few thousand ssh
connections, and another few thousand ssl connections),
`sslh-select` will be better.
* `sslh-ev` works very much like `sslh-select`, but uses
`libev` as a backend. `libev` provides more portability
and alternative ways to support very large numbers of
connections.
If you have a very large site (tens of thousands of connections),
you'll need a vapourware version that would use libevent or
something like that.
Installation
------------