dpibreak.git/src/platform, branch v0.4.2System-wide DPI circumvention with minimal configuration
http://git.dilluti0n.com/dpibreak.git/atom?h=v0.4.22026-02-15T18:18:26Zwindows: fix nit build failure2026-02-15T18:18:26Zdilluti0nhskimse1@gmail.com2026-02-15T18:18:07Zurn:sha1:17702221d834de2b13789244edfcb4f9ee18f135linux: add TODO on daemonize2026-02-15T17:55:54Zdilluti0nhskimse1@gmail.com2026-02-15T17:55:54Zurn:sha1:5236617a0db0578794bb51f01b0a55028d9d1b3eopt: decouple set_opt() from logging2026-02-15T17:52:03Zdilluti0nhskimse1@gmail.com2026-02-15T17:49:49Zurn:sha1:b68753e878c440f1a11aa89f1f359764f1609734
set_opt() was logging each option as it set them, which created a
tight coupling between option initialization and log output timing.
This was particularly problematic for daemon mode: daemonize must
happen after set_opt() (to know whether -D was passed) but before
logging (so output goes to the log file, not stdout).
Split into set_opt() -> InitializedOpts and InitializedOpts::log(),
using a typestate pattern to enforce at compile time that log() cannot
be called before set_opt(). This lets each platform's bootstrap()
handle daemonization between the two steps:
let initialized = opt.set_opt()?;
platform::bootstrap()?; // daemonize here if needed
initialized.log(); // now safe to log
Also:
- Move daemonize_1() into platform::bootstrap() on both platforms
- Make daemonize_1() / service_main() private to their platform modules
- Fix the long-standing TODO about using log_println in daemonize()
linux: fix log file truncated when daemonize fails2026-02-15T17:23:41Zdilluti0nhskimse1@gmail.com2026-02-15T17:21:36Zurn:sha1:90972573f4ecf838469e396fb4f81fa02cade5de
1. open without O_APPEND (offset = 0) and O_TRUNC (original bug)
2. dup file descripter with .try_clone() and feed it to daemonize
3. truncate file with .set_len(0) on child after daemonize.start()
succed
Fixes: https://github.com/dilluti0n/dpibreak/issues/17
linux: exit if not root2026-02-15T16:30:46Zdilluti0nhskimse1@gmail.com2026-02-15T16:30:46Zurn:sha1:38382fa2bd354617d930b339a370cbe23b6e7945linux: repurpose bootstrap to do things before requiring cleanup2026-02-15T16:25:16Zdilluti0nhskimse1@gmail.com2026-02-15T16:20:26Zurn:sha1:b07153539ca5b8674ba15dece87883bae1056900linux: modify PID_FILE and log path2026-02-15T16:14:46Zdilluti0nhskimse1@gmail.com2026-02-15T16:14:46Zurn:sha1:3763efb7858cdae792be49f6974c4e5a098d46d8
Fixes: https://github.com/dilluti0n/dpibreak/issues/16
linux: add PID file locking for single instance enforcement2026-02-15T13:36:06Zdilluti0nhskimse1@gmail.com2026-02-15T13:36:06Zurn:sha1:b26c2c8de5260b0e2a0b52cd838cb8a4bc1a63c1
Prevent multiple non-daemon dpibreak instances using flock(). Show
existing PID on conflict and maintain lock until process termination.
linux: extract PID_FILE constant for reuse2026-02-15T13:13:35Zdilluti0nhskimse1@gmail.com2026-02-15T13:05:13Zurn:sha1:f31938fd8eea3d05f9e62daee236cf7c56ade227Consolidate setup logic into run()2026-02-15T13:04:25Zdilluti0nhskimse1@gmail.com2026-02-15T13:01:43Zurn:sha1:3cb2c192454964c2ae01e196eaa7fdd6434efeb5
The bootstrap/run separation was unnecessary. Move all initialization
(cleanup + nftables setup): into run() and skip bootstrap in daemon
mode. We repurpose the bootstrap() function to only run in non-daemon
mode for future foreground-only initialization.
- Add OPT_DAEMON option to detect daemon mode
- Move cleanup() and install_rules() from bootstrap() to run()
- Make bootstrap() a no-op (only called in non-daemon mode)