0.2.1.27 rebinding or-port on HUP?

[Sebastian Lechte <seb@xxxxxxxxxxxxxxxx>]

Hi list,


I've upgraded my bridge relay from 0.2.1.26 to 0.2.1.27 yesterday. While
rotating logs a HUP gets issued. The log shows:

Dec 08 03:10:06.854 [warn] Could not bind to 0.0.0.0:443: Permission denied
Dec 08 03:10:06.857 [warn] Failed to parse/validate config: Failed to
bind one of the listener ports.
Dec 08 03:10:06.857 [err] Reading config failed--see warnings above. For
usage, try -h.
Dec 08 03:10:06.857 [warn] Restart failed (config error?). Exiting.

The config has "User tor", the daemon gets started as root. After
dropping priviledges, binding to <1024 might fail.

Is the rebinding of the or-port on HUP a new "feature"?
Do I have to update the RC script to include any new options to make
this work?

What else could have caused this, if anything?


Sincerely

Sebastian


***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxxx with
unsubscribe or-talk    in the body. http://archives.seul.org/or/talk/