From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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=-2.9 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.6 Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 644D01F428 for ; Tue, 28 Mar 2023 04:08:32 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20210112 header.b=m86XXqFO; dkim-atps=neutral Received: by mail-ed1-x530.google.com with SMTP id eg48so44253634edb.13 for ; Mon, 27 Mar 2023 21:08:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679976509; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Aa4jLa4M5ynJbjRWlGd1wZFKdJVOnEwUXMTnQwIDDjc=; b=m86XXqFOhH6SSTKl/AgpdLsmZUXchR8aSbKmw11u0R3dSSoC6BX0dKclXMHIocE7aT qEID0glIuBnbeCJtx3W5Xi8yPUzFCiBeV0ZVxGvuO44B74QWWe8L5V+l0gL0x3Tml1ZG f/X4OYcjjI4bLymWxHydyvDV8K+lTtn9VKTta+X0GyYTIRCiEnJFfzUEnPptEShqKVhy /B6N0aekN9L73PPnZ5kzQ/JIdrNwj80bzRGaCf3Yb1a8lBn8eL1tsRHHKha2vwIJADFN QuE+O0mMz+3FIJhrxWWSTQxmtQWmcuJzmavylLkm6Bl7Q40bBIXeHe6xL+z9xN2RI0v6 uzUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679976509; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Aa4jLa4M5ynJbjRWlGd1wZFKdJVOnEwUXMTnQwIDDjc=; b=5ITrRdR0qJHYYUIRqdHXlKfOnQc3wl9gyc/pAEcXON3qdYjJlNL0x4oxrUaeUfKc+N gLsugEBAoUocqA6+sdCdbZjuxXn7EeV/n4YvbUWUdx4p9JNp+X4XVNndvbSBIUY7XLo0 ST2GZG/ndnVGaRaLq3bE1fm1omdu6mWfFzKhRWyPNk8NOaFkHXZ4vRFQiaddtYdiPXjQ pfqJB5ogzDHrzYdEDaH8QaFkOdUUXoH2qjytbMRlymkiJVLwl0StX+1JaXBGauAPIRXV Mir+838GHXQ4vGMNccxGug503HkevRfA9LNjQlxuT980FFshL3TSj2GYKo7BpBMJuFKo sqEQ== X-Gm-Message-State: AO0yUKUpMosoPD6bWHyHS83pykNBToWwHT2vMPkfRTzGgA1HFctGat+T GzZOqrZDLJw/yOc5gcrKer0fxlCYywr05PWWZKA= X-Google-Smtp-Source: AK7set8jUScvc41GRc1Ulm+qCrDRNaxlyC2wXw0jZ7+xSuClOJqsFjXJQ+L5KkbS2E7czP9NSCeaUiqY2oLMWmIa8Nk= X-Received: by 2002:a17:907:2c66:b0:931:faf0:3db1 with SMTP id ib6-20020a1709072c6600b00931faf03db1mr10952822ejc.4.1679976509561; Mon, 27 Mar 2023 21:08:29 -0700 (PDT) MIME-Version: 1.0 References: <20230328013226.M125137@dcvr> <20230328025205.M639038@dcvr> <20230328033816.M690495@dcvr> In-Reply-To: <20230328033816.M690495@dcvr> From: Louis DeLosSantos Date: Tue, 28 Mar 2023 00:08:18 -0400 Message-ID: Subject: Re: Issues with `lei` as non-root To: Eric Wong Cc: meta@public-inbox.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: > 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=E2=80=AFPM Eric Wong wrote: > > Louis DeLosSantos 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 > > > =3D=3D> /proc/sys/fs/inotify/max_user_instances <=3D=3D > > 128 > > > > > 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).