Path: csiph.com!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail From: Dmitry Goncharov Newsgroups: gnu.bash.bug Subject: Re: Is this a bug? Date: Thu, 6 Aug 2020 14:39:29 -0400 Lines: 11 Approved: bug-bash@gnu.org Message-ID: References: <1361377909.989786.1596736417780.ref@mail.yahoo.com> <1361377909.989786.1596736417780@mail.yahoo.com> NNTP-Posting-Host: lists.gnu.org Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Trace: usenet.stanford.edu 1596739183 10975 209.51.188.17 (6 Aug 2020 18:39:43 GMT) X-Complaints-To: action@cs.stanford.edu Cc: "bug-bash@gnu.org" To: George R Goffe Envelope-to: bug-bash@gnu.org X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=HsuxLK0KwhvoIxXywSOQcWCJxdWAb8QSkEhymkNwwH8=; b=QsQ2duC2j6YM5arEHMQTK7O30KUZelEKYGO778Ewsa7j+rF530zuxaqQQiAWcE56J8 mLEErRJzmJIMli1zEFbfyI5RyTaNOhfOCbDSKXm0/++C0UHi5h+hT748QEygSm030v8Z Nvd6D8JuxY0TvZT1e4f2qq3iCaqeBViNXuM3/r7qkMTu8ks/l3EqsUxUj0CPLe8GUbBu Ygf7/FEJaYTFUQWN3dyediYM7wDPIrnVCykkRCYiEk+U84yjkC1to2vU/3K+hyJnbUXq pcEVdRedIdRUFPhkP2pUidMcZHgp1ebIlQ564DiA8WOlcnlfQMP9X7VmG/Es34z/H76d pw2Q== X-Gm-Message-State: AOAM5305uxe9Qcj6rGxAqPHSOiejMykY6Em05z8uB8rKz8n2th9x5ICx E1z8YnSMO7c/GNRa11qhYD2fhTDKtpIc1XleWhI= X-Google-Smtp-Source: ABdhPJzdVwtWh12M2trjKrENhO44K2O3Cr8jar+VJUgVkAwt1P1/YOU+G5hhjmON+ovbyBWnuaSv7q2ZMOFGuHS1JRw= X-Received: by 2002:ac8:3d92:: with SMTP id v18mr10448287qtf.104.1596739178123; Thu, 06 Aug 2020 11:39:38 -0700 (PDT) In-Reply-To: <1361377909.989786.1596736417780@mail.yahoo.com> Received-SPF: pass client-ip=209.85.160.177; envelope-from=gonch.dmitry@gmail.com; helo=mail-qt1-f177.google.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/08/06 14:39:38 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: 1 X-Spam_score: 0.1 X-Spam_bar: / X-Spam_report: (0.1 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=1, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: bug-bash@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports for the GNU Bourne Again SHell List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-Mailman-Original-Message-ID: X-Mailman-Original-References: <1361377909.989786.1596736417780.ref@mail.yahoo.com> <1361377909.989786.1596736417780@mail.yahoo.com> Xref: csiph.com gnu.bash.bug:16725 On Thu, Aug 6, 2020 at 1:54 PM George R Goffe wrote: > I have several directories on a system with > 300k files. When I use file= name completion bash freezes for over a minute depending on the number of f= iles. I'm pretty sure that bash has to read the directory to do the complet= ion but the read appears to be uninterruptible. Is this a bug? Why don't you run strace (or truss or whatever you have on your system) and see which syscall bash is blocked in? regards, Dmitry