public-inbox.git - an "archives first" approach to mailing lists

Date	Commit message (Collapse)
2024-04-28	send_cmd4: make `tries' a per-call parameter
	While existing callers are private (lei, *-index, -watch) are private, we should not be blocking the event loop in public-facing servers when we hit ETOOMANYREFS, ENOMEM, or ENOBUFS.
2023-10-06	ipc: lower-level send_cmd/recv_cmd handle EINTR directly
	This ensures script/lei $send_cmd usage is EINTR-safe (since I prefer to avoid loading PublicInbox::IPC for startup time). Overall, it saves us some code, too.
2023-09-24	ipc: recv_cmd4 clobbers destination buffer on errors
	Handling this should be done at the lowest levels possible; so away from higher-level lei code.
2023-02-22	sendmsg: prefix sleep message with `#'
	It's an informative message that's harmless, so hopefully the `#' prefix puts the users mind at ease. (I saw it on an `lei import' against an IMAP source)
2022-04-26	lei: move to v5.12 to avoid "use strict"
	Socket.pm still loads strict.pm, unfortunately, which hurts startup time; but we'll save some LoC this way.
2022-03-23	recv_cmd: do not undef recvmsg buffer arg on errors
	It's a waste of ops and cycles, and inconsistent with perl sysread() behavior which doesn't touch the supplied buffer on errors.
2021-10-23	cmd_ipc4: retry sendmsg on ENOBUFS/ENOMEM/ETOOMANYREFS
	I'm seeing ENOBUFS on a RAM-starved system, and slowing the sender down enough for the receiver to drain the buffers seems to work. ENOMEM and ETOOMANYREFS could be in the same boat as ENOBUFS. Watching for POLLOUT events via select/poll/epoll_wait doesn't seem to work, since the kernel can already sleep (or return EAGAIN) for cases where POLLOUT would work.
2021-02-03	cmd_ipc4: fix comments and formatting

2021-01-14	cmd_ipc: support + test EINTR + EAGAIN, no FDs
	We'll ensure our {send,recv}_cmd4 implementations are consistent w.r.t. non-blocking and interrupted sockets. We'll also support receiving messages without FDs associated so we don't have to send dummy FDs to keep receivers from reporting EOF.
2021-01-12	ipc: start supporting sending/receiving more than 3 FDs
	Actually, sending 4 FDs will be useful for lei internal xsearch work once we start accepting input from stdin. It won't be used with the lightweight lei(1) client, however. For WWW (eventually), a single FD may be enough.
2021-01-12	cmd_ipc: send FDs with buffer payload
	For another step in in syscall reduction, we'll support transferring 3 FDs and a buffer with a single sendmsg/recvmsg syscall using Socket::MsgHdr if available. Beyond script/lei itself, this will be used for internal IPC between search backends (perhaps with SOCK_SEQPACKET). There's a chance this could make it to the public-facing daemons, too. This adds an optional dependency on the Socket::MsgHdr package, available as libsocket-msghdr-perl on Debian-based distros (but not CentOS 7.x and FreeBSD 11.x, at least). Our Inline::C version in PublicInbox::Spawn remains the last choice for script/lei due to the high startup time, and IO::FDPass remains supported for non-Debian distros. Since the socket name prefix changes from 3 to 4, we'll also take this opportunity to make the argv+env buffer transfer less error-prone by relying on argc instead of designated delimiters.