Erlang/OTP Forums
Author Message

<  Erlang bugs mailing list  ~  SASL - duplicate alarms bug
asergey
Posted: Thu Jul 28, 2005 4:53 pm Reply with quote
User Joined: 12 Mar 2005 Posts: 313
Is there a reason that the SASL's alarm handler doesn't check for
duplicate alarms before adding new ones to the list?

If you do the following on the system with low disk space / free memory:

1. Start SASL
2. Start OS_MON
3. Stop OS_MON
4. Start OS_MON

you'll get duplicate alarms that are not easily clearled (you'd need to
call alarm_handler:clear_alarm() multiple times for the same AlarmID...

17> alarm_handler:get_alarms().
[{system_memory_high_watermark,[]},
{{disk_almost_full,"/mnt/cdrom"},[]},
{{disk_almost_full,"/usr"},[]},
{system_memory_high_watermark,[]},
{{disk_almost_full,"/mnt/cdrom"},[]},
{{disk_almost_full,"/usr"},[]}]
18> alarm_handler:clear_alarm(system_memory_high_watermark).
[{{disk_almost_full,"/mnt/cdrom"},[]},
{{disk_almost_full,"/usr"},[]},
{system_memory_high_watermark,[]},
{{disk_almost_full,"/mnt/cdrom"},[]},
{{disk_almost_full,"/usr"},[]}]

This looks like a bug to me.

Serge


Post generated using Mail2Forum (http://m2f.sourceforge.net)
Back to top View user's profile Send private message

Display posts from previous:  

All times are GMT
View next topic
View previous topic
Page 1 of 1
Erlang Forum - Trap Exit Forum Index  ~  Erlang bugs mailing list
This forum is locked: you cannot post, reply to, or edit topics.

Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum
Hosted by Erlang Solutions    |    Powered by phpBB and NoseBleed 1.14