aboutsummaryrefslogtreecommitdiff
path: root/Cargo.toml
diff options
context:
space:
mode:
authorMroik <mroik@delayed.space>2026-04-11 04:02:53 +0200
committerMroik <mroik@delayed.space>2026-04-13 06:56:11 +0200
commitffc0ad7c86408193b213c46cbca5c0d8b60f8632 (patch)
tree2612530158ed0a2529f866e23f324758011efcfd /Cargo.toml
parentb336fd39444e8089d35a7a2bd4c0c3e8228c6c36 (diff)
Do not propagate TcpListener.accept() errors
Errors produced by the socket may not be necessarily fatal, meaning that while a connection might be dropped the process should be able to resume execution as if nothing happened and accept the next connection. Error handling for accept() has been copied from NGINX's [1]. [1] https://stackoverflow.com/questions/76955978/which-socket-accept-errors-are-fatal Signed-off-by: Mroik <mroik@delayed.space>
Diffstat (limited to 'Cargo.toml')
-rw-r--r--Cargo.toml1
1 files changed, 1 insertions, 0 deletions
diff --git a/Cargo.toml b/Cargo.toml
index 570c437..cbd5e80 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -6,6 +6,7 @@ edition = "2024"
[dependencies]
anyhow = "1.0.102"
env_logger = "0.11.10"
+libc = "0.2.184"
log = "0.4.29"
rusqlite = "0.39.0"
tokio = { version = "1.51.0", features = ["macros", "rt-multi-thread", "sync"] }
XMR address: 854DmXNrxULU3ZFJVs4Wc8PFhbq29RhqHhY8W6cdWrtFN3qmooKyyeYPcDzZTNRxphhJ5UzASQfAdEMwSteVqymk28aLhqj