PacketFence - BTS - PacketFence |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0000835 | PacketFence | core | public | 2009-10-30 16:36 | 2012-02-29 10:58 |
|
Reporter | obilodeau | |
Assigned To | obilodeau | |
Priority | normal | Severity | minor | Reproducibility | random |
Status | closed | Resolution | unable to reproduce | |
Platform | | OS | | OS Version | |
Product Version | | |
Target Version | | Fixed in Version | | |
fixed in git revision | |
fixed in mtn revision | |
|
Summary | 0000835: concurrency FAIL! |
Description | I think we have a concurrency problem in violation_trigger when its called from pfsetvlan. Somehow I think the content of the @trigger_info array of hash-references is swapped when another thread hit a violation_trigger spot too.
I need to reproduce in a controlled environment before jumping to conclusions.. |
Steps To Reproduce | |
Additional Information | |
Tags | No tags attached. |
Relationships | |
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2009-10-30 16:36 | obilodeau | New Issue | |
2009-10-30 16:37 | obilodeau | Status | new => assigned |
2009-10-30 16:37 | obilodeau | Assigned To | => obilodeau |
2011-01-18 11:50 | obilodeau | Note Added: 0001816 | |
2011-01-18 11:50 | obilodeau | Status | assigned => closed |
2011-01-18 11:50 | obilodeau | Resolution | open => unable to reproduce |
2012-02-29 10:58 | obilodeau | Category | future => core |