Anonymous | Login | 2024-11-23 02:29 EST |
Main | My View | View Issues | Change Log | Roadmap |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||
0001509 | PacketFence | core | public | 2012-08-08 13:28 | 2015-02-18 10:59 | |||
Reporter | obilodeau | |||||||
Assigned To | ||||||||
Priority | normal | Severity | major | Reproducibility | always | |||
Status | closed | Resolution | open | |||||
Platform | OS | OS Version | ||||||
Product Version | ||||||||
Target Version | 3.6.1 | Fixed in Version | ||||||
Summary | 0001509: improve service start management (radiusd fails to start silently) | |||||||
Description | When starting packetfence, if radiusd cannot start for whatever reason, no indication whatsoever that it didn't start is output. However a look at the exit status reveals if it started successfully or not. I think we should alter the services management layer to be able to look at exit statuses and report problems accordingly. It's probably time to do the whole pf::services refactoring into objects.. | |||||||
Tags | No tags attached. | |||||||
fixed in git revision | ||||||||
fixed in mtn revision | ||||||||
Attached Files | ||||||||
Notes | |
(0003907) lmunro (administrator) 2015-02-18 10:59 |
Obsolete bug tracker entries. PF 4 introduced changes that either make these irrelevant or impossible to reproduce. New issues are moving to github issues. |
Issue History | |||
Date Modified | Username | Field | Change |
2012-08-08 13:28 | obilodeau | New Issue | |
2012-10-19 11:37 | fgaudreault | Target Version | => general |
2012-10-26 16:08 | fgaudreault | Target Version | general => 3.6.1 |
2015-02-18 10:59 | lmunro | Note Added: 0003907 | |
2015-02-18 10:59 | lmunro | Status | new => closed |
Copyright © 2000 - 2012 MantisBT Group |