From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <e@80x24.org>
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on dcvr.yhbt.net
X-Spam-Level: 
X-Spam-ASN:  
X-Spam-Status: No, score=-4.2 required=3.0 tests=ALL_TRUSTED,BAYES_00,
	DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF shortcircuit=no
	autolearn=ham autolearn_force=no version=3.4.6
Received: from localhost (dcvr.yhbt.net [127.0.0.1])
	by dcvr.yhbt.net (Postfix) with ESMTP id C20A81F41C;
	Tue, 28 Mar 2023 03:38:16 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=80x24.org;
	s=selector1; t=1679974696;
	bh=2MxadWbMRKj3hfFltBdYH4WsqRG668QBY2ZcrMHb9ms=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
	b=YwDaL0XCVUcQKF6hjHcvW4qOiwO3xX51w7aX1wNiza8RdB2C6156CjJbf/3IkWfcL
	 DG+F2f2DUOPJiMikxKE+2UOvSlv6j7jLGi//Ig43ItP9qoVQIysLCE23Sujj6XYM8v
	 ZVZ3jN+TB0M/VlUNwPLRtYLO+72PHq3UjjjCubqc=
Date: Tue, 28 Mar 2023 03:38:16 +0000
From: Eric Wong <e@80x24.org>
To: Louis DeLosSantos <louis.delos@gmail.com>
Cc: meta@public-inbox.org
Subject: Re: Issues with `lei` as non-root
Message-ID: <20230328033816.M690495@dcvr>
References: <CAE6jdTpoNijeb8gMTX2D=CNWOKx7LuC9vpn24TwSaKAXqrpHOA@mail.gmail.com>
 <20230328013226.M125137@dcvr>
 <CAE6jdTok74ORobFTrxtv=JxpZ1PKLi4KtOtY80RLFMdjDWww-w@mail.gmail.com>
 <20230328025205.M639038@dcvr>
 <CAE6jdTqxeh-_+9WXvG-C4QfrgcWs7jm5X24YmK0Vmo5XU-0TLA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAE6jdTqxeh-_+9WXvG-C4QfrgcWs7jm5X24YmK0Vmo5XU-0TLA@mail.gmail.com>
List-Id: <meta.public-inbox.org>

Louis DeLosSantos <louis.delos@gmail.com> 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).