bind to port 443 + wake from hibernation = exit
Jan 28 22:05:50.644 [notice] Opening OR listener on 184.108.40.206:443 Jan 28 22:05:50.644 [warn] Could not bind to 220.127.116.11:443: +Permission denied Jan 28 22:05:50.645 [warn] Failed to parse/validate config: Failed +to bind one of the listener ports.
Basically if you bind to port 443 directly, and then drop privs, that's fine. When you hup, Tor will (should) correctly decide to leave that port alone since it hasn't changed and it wouldn't be able to bind it again anyway.
But when we hibernate, and then come back, we can't bind it. Currently we die.
Option one, never close it in this case. Not great, since we want to be hibernating, but not awful.
Option two, keep a separate root process around that can jumpstart Tor again. Ugh.
Option three, warn if this configuration is used, so the user can at least know.
How do we auto detect that it's a privileged port? Just "port < 1024"?
[Automatically added by flyspray2trac: Operating System: All]