Konstantin Ryabitsev <konstan...@linuxfoundation.org> wrote: > On Tue, May 03, 2022 at 01:50:52PM +0100, Filipe Manana wrote: > > > Perhaps it's already running lei-daemon as an older version? > > > "lei daemon-kill" should kill it and it'll restart on the next > > > command, unless something else got wedged. > > > > Ah, running "lei daemon-kill" fixed it. > > I don't know if I did something wrong before, but after running that, > > lei is now working fine.
Good to know! > I think this is actually a common occurrence. Any way lei-daemon can recognize > when there's a version mismatch between itself and the binary talking to it? Sorta, but even I manage to lose track of which commits cause protocol or internal API changes since everything is lazy-loaded. I think the best way would be to have inotify/kqueue watch the /PublicInbox/ directory and auto-restart iff no active commands are running... -- unsubscribe: one-click, see List-Unsubscribe header archive: https://public-inbox.org/meta/
