Loggers: no blocks flag

A logger's lines are written by a thread of its own, its clients only
queueing them, so a logger whose writes wait cannot hold a client's
thread or a loop: its blocks flag, giving its services a thread for each
client, is gone. ODBC was the logger setting it; its services are served
on loops now too. Only a logger whose thread could not be started is
written by its clients themselves, as before.

Plugins: struct logtype loses its last member, blocks.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Vladimir DubrovinandClaude Opus 5.5 committed 2026-10-27 15:32:01 +03:00
1 parent e09e20e71c
commit 270b02293e
3 files changed
+1 -3

No files matched your search

-1
View File
@@ -668,7 +668,6 @@ struct logtype {
int standard; /* kept open for the life of the process */
int text; /* writes a line of text: errors can go there */
int params; /* the string after a comma is parameters */
int blocks; /* waits for its writes other than in sockpoll() */
};
/* What a log's queue holds: a line (log.c's struct logslot, of which this