I am also seeing this bug, and would like to see this resolved outside
of the workaround to a port higher than 1024. It seems to be a problem
relating to binding the TCP port later after it has already dropped
permissions. My rsyslog.conf file (attached) is using the
$PrivDropToUser syslog and
The example server configuration listening on TCP 514 that fails.
** Attachment added: Ubuntu 12.04 LTS Server rsyslog.conf from rsyslog
5.8.6-1ubuntu8 Example
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/789174/+attachment/3265563/+files/rsyslog.conf
--
You received this bug
Scott,
Thank you for the information. In my initial browse I'm not seeing
anything updated regarding improved listener behavior, so I think that
sleep workaround stands. I'm definitely looking into that over either
changing the port or running as root (which I'd like to avoid if at all
