| Anonymous | Login | 2024-05-18 16:08 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 | ||||
| 0008601 | ClearOS | app-network - Network Settings | public | 2016-05-10 09:19 | 2018-10-03 07:41 | ||||
| Reporter | user2 | ||||||||
| Assigned To | user2 | ||||||||
| Priority | normal | Severity | major | Reproducibility | have not tried | ||||
| Status | closed | Resolution | won't fix | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 6.8.0 Beta 1 | ||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0008601: Syswatch "reload" is not working properly | ||||||||
| Description | When network configuration changes are done, a syswatch "reload" is triggered. This reload is not working properly - the old configuration settings persist. Avoid reloads and do a full restart. With clearsync events handling most of the old syswatch jobs (e.g. updating network settings for IDS, IPS, Squid, etc), a restart is quick and easy these days. It's almost down to being a dedicated network/multiwan monitoring daemon. | ||||||||
| 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 09:19 | user2 | New Issue | |
| 2016-05-10 09:19 | user2 | Status | new => assigned |
| 2016-05-10 09:19 | user2 | Assigned To | => user2 |
| 2016-05-10 09:19 | user2 | Issue generated from: 0008181 | |
| 2016-05-10 09:19 | user2 | Relationship added | related to 0008181 |
| 2018-10-03 07:41 | user2 | Status | assigned => closed |
| 2018-10-03 07:41 | user2 | Resolution | open => won't fix |
|
Issue History |