PacketFence - BTS - PacketFence | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000978 | PacketFence | error-handling | public | 2010-05-05 10:09 | 2015-02-13 15:24 |
| Reporter | obilodeau | ||||
| Assigned To | obilodeau | ||||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | open | ||
| Platform | OS | OS Version | |||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| fixed in git revision | |||||
| fixed in mtn revision | |||||
| Summary | 0000978: add a restart reason to packetfence's `pfcmd service` | ||||
| Description | Let me give an example: I want to know if the daemon restarted because of logrotation, the watchdog or because of a manual restart. With a restart reason field on the CLI, we could log that string into logs/packetfence.log directly as a restart reason. This way, in our logrotate script we do a bin/pfcmd service pf restart 'log rotation', in our watchdog, 'restarted by watchdog', etc. So when an entry is empty, we assume user restart. | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2010-05-05 10:09 | obilodeau | New Issue | |||
| 2010-05-05 10:09 | obilodeau | Status | new => assigned | ||
| 2010-05-05 10:09 | obilodeau | Assigned To | => obilodeau | ||
| 2010-11-19 14:25 | obilodeau | Target Version | 1.10.0 => 2.0.0 | ||
| 2011-01-18 09:30 | obilodeau | Target Version | 2.0.0 => 2.1.0 | ||
| 2011-03-03 15:16 | obilodeau | Target Version | 2.1.0 => +1 | ||
| 2011-03-03 15:18 | obilodeau | Target Version | +1 => +2 | ||
| 2015-02-13 15:24 | lmunro | Note Added: 0003681 | |||
| 2015-02-13 15:24 | lmunro | Status | assigned => closed | ||
| Notes | |||||
|
|
|||||
|
|
||||