mirror of
https://github.com/sshuttle/sshuttle.git
synced 2025-05-06 09:05:16 +02:00
560c6b4ce8
If an exception occurs in hostwatch, sshuttle exits. Problems read/writing the ~/.sshuttle.hosts cache file on the remote machine would therefore cause sshuttle to exit. With this patch, we simply continue running without writing/reading the cache file in the remote home directory. This serves as an alternate fix for pull request #322 which proposed storing the cache file elsewhere. A list of included changes: - If we can't read or write the host cache file on the server, continue running. Hosts can be collected through the netstat, /etc/hosts, etc and the information can be reconstructed each run if a cache file isn't available to read. We write a log() message when this occurs. - Add additional types of exceptions to handle. - Continue even if we cannot read /etc/hosts on the server. - Update man page to mention the cache file on the remote host. - Indicate that messages are related to remote host instead of local host. - Add comments and descriptions to the code. |
||
|---|---|---|
| .. | ||
| changes.rst | ||
| chromeos.rst | ||
| conf.py | ||
| how-it-works.rst | ||
| index.rst | ||
| installation.rst | ||
| make.bat | ||
| Makefile | ||
| manpage.rst | ||
| openwrt.rst | ||
| overview.rst | ||
| platform.rst | ||
| requirements.rst | ||
| support.rst | ||
| tproxy.rst | ||
| trivia.rst | ||
| usage.rst | ||
| windows.rst | ||