| Anonymous | Login | 2024-04-24 18:25 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 | ||||
| 0000934 | ClearOS | app-base - Base System | public | 2013-01-14 09:16 | 2013-04-26 19:41 | ||||
| Reporter | user2 | ||||||||
| Assigned To | user2 | ||||||||
| Priority | normal | Severity | tweak | Reproducibility | N/A | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | 6.4.0 Beta 2 | Fixed in Version | 6.4.0 Beta 2 | ||||||
| Summary | 0000934: Add clearsync reload event | ||||||||
| Description | When a new or updated configuration lands in /etc/clearsync.d, clearsync should be restarted. To prevent missing an event during a reload, move this functionality to the base app. Right now, there are a good dozen apps that restart clearsync on an upgrade event -- too frequent and too heavy handed. | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0000642) user2 2013-01-14 09:37 |
SVN 5418 |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2013-01-14 09:16 | user2 | New Issue | |
| 2013-01-14 09:30 | user2 | Status | new => confirmed |
| 2013-01-14 09:37 | user2 | Note Added: 0000642 | |
| 2013-01-14 09:37 | user2 | Status | confirmed => resolved |
| 2013-01-14 09:37 | user2 | Fixed in Version | => 6.4.0 Beta 2 |
| 2013-01-14 09:37 | user2 | Resolution | open => fixed |
| 2013-01-14 09:37 | user2 | Assigned To | => user2 |
| 2013-04-26 19:41 | user2 | Status | resolved => closed |
|
Issue History |