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
Date: Tue, 28 Mar 2023 03:38:16 +0000 [thread overview]
Message-ID: <20230328033816.M690495@dcvr> (raw)
In-Reply-To: <CAE6jdTqxeh-_+9WXvG-C4QfrgcWs7jm5X24YmK0Vmo5XU-0TLA@mail.gmail.com>
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).
next prev parent reply other threads:[~2023-03-28 3:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 1:00 Issues with `lei` as non-root Louis DeLosSantos
2023-03-28 1:32 ` Eric Wong
2023-03-28 1:36 ` public-inbox.org downtime expected in the next 6-8 hours Eric Wong
2023-03-28 2:30 ` Issues with `lei` as non-root Louis DeLosSantos
2023-03-28 2:52 ` Eric Wong
2023-03-28 3:05 ` Louis DeLosSantos
2023-03-28 3:38 ` Eric Wong [this message]
2023-03-28 4:08 ` Louis DeLosSantos
2023-03-28 11:12 ` [PATCH] inotify: wrap with informative error message Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230328033816.M690495@dcvr \
--to=e@80x24.org \
--cc=louis.delos@gmail.com \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).