> On 18 Oct. 2016, at 13:25, Jesse V <kernelc...@torproject.org> wrote:
> 
> On 10/17/2016 12:34 PM, Hoshpak wrote:
>>> # chattr +i /etc/resolv.conf
>>> 
>>> Exact it works fine :)
>> 
>> Please only do this if your are sure your server is not running in a
>> Virtuozzo/OpenVZ container environment. On Virtuozzo, the startup
>> procedure includes scripts that rewrite resolv.conf and fail if they
>> can't write to it. In these cases you could be left with an unbootable
>> container and have to raise a support ticket with your ISP to make them
>> "fix" the issue by removing the immutable bit and starting the container
>> again.
> 
> Thank you very much for that tip. Cronjob is probably the way to go then.

Configuring tor with a separate ServerDNSResolvConfFile may be more
reliable, and would avoid race conditions.

Of course, that doesn't change the resolver for the rest of your system.

Tim

> 
> -- 
> Jesse
> 
> _______________________________________________
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

T

--
Tim Wilson-Brown (teor)

teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
------------------------------------------------------------------------------







_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Reply via email to