Open
Description
> rathole -V
rathole 0.4.7
Describe the bug
This occurs when I try to start rathole with systemd, It failed to start unexpectedly and has no valid debug information about it:
> journalctl -f -u rathole.service
Mar 16 14:34:09 host systemd[1]: Stopped rathole Daemon.
Mar 16 14:34:09 host systemd[1]: rathole.service: Consumed 12ms CPU time, received 960B IP traffic, sent 9.7K IP traffic.
Mar 16 14:34:09 host systemd[1]: Started rathole Daemon.
Mar 16 14:34:09 host rathole[99122]: Mar 16 14:34:09.370 INFO handle{service=example}: rathole::client: Starting <omitted>
Mar 16 14:34:09 host systemd[1]: rathole.service: Deactivated successfully.
To Reproduce
Steps to reproduce the behavior:
- Create config dir
config
, with permission 751 owned by user B. - Start
rathole
with config file which with full permission and owned by user A, in config dir.
Run rathole by user A:
> RUST_LOG=trace rathole --client config/test.toml
...
Mar 16 14:41:59.500 TRACE config_watcher{path="config/test.toml"}: mio::poll: registering event source with poller: token=Token(0), interests=READABLE
Mar 16 14:41:59.501 INFO handle{service=ssh_tcp}: rathole::client: Starting <omitted>
Mar 16 14:41:59.501 TRACE mio::poll: deregistering event source from poller
It exits directly, without reporting any available information related to permission lacking.
Bcz I found this, seems rathole needs read permission of the parent directory?
Line 165 in 9479b9a
Is there a way to implement hot-reload without this permission? Or at least report some error messages about the permission lacking...
Environment:
> uname -srm
Linux 6.2.5 x86_64