Open JasonGao180 opened 9 years ago
I reproduce it again, the following is the log, it only happend when it restore the /etc/hosts file.
[DEBUG] - RemoteHostsManager - Starting timer for remote hosts files. Interval: 60 minutes
[DEBUG] - HostsMainController - Saving selected hosts file
[DEBUG] - AbstractHostsController - Saving hosts file "Default" to "/etc/hosts"
[DEBUG] - AbstractHostsController - System hosts file is not writeable: "/etc/hosts"
[DEBUG] - PrivilegedActions - Making /etc/hosts writable for user jasongao
[DEBUG] - Util - Flushing Directory Service Cache
[DEBUG] - HostsMainController - External application has changed the hosts file, restoring file
[DEBUG] - AbstractHostsController - Restoring hosts file "Default" to "/etc/hosts"
[DEBUG] - Util - Flushing Directory Service Cache
I encountered the same issue, as described in this bug: https://github.com/2ndalpha/gasmask/issues/15, I have a combined hosts file activated which is combined with a local and remote file.
Happens here too, after updating the remote file:
me@mybox ~> more /etc/hosts Remote/someonewhocares.org 0.0.0.0 Local/antiads
Repairable by setting the output (checkmark) to another file and then back again.
I'm encountering the same issue. Is this how Gas Mask is supposed to work or a bug?
Note that things appear to work fine when the hosts file is a list of of my list names; however, when I ping 'localhost' it points to somewhere else. 'Refreshing' the hosts file through Gas Mask manually fixes the hosts file and localhost correctly points to 127.0.0.1.
I have the same problem here. It happens whenever Gas Mask changes the hosts file without user interaction. Namely when external hosts files are being updated or when the hosts file has been modified by some other application and Gas Mask restores the file.
I helped myself for now by running this script so I am at least informed whenever the hosts file is damaged.
!/bin/bash
hostsfile="/etc/hosts" query="ivwbox" if ! grep -q "$query" "$hostsfile"; then /usr/local/bin/terminal-notifier -message "hosts-file is not OK! Check Gas Mask!" -title "Gas Mask problem!" fi
which is run every time the hosts file changes and every 5 minutes by a LaunchAgent. The script needs "terminal-notifier" from brew.
Same issue here. (When using a combined hosts file) each time the remote hosts file is updated automatically in /etc, the new hosts file just reads:
Remote/someonewhocares.org Local/Original File
I can confirm that while the remote file in the Gas Mask folder (someonewhocares.org.hst) shows the latest update from someonewhocares.org/hosts/hosts, the one in /etc (above) has no apparent effect in blocking out sites, after some tests. Only by activating another hosts file in Gas Mask and then switching back again does the hosts file in /etc finally update properly (as someone has mentioned earlier).
Does anyone NOT have this issue with the current version (0.8.5) and external hosts files? I'm wondering if it can be fixed with a complete reinstall or something like that.
Try unchecking the "Override external modifications" checkbox. That resolved the problem for me.
@fmera +1 for your workaround but still would be good to fix this bug
@PikachuEXE I've since moved on to SwitchHosts! and find it quite ok, no issues at all. You can check it out at either https://oldj.github.io/SwitchHosts/ or https://github.com/oldj/SwitchHosts/releases
Thanks I will try it later
I used the Combined Hosts functionality, but sometimes it output the following pictures.