> Thats a lot of tail processes.... Ugh, sorry to waste your time. All the tails were from a run away UI program I'm working on. Once I killed them, `let` runs just fine as non-root.
Thanks for the free tech support, hope I didn't steal your attention from something valuable :-D. On Mon, Mar 27, 2023 at 11:38 PM Eric Wong <[email protected]> wrote: > > Louis DeLosSantos <[email protected]> wrote: > > > Definitely not; the lei-daemon is per-user. > > > > Okay, maybe this is the issue to begin with? I installed lei from dnf. > > I'm not sure what launches the daemon, is it launched on first run? > > > > If that is the case, it was probably launched when I restored to `sudo > > lei q ....` command. > > But, if its running as systemd service, I could move it to user service. > > You shouldn't need to manage it as a service; it's auto-started > and killing it is harmless in most cases. I'm considering it > have it auto-exit if it stays idle for a long time and there's > no active inotify watches. > > lei-daemon doesn't start until any other lei command is invoked; > so it shouldn't be started on installation. > > > # show system-wide limits > > > ==> /proc/sys/fs/inotify/max_user_instances <== > > 128 > > <snip> > > > tail 367093 louis 4r a_inode 0,14 0 > > Thats a lot of tail processes.... > I wonder if they were spawned by `lei q -v' for emitting curl stderr? > They should be auto-killed. > (or if you have some other reason for running tail on your system).
