ClearFoundation Tracker - ClearOS | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0010581 | ClearOS | app-events - Events System | public | 2016-09-15 09:48 | 2016-11-30 10:28 |
| Reporter | user2 | ||||
| Assigned To | user2 | ||||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Platform | OS | OS Version | |||
| Product Version | 7.2.0 | ||||
| Target Version | 7.3.0 Beta 1 | Fixed in Version | 7.3.0 Beta 1 | ||
| Summary | 0010581: Create an "onboot" event | ||||
| Description | In ClearOS, we need to bind to specific interfaces (e.g. Squid, CUPS) more than a typical Linux distribution. Many upstream systemd scripts contain this directive: [Unit] ... After=network.target The problem: there's no guarantee that the network has bind-able interfaces when the "network.target" event occurs. Since we don't want to patch a bunch of upstream systemd scripts, create an "onboot" event as a workaround. Any app that needs to bind to specific IPs should have a sanity check script added to /var/clearos/events/onboot. See app-print-server for an example. | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2016-09-15 09:48 | user2 | New Issue | |||
| 2016-09-15 09:48 | user2 | Status | new => resolved | ||
| 2016-09-15 09:48 | user2 | Fixed in Version | => 7.3.0 Beta 1 | ||
| 2016-09-15 09:48 | user2 | Resolution | open => fixed | ||
| 2016-09-15 09:48 | user2 | Assigned To | => user2 | ||
| 2016-11-16 09:12 | user2 | Target Version | 7.3.0 Beta 1 => 7.3.0 Beta 1 | ||
| 2016-11-16 09:12 | user2 | Fixed in Version | 7.3.0 Beta 1 => 7.3.0 Beta 1 | ||
| 2016-11-30 10:28 | user2 | Status | resolved => closed | ||
| There are no notes attached to this issue. |