James Short
James Short
Dup of #501
Yeah we need some logs from running `etserver --logtostdout -v 9 --cfgfile=/etc/et.cfg` directly to get systemd out of the equation. @Overload119 you need to remove the `--daemon` option from your...
@RonanMacF Can you run with the `--terminal-path` option to explicitly give the path to the `etterminal` binary you want to use on the server (and confirm your user can execute...
@Beraliv ipv6 host addresses are now supported so please try with the latest code (just `et` the client executable, needs to be updated)!
The issue can be resolved with the `--macserver` option (or `--terminal-path` which recently replaced the `--prefix` option) give a fully qualified path to the `etterminal` binary on the server.
Quick follow up if people find this: in older releases of the `et` client binary, the option was `--prefix` and requires a full path to the `etterminal` binary (`--prefix=/usr/local/bin/etterminal`) but...
@joexue Can you explain what the issue is: errors, logs etc?
@joexue can you confirm that `export PATH="$PWD"/out/bin:/usr/sbin:/usr/bin:/sbin:/bin` is setting your path correctly and that `$PWD/out/bin` has cmake of the correct version (higher than 3.15)?
> do you mean the build will set the path or I have to set path myself? No, the script does exactly that, but I was just implying that you...
I haven't ever used that script and it hasn't been updated in 3 years so I'm going to assume it is in need of updates (or we can just delete...