Hi,
When starting vigil directly in a bash shell from e.g. a SSH session I get the following error:
[root@pop-rocky-4gb-fsn1-1 vigil]# vigil -c ./vigil.cfg
thread 'main' panicked at 'cannot substitute environment variables: Error("variable value '() { ( alias;\n eval ${which_declare} ) | /usr/bin/which --tty-only --read-alias --read-functions --show-tilde --show-dot $@\n}' contains forbidden character '$'")', /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/vigil-server-1.26.3/src/config/reader.rs:32:48
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Aborted (core dumped)
OS is Rocky Linux 9
The same machine can run vigil via systemd.
I think that vigil looks into more environment variables than it should and finds something it does not like. I think it would be better if vigil just ignored what environment variables it has nothing to do with contains.
I have no issues starting vigil directly this way on Debian.
Why start vigil like this? For debugging and trying stuff.
Best regards,
Emil Kristensen
Hi,
When starting vigil directly in a bash shell from e.g. a SSH session I get the following error:
OS is Rocky Linux 9
The same machine can run vigil via systemd.
I think that vigil looks into more environment variables than it should and finds something it does not like. I think it would be better if vigil just ignored what environment variables it has nothing to do with contains.
I have no issues starting vigil directly this way on Debian.
Why start vigil like this? For debugging and trying stuff.
Best regards,
Emil Kristensen