6cd4a1b888
Order qubes-meminfo-writer-dom0 before systemd-user-sessions
...
qubes-vm@.service would already cause this ordering, but not every user
has any autostart=True VMs.
Also needed to maybe f*x QubesOS/qubes-issues#3149 at some point.
6 years ago
fbbd21a54b
qmemman-meminfo-writer: send simplified meminfo value
...
Send just one value - used memory (which is calculated anyway),
instead of full input data. This greatly simplify parsing at qmemman
side.
Fixes QubesOS/qubes-issues#1312
7 years ago
d95174f52c
makefile: honor build env CFLAGS and LDFLAGS
...
Generally build env (rpmbuild, dpkg-buildpackage) provide sane and
useful defaults.
Fixes hardening-no-relro lintian warning.
QubesOS/qubes-issues#1416
9 years ago
2f5ef8e2aa
use 64-bit integers for memory sizes to support > 2 TB RAM
9 years ago
2d871075cc
Report Xen balloon current size instead of Linux total memory
...
This results in qmemman knowing about the memory map overhead and
properly sizing VMs.
9 years ago
9ee8281ab7
archlinux: ensure /usr/sbin is not use to follow archlinux packaging guidelines
9 years ago
ceb0e25d3b
fedora: fix systemd service files permission
9 years ago
7693f097d4
use systemd in debian
10 years ago
566bd2901b
Initial native debian packaging
10 years ago
bc75b6559b
Use xenstore.h when xen >= 4.2
10 years ago
b12f1539a4
Add -Wextra -Werror to all C code
...
Not only the security-critical one.
10 years ago
12a9049cfe
Fix some more -Wextra warnings
10 years ago
7f2ac22d49
meminfo-writer: fix high memory check for more than about 150 GB RAM
10 years ago
e6c29bbae1
meminfo-writer: ensure we do not write outside our buffer
...
Reading the max size would cause a NUL to be written after
the buffer, while an error would cause one to be written
before it.
10 years ago
2758d2a1d3
meminfo-writer: kill child if we error out due to failure to write the pid file
10 years ago
1a72505d24
meminfo-writer: simple command line sanity checks
10 years ago
0c718b7f54
meminfo-writer: trivial typo fix
10 years ago
76afc2e72f
meminfo-writer: ensure we always use the first parses memory info
...
It could plausibly be ignored for stupidly large thresholds
10 years ago
7e086970e9
meminfo-writer: make meminfo parsing more robust
...
- ensure we see all the expected fields
- avoid overflowing name buffer on malformed input
- avoid possible overread when the last line is small
10 years ago
2ba46ff17f
meminfo-writer: make buffers const where possible
10 years ago
f0b1271a5e
Include meminfo-writer
...
It is common for dom0 and VM, so keep in one place for both of them.
10 years ago
Rusty Bird