Opened 2 years ago
Closed 2 years ago
#182 closed enhancement (fixed)
Consider moving away the f/w checking code out from the qubes-manager...
| Reported by: | joanna | Owned by: | marmarek |
|---|---|---|---|
| Priority: | minor | Milestone: | Release 1 Beta 2 |
| Component: | core | Keywords: | |
| Cc: |
Description
...and perhaps rewrite it in C -- it really eats lots of CPU, and is currently executed every 5 sec -- this is quite a killer for batteries I think. Also, I think such code should be independent from the manager and should be part of the core instead.
Change History (3)
comment:1 Changed 2 years ago by joanna
- Milestone changed from Release 1 Beta 1 to Release 1 Beta 2
comment:2 Changed 2 years ago by marmarek
- Owner changed from joanna to marmarek
- Status changed from new to assigned
comment:3 Changed 2 years ago by marmarek
- Resolution set to fixed
- Status changed from assigned to closed
Note: See
TracTickets for help on using
tickets.
Perhaps the better idea is just to display message directly from firewallvm, when loading firewall failed.
Maybe left only some flag in xenstore indicating result of last firewall loading (success/fail).
This will eliminate one data flow VM->dom0 which is always good.