Arch Linux User Repository

Had already done so, thank you.

@taba will fix the issue with the man page asap. About the ev service, I would rather not add it as it is not yet present upstream. But you can always create yours, see the one in the official package link.

Could you create a sslh-ev@.service?

@gilcu3

drwxr-xr-x 1 root root   18 მაი  6 17:41 sslh.8.gz

Also, thanks!

@taba thanks for the notice, should be fixed now. I did some changes to adapt to upstream behavior better. Now config files are in /etc/sslh/ and you can start any of them (for example default.cfg) by systemctl start sslh@default (uses sslh-fork) or sslh-select@default.

sed: can't read scripts/systemd.sslh.service: No such file or directory

@Nebulosa added changes, should be good now, thanks for pointing things out

You right, I didn't catch that.

So we need make override systemd file In case using -select and -ev and remove making a link from PKGBUILD.

Like that:

In PKGBUILD:

prepare() {
  cd ${pkgname%-git}
  sed -i 's|ExecStart=/usr/sbin/sslh --foreground $DAEMON_OPTS|ExecStart=/usr/bin/sslh-fork --foreground --config=/etc/sslh.cfg|;/EnvironmentFile/d' scripts/systemd.sslh.service
  sed '29 s|443|7443|;30 s|443|8443|;s|thelonious|0.0.0.0|;/user:/d;/pidfile:/d;s|^\(# example.cfg\)|\1 in /usr/share/doc/'${pkgname%-git}' folder|' < basic.cfg > sslh.cfg
}

In install file:

post_install() {
    echo "/etc/sslh.cfg editing is required!"
    echo "Details: https://github.com/yrutschle/sslh/blob/master/doc/config.md"
    echo "Don't forget execute 'systemctl daemon-reload' and 'systemctl restart sslh.socket' after editing."
    echo "/usr/bin/sslh-fork is using by default."
    echo "If you want using sslh-select or sslh-ev you should make systemd override file for you own, e.g."
    echo "/etc/systemd/system/sslh.service.d/exec.conf"
    echo "[Service]"
    echo "ExecStart=/usr/bin/sslh-select --foreground --config=/etc/sslh.cfg"
}

Yes, I get that, but modifying a symlink doesn't seem like the right choice, seems better to have several systemd services. The symlink would be overwritten with every update :|

As I wrote before, in item #5 - symlink to required executable file. Sslh.service always start /usr/bin/sslh - so you need only one .service file. I think that, at first, you decide which type of executable you need, linked it, and after configure sslh.cfg. You use only one executable and config.

It's like Apache (fork process for each client) and Nginx (one process for all clients), as I understood, so, no need launch all of them simultaneously .