My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
  Advanced search   Search tips   Subscriptions
Issue 18: munged is uninterruptible and consumes cpu on FreeBSD 8.2 & 9.0
  Back to list
Status:  Fixed
Owner:  chris.m.dunlap
Closed:  Sep 2012

Sign in to add a comment
Project Member Reported by chris.m.dunlap, Sep 25, 2012
What steps will reproduce the problem?

Run munged on FreeBSD 8.2 or later.

What is the expected output? What do you see instead?

munged should consume negligible cpu when idle, and gracefully terminate upon receipt of a SIGTERM.  Instead, munged consumes an entire cpu and must be forcibly terminated with a SIGKILL.

What version of the software are you using? On what operating system?

munge-0.5.10 on FreeBSD 8.2 & 9.0

Please provide any additional information below.

This bug was introduced by commit 501d7a1dd24878daefbe123c8b76991f775be607.

This behavior can be averted by running munged with "--group-update-time=-1".
Sep 26, 2012
Project Member #1 chris.m.dunlap
Where's the clicky hyperlink?  Let's try revision 501d7a1dd24878daefbe123c8b76991f775be607.
Sep 26, 2012
Project Member #2 chris.m.dunlap
This issue was closed by revision 2ab4d6b42324.
Status: Fixed
Oct 19, 2012

For information this patch has been submitted to FreeBSD (, package munge-0.5.10_1 will work flawlessly.
Oct 19, 2012
Project Member #4 chris.m.dunlap
Thanks for the feedback.  I've setup FreeBSD VMs for testing so hopefully I can catch these types of errors before a release.
Sign in to add a comment

Powered by Google Project Hosting