From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PCsEY-0007X4-CL for garchives@archives.gentoo.org; Mon, 01 Nov 2010 11:07:26 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A5AA3E08AD; Mon, 1 Nov 2010 11:07:03 +0000 (UTC) Received: from mail-ey0-f181.google.com (mail-ey0-f181.google.com [209.85.215.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 65426E08AD for ; Mon, 1 Nov 2010 11:07:03 +0000 (UTC) Received: by eyb6 with SMTP id 6so1788869eyb.40 for ; Mon, 01 Nov 2010 04:07:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:cc:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=U7S8ocdvhF2k6uJ/yYtgMizp1mszArtgTJXoUbeb7MA=; b=YITFOa/DhcRNlvO4LU+zqqbkTm9KCvWykvmYbQxjHmVD11TNNgXTTfPg6cPCU/tvVl EHLwb7EKaYU8Fg6Ldm9/DMVqRHY823GwFdin92SsmQWlZznUngmkXxv+b5gsOUc1DMmj flTqn1icNnGZvu+S8MffVVIdV4Vfv/pzVm4aU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=yEDkPB2PnRt4CuIhpvt2FMu8SKLitfnLZ5PZtA984ksjRMQ5SJbv3/jXz0XJvxejPl Of7xROblo3OQTxYXC3W3fXZkjJf6ef3ZlV6Gz2+UJM4zDL6KLMrm7NkczFoX29rmuUvt WIlMO+5p0utBwMwwmG2CthKWlz4xyNgzKxPkw= Received: by 10.213.34.79 with SMTP id k15mr13056223ebd.26.1288609622656; Mon, 01 Nov 2010 04:07:02 -0700 (PDT) Received: from nazgul.localnet (dustpuppy.is.co.za [196.14.169.11]) by mx.google.com with ESMTPS id v51sm4101608eeh.4.2010.11.01.04.07.01 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 01 Nov 2010 04:07:01 -0700 (PDT) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: When ls command fails but only on $HOME Date: Mon, 1 Nov 2010 13:07:34 +0200 User-Agent: KMail/1.13.5 (Linux/2.6.36-ck; KDE/4.5.2; x86_64; ; ) Cc: Harry Putnam References: <87pqupbaoe.fsf@newsguy.com> <201011011249.53945.alan.mckinnon@gmail.com> <87hbg1b9d5.fsf@newsguy.com> In-Reply-To: <87hbg1b9d5.fsf@newsguy.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201011011307.34534.alan.mckinnon@gmail.com> X-Archives-Salt: 17823218-4b83-4ee3-a391-4b3c1328e4cb X-Archives-Hash: 9c990f64fa0164acc282fd97a1a05e5b Apparently, though unproven, at 12:56 on Monday 01 November 2010, Harry Putnam did opine thusly: > Alan McKinnon writes: > > Apparently, though unproven, at 12:28 on Monday 01 November 2010, Harry > > Putnam > > > > did opine thusly: > >> Something I have not run into before. > >> > >> Following a major update still in progress I find the ls command will > >> not run on $HOME. > >> > >> I can view the directory with emacs in dired mode but `ls' simply will > >> not complete... never shows anything and stays hung indefinitely. > >> > >> Top shows 94% idle so its not from heavy system usage. > >> > >> The ls command seems to work anywhere else, and I see nothing peculiar > >> when viewing $HOME with emacs. > >> > >> Running `ls' from a root shell against my user $HOME, is the same story, > >> indefinite hang, nothing listed. > >> > >> I've let it run from both user and root shell for upwards of 1/2 hr. > >> Still just sets there. > >> > >> I've killed the terminal and restarted both user and root shells. But > >> still the same result... a `ls' against my user $HOME will just hang. > >> > >> In both root shell and user shell, once `ls' is run against my user > >> $HOME, the command hangs but also cannot by interrupted. Ctrl-c will > >> not stop it. > >> > >> It only seem to happen on $HOME.... how very odd. > >> Anyone else seen that or have an idea what might be the cause? > > > > By the time the command hits ls itself, the shell has already expanded > > the HOME variable. So it's unlikely to be the command and more something > > dodgy with your shell. > > > > What shell are you using? > > What is the output of "echo $HOME"? > > My shell is xterm... and was just updated to: > Wed Oct 27 10:15:06 2010 >>> x11-terms/xterm-262 That's the terminal. What shell do you use/ > > echo $HOME > /home/reader > > That recent update may be the problem. I'll back that out later to > see, but right now have a bigger and more urgent problem getting mail > back in order following a major update. -- alan dot mckinnon at gmail dot com