Ubuntu
sipxtapi package

OsSysLogTask not assigning syslog server sockets correctly

Bug #1600671 reported by Thomas Gutzler
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sipxtapi (Ubuntu)
New
Undecided
Unassigned

Bug Description

OsSysLogTask::processAddSocket() is supposed to add a syslog server socket to the list of available sockets (mpSockets) if there is still one available. The loop which is inserting the newly created socket into mpSockets[] is not terminated when an available spot is found. This fills up the array the first time a syslog server is added leaving no room for more.
Worse, the syslog server will get multiple copies of the same log message blowing up the logfile unnecessarily.

Patch is attached.

Tags: patch
Revision history for this message
Thomas Gutzler (0-u1) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "OsSysLogTask.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
Thomas Gutzler (0-u1) wrote :

While we're looking at OsSysLogTask::processAddSocket()...
This patch fixes the above problem and makes sure that we're not adding the same syslog server socket twice

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.