Anonymous | Login | 2024-11-21 01:36 MST |
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 | ||||
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. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||