Closed jthulhu closed 2 years ago
lorri is socket activated. If anything accesses the socket the daemon is started by systemd.
Yes, but my issue is not that I can't start manually lorri, it's that when I open a project and that lorri is supposedly running, it prints lorri daemon is not running and this project has not yet been evaluated, please run lorri daemon
.
However, in the past few days, I could not reproduce this issue anymore (ie. lorri started working as expected)...
This happens if you install lorri for the first time and the socket is not created yet. Either reload your user session or run: systemctl --user start lorri.socket
.
I suggest you change the README then, since there it's written that the solution is systemctl --user daemon-reload
, which did not work for me. Or is it an other issue?
There is already a note about this and it says if ddaemon-reload does not work reboot.
Fine.
Lorri requires a running daemon, which is expected to be managed by
systemd
. However,systemd
refuses to startlorri
, as it claims lorri is configured to refuse manual start/stop, and is by default loaded but inactive. Launching lorri's daemon via command line works.To Reproduce
systemctl --user daemon-reload
as indicated (or reboot)lorri init
, thendirenv allow
lorri daemon
'Expected behavior The daemon should not be handled by hand, but automatically started by anyone (systemd, lorri itself, ...) but me.
Metadata OS: NixOS 21.05 / Kernel 5.10.66 Lorri: Lorri 1.5 (installed via home-manager, stable channel)