Description of the problem:

syslogd after including the latest patch
"sysklogd-1.4.1-noforward_local_address.patch" introduced a memory leak when
using remote logging.
Everytime the syslogd daemon is restarted, it keeps leaking memory around the
size of ifaddrs and this is because there is a usage of getifaddrs() without
calling then freeifaddrs() to clear the dynamically allocated data.

Version-Release number of selected component (if applicable):
sysklogd-1.4.1-26_EL

How reproducible:
Always

Steps to Reproduce:
1. Setup syslog for remote auditing:
   In remote host change /etc/sysconfig/syslog to get the flag -r.
(SYSLOGD_OPTIONS="-m 0 -r")
   In local host  change /etc/syslog.conf to log into remote (for this case we
used *.info  @remote)
2. Reload syslogd. SIGHUP.
3. Run the following:
   % while true ; do /bin/kill -HUP `pidof syslogd` ; cat /proc/`pidof
syslogd`/status | grep -i vmdata; done
  
Actual results:
         VmData:      148 kB
         VmData:      148 kB
         VmData:      148 kB
         VmData:      796 kB
         VmData:     1696 kB
         VmData:     2588 kB

Expected results:
         VmData:      148 kB
         VmData:      148 kB
         VmData:      148 kB
         VmData:      148 kB
         VmData:      148 kB
         VmData:      148 kB
	 
Additional info:
Patch attached tested and writen by the customer.

Business Impact:

The custmer is using syslogd which configured logging to local files and remote
hosts. This customer's system is heavily logging, therefore logrotate runs every
10 seconds. Since kill -HUP is called when running logrotate, the syslogd's
memory increases swiftly.