| Anonymous | Login | 2024-04-26 07:22 MDT |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0008641 | ClearOS | syswatch | public | 2016-05-10 13:36 | 2016-05-17 11:37 | ||||
| Reporter | user2 | ||||||||
| Assigned To | user2 | ||||||||
| Priority | normal | Severity | minor | Reproducibility | have not tried | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 7.2.0 | ||||||||
| Target Version | 7.2.0 Updates | Fixed in Version | 7.2.0 Updates | ||||||
| Summary | 0008641: Extra PPPoE kill is not selective enough | ||||||||
| Description | PPPoE connections can sometimes lock PPP devices which causes a gentle "ifdown pppX" to no longer function. Syswatch comes a long and kills the pppd/pppoe process, but the regex for determining the process ID is lame. Tighten it up. | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
||||||
|
||||||
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2016-05-10 13:36 | user2 | New Issue | |
| 2016-05-10 13:37 | user2 | Issue cloned: 0008651 | |
| 2016-05-10 13:37 | user2 | Relationship added | related to 0008651 |
| 2016-05-17 11:37 | user2 | Status | new => resolved |
| 2016-05-17 11:37 | user2 | Fixed in Version | => 7.2.0 Updates |
| 2016-05-17 11:37 | user2 | Resolution | open => fixed |
| 2016-05-17 11:37 | user2 | Assigned To | => user2 |
| 2016-05-17 11:37 | user2 | Status | resolved => closed |
|
Issue History |