PacketFence - BTS - PacketFence
View Issue Details
0000909PacketFencecorepublic2010-02-09 14:222015-02-13 15:35
obilodeau 
 
normalfeaturealways
closedopen 
 
investigate 
0000909: use pfcmd_vlan for modules relying on Net::Telnet
pfcmd_vlan since it's a brand new process, we no longer face all the bugs related to Net::Telnet use of sigalrm in a threaded perl program (see 0000902)

We could find a way to work around that by encapsulating calls to pfcmd_vlan.

But it could be solved if we move over to a multi process-based approach instead of a threaded approach.
No tags attached.
related to 0000907closed obilodeau pfsetvlan doesn't need to stop on SIGALRM 
related to 0000902closed  Net::Telnet and Net::Appliance::Session use alarm() for timeout which is incompatible with threaded perl 
Issue History
2010-02-09 14:22obilodeauNew Issue
2010-02-09 14:22obilodeauStatusnew => assigned
2010-02-09 14:22obilodeauAssigned To => obilodeau
2010-02-09 14:22obilodeauRelationship addedrelated to 0000907
2010-02-09 14:23obilodeauDescription Updated
2010-02-09 14:23obilodeauRelationship addedrelated to 0000902
2010-04-15 17:43obilodeauProjectPacketFence 1.9 => PacketFence
2010-05-05 17:02obilodeauNote Added: 0001557
2010-05-05 17:02obilodeauSeverityminor => feature
2010-05-05 17:02obilodeauCategory1.9.0 => 1.10.x
2010-05-05 17:02obilodeauTarget Version => 1.10.0
2010-11-19 14:25obilodeauTarget Version1.10.0 => 2.0.0
2010-11-19 14:28obilodeauCategory1.10.x => 2.x
2010-11-19 14:51obilodeauCategory2.x => core
2011-01-18 09:30obilodeauTarget Version2.0.0 => 2.1.0
2011-03-03 15:16obilodeauTarget Version2.1.0 => +1
2011-03-03 15:18obilodeauTarget Version+1 => +2
2012-10-19 14:56fgaudreaultAssigned Toobilodeau =>
2012-10-19 14:56fgaudreaultTarget Versionlong-term => investigate
2012-10-19 14:56fgaudreaultNote Added: 0003205
2015-02-13 15:35lmunroNote Added: 0003753
2015-02-13 15:35lmunroStatusassigned => closed

Notes
(0001557)
obilodeau   
2010-05-05 17:02   
Right now problem mitigated by new alarm handler and log message. Re-evaluate for 1.10.x
(0003205)
fgaudreault   
2012-10-19 14:56   
Well re-evaluate :) I think we can close this one.
(0003753)
lmunro   
2015-02-13 15:35   
No longer relevant.