[gentoo-user] When ls command fails but only on $HOME

[gentoo-user] When ls command fails but only on $HOME

[Harry Putnam]

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?

Re: [gentoo-user] When ls command fails but only on $HOME

[Alan McKinnon]

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"?


-- 
alan dot mckinnon at gmail dot com

[gentoo-user] Re: When ls command fails but only on $HOME

[Harry Putnam]

Alan McKinnon <alan.mckinnon@gmail.com> 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

 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.

Re: [gentoo-user] Re: When ls command fails but only on $HOME

[Alan McKinnon]

Apparently, though unproven, at 12:56 on Monday 01 November 2010, Harry Putnam 
did opine thusly:

> Alan McKinnon <alan.mckinnon@gmail.com> 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

Re: [gentoo-user] Re: When ls command fails but only on $HOME

[Willie Wong]

On Mon, Nov 01, 2010 at 01:07:34PM +0200, Alan McKinnon wrote:
> > >> Something I have not run into before.
> > >> 
> > >> Following a major update still in progress I find the ls command will
> > >> not run on $HOME.
> > >> 
> > > 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

Before we go further, when you said `ls' will not complete against
$HOME, which of the following scenario did you mean?

  a)  you typed `ls $HOME' as a user  (the one I think Alan thinks you
mean)
  b)  you type `ls' while in your home directory (/home/reader)
  c)  you typed `ls /home/reader' ?

W
-- 
Willie W. Wong                                     wwong@math.princeton.edu
Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire 
         et vice versa   ~~~  I. Newton

[gentoo-user] Re: When ls command fails but only on $HOME

[Harry Putnam]

Alan McKinnon <alan.mckinnon@gmail.com> writes:


[...]

>> > 
>> > 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/
>

Sorry... still asleep... bash-4.1_p9


Willie Wong <wwong@Math.Princeton.EDU> writes:

[...]

> Before we go further, when you said `ls' will not complete against
> $HOME, which of the following scenario did you mean?
>
>   a)  you typed `ls $HOME' as a user  (the one I think Alan thinks you
> mean)
>   b)  you type `ls' while in your home directory (/home/reader)
>   c)  you typed `ls /home/reader' ?

All three of those produce the same effect.  Also if run from root
shell against my users home `# ls /home/reader'

The command just hangs there as described.

However, as indicated earlier... my user or root can run `ls' against
any other directory like normal.

  ls /etc

Shows the content of /etc

  ls /home/reader

Hangs eternally.

Also, as mentioned, I can view /home/reader with emacs in dired
(directory) mode, Which oddly enough uses ls and ls switches for that
display far as I know. 

However, vim will not display /home/reader... and
hangs eternally... requiring the shell to be killed.

Viewing $HOME with emacs shows nothing untoward that I see.  I thought
maybe I'd somehow acquired thousands of files and `ls' was just taking
forever to display the list... but no... nothing unusual in $HOME.

Re: [gentoo-user] Re: When ls command fails but only on $HOME

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 446 bytes --]

On Mon, 01 Nov 2010 07:51:50 -0500, Harry Putnam wrote:

> However, as indicated earlier... my user or root can run `ls' against
> any other directory like normal.
> 
>   ls /etc
> 
> Shows the content of /etc
> 
>   ls /home/reader

What about ls /home/reader/somedir ?


-- 
Neil Bothwick

A friend of mine sent me a postcard with a satellite photo of the
entire planet on it, and on the back he wrote, "Wish you were here."

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: When ls command fails but only on $HOME

[Alan McKinnon]

Apparently, though unproven, at 14:51 on Monday 01 November 2010, Harry Putnam 
did opine thusly:

> Alan McKinnon <alan.mckinnon@gmail.com> writes:
> 
> 
> [...]
> 
> >> > 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/
> 
> Sorry... still asleep... bash-4.1_p9
> 
> 
> Willie Wong <wwong@Math.Princeton.EDU> writes:
> 
> [...]
> 
> > Before we go further, when you said `ls' will not complete against
> > $HOME, which of the following scenario did you mean?
> > 
> >   a)  you typed `ls $HOME' as a user  (the one I think Alan thinks you
> > 
> > mean)
> > 
> >   b)  you type `ls' while in your home directory (/home/reader)
> >   c)  you typed `ls /home/reader' ?
> 
> All three of those produce the same effect.  Also if run from root
> shell against my users home `# ls /home/reader'
> 
> The command just hangs there as described.
> 
> However, as indicated earlier... my user or root can run `ls' against
> any other directory like normal.
> 
>   ls /etc
> 
> Shows the content of /etc
> 
>   ls /home/reader
> 
> Hangs eternally.
> 
> Also, as mentioned, I can view /home/reader with emacs in dired
> (directory) mode, Which oddly enough uses ls and ls switches for that
> display far as I know.
> 
> However, vim will not display /home/reader... and
> hangs eternally... requiring the shell to be killed.
> 
> Viewing $HOME with emacs shows nothing untoward that I see.  I thought
> maybe I'd somehow acquired thousands of files and `ls' was just taking
> forever to display the list... but no... nothing unusual in $HOME.


I suspect directory corruption in /home - is it a separate partition?

I don't recall if you mentioned this or not, do you get the same result if you 
run "ls $HOME" as root? root's home dir is not on /home so that will vbe a 
valuable clue. If that command works, do an fsck on /home


-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] Re: When ls command fails but only on $HOME

[alex]

[-- Attachment #1: Type: text/plain, Size: 2838 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 01.11.2010 14:13, schrieb Alan McKinnon:
> Apparently, though unproven, at 14:51 on Monday 01 November 2010, Harry Putnam 
> did opine thusly:
> 
>> Alan McKinnon <alan.mckinnon@gmail.com> writes:
>>
>>
>> [...]
>>
>>>>> 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/
>>
>> Sorry... still asleep... bash-4.1_p9
>>
>>
>> Willie Wong <wwong@Math.Princeton.EDU> writes:
>>
>> [...]
>>
>>> Before we go further, when you said `ls' will not complete against
>>> $HOME, which of the following scenario did you mean?
>>>
>>>   a)  you typed `ls $HOME' as a user  (the one I think Alan thinks you
>>>
>>> mean)
>>>
>>>   b)  you type `ls' while in your home directory (/home/reader)
>>>   c)  you typed `ls /home/reader' ?
>>
>> All three of those produce the same effect.  Also if run from root
>> shell against my users home `# ls /home/reader'
>>
>> The command just hangs there as described.
>>
>> However, as indicated earlier... my user or root can run `ls' against
>> any other directory like normal.
>>
>>   ls /etc
>>
>> Shows the content of /etc
>>
>>   ls /home/reader
>>
>> Hangs eternally.
>>
>> Also, as mentioned, I can view /home/reader with emacs in dired
>> (directory) mode, Which oddly enough uses ls and ls switches for that
>> display far as I know.
>>
>> However, vim will not display /home/reader... and
>> hangs eternally... requiring the shell to be killed.
>>
>> Viewing $HOME with emacs shows nothing untoward that I see.  I thought
>> maybe I'd somehow acquired thousands of files and `ls' was just taking
>> forever to display the list... but no... nothing unusual in $HOME.
> 
> 
> I suspect directory corruption in /home - is it a separate partition?
> 
> I don't recall if you mentioned this or not, do you get the same result if you 
> run "ls $HOME" as root? root's home dir is not on /home so that will vbe a 
> valuable clue. If that command works, do an fsck on /home
> 
> 
Could also some problem with the inodes, could't?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJMzsDmAAoJEB8n+SuWCkjvtl0H/3Ex2l3razqJiXXV8BTUJSt6
6IxjvQ12e48vj6ED8vJ083LEEotGswTTzODHHdJApGoSgp8msCodSyjudscLNJRJ
8cpdGWOsIV8paLUfSkDXZConLdpfJp1fgTiupGrkXdCfW2jKM1R2K1dC7uPr+wXf
nZtgaXGBw7Ao04mlgPNgXYXlN2V9JsWelc1AJhWBoCocopJj/eEeaHSCrLFzhInF
Sm5GjVRaIEGKbplzi5mBgOgvQ756nCeAzjXM/Va5obvIrwbnGNd9VEJQ+WnJGCKT
lFcfmRGorPPPYktvQTM3BiZf6Fs23C0ude+lZBgt4I+HtCyKrYHANLFrx1WBC3s=
=IKBq
-----END PGP SIGNATURE-----


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3656 bytes --]

Re: [gentoo-user] Re: When ls command fails but only on $HOME

[Alan McKinnon]

Apparently, though unproven, at 15:30 on Monday 01 November 2010, alex did 
opine thusly:

> > I suspect directory corruption in /home - is it a separate partition?
> > 
> > I don't recall if you mentioned this or not, do you get the same result
> > if you run "ls $HOME" as root? root's home dir is not on /home so that
> > will vbe a valuable clue. If that command works, do an fsck on /home
> 
> Could also some problem with the inodes, could't?

Yes. Doesn't matter if it's inodes or blocks, it's still corruption. 
inodes are just blocks that the fs drivers understands to treat specially.
-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] Re: When ls command fails but only on $HOME

[covici]

Harry Putnam <reader@newsguy.com> wrote:

> Alan McKinnon <alan.mckinnon@gmail.com> 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
> 
>  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.
Sendmail will reject if the load is high enough.  This can be adjusted
and if your load is 12, this is probably the problem.  Also, make sure
the daemon is running -- you should have two daemons, the mta and the
other one (mssp) I think which reads the mclient-queue.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] When ls command fails but only on $HOME

[Alex Schuster]

Am 01.11.2010 11:28, schrieb Harry Putnam:

> I can view the directory with emacs in dired mode but `ls' simply will
> not complete... never shows anything and stays hung indefinitely.
[...]
> It only seem to happen on $HOME.... how very odd.
> Anyone else seen that or have an idea what might be the cause?

No. But maybe 'strace ls' will show something?

Is /home on a separate partition? I'd do a fsck on it. touch /forcefsck
or use a live cd for this. Good luck,

	Wonko

[gentoo-user] Re: When ls command fails but only on $HOME

[Harry Putnam]

Alex Schuster <wonko@wonkology.org> writes:

> Am 01.11.2010 11:28, schrieb Harry Putnam:
>
>> I can view the directory with emacs in dired mode but `ls' simply will
>> not complete... never shows anything and stays hung indefinitely.
> [...]
>> It only seem to happen on $HOME.... how very odd.
>> Anyone else seen that or have an idea what might be the cause?
>
> No. But maybe 'strace ls' will show something?
>
> Is /home on a separate partition? I'd do a fsck on it. touch /forcefsck
> or use a live cd for this. Good luck,

Just to close this thread... a reboot swept away all `ls' problems so
still not sure what caused it, but am happily having normal experience
with `ls' once again.

The reboot was strictly unplanned, as the machine locked up
overnight... no console access or by ssh, resulting in a hard manual
reboot.

When the machine came up, the `ls' problem had disappeared as well as
sendmail problems discussed in a different thread.

Thank you all for input and suggestions

[gentoo-user] Re: When ls command fails but only on $HOME

[Grant Edwards]

On 2010-11-05, Harry Putnam <reader@newsguy.com> wrote:
> Alex Schuster <wonko@wonkology.org> writes:
>
>> Am 01.11.2010 11:28, schrieb Harry Putnam:
>>
>>> I can view the directory with emacs in dired mode but `ls' simply will
>>> not complete... never shows anything and stays hung indefinitely.
>> [...]
>>> It only seem to happen on $HOME.... how very odd.
>>> Anyone else seen that or have an idea what might be the cause?
>>
>> No. But maybe 'strace ls' will show something?
>>
>> Is /home on a separate partition? I'd do a fsck on it. touch /forcefsck
>> or use a live cd for this. Good luck,
>
> Just to close this thread... a reboot swept away all `ls' problems so
> still not sure what caused it, but am happily having normal experience
> with `ls' once again.
>
> The reboot was strictly unplanned, as the machine locked up
> overnight... no console access or by ssh, resulting in a hard manual
> reboot.
>
> When the machine came up, the `ls' problem had disappeared as well as
> sendmail problems discussed in a different thread.

It sounds to me like you've got hardware problems.  I'd at least run
memtest86 overnight if I were you.

-- 
Grant Edwards               grant.b.edwards        Yow! I feel partially
                                  at               hydrogenated!
                              gmail.com            

Re: [gentoo-user] Re: When ls command fails but only on $HOME

[Indexer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Another thing to check, is that the folder is marked +x in chmod. It may be that on reboot some automated cleaning script re-added that flag.

Folders can only be listed if they are +x btw

On 06/11/2010, at 01:37, Grant Edwards wrote:

> On 2010-11-05, Harry Putnam <reader@newsguy.com> wrote:
>> Alex Schuster <wonko@wonkology.org> writes:
>> 
>>> Am 01.11.2010 11:28, schrieb Harry Putnam:
>>> 
>>>> I can view the directory with emacs in dired mode but `ls' simply will
>>>> not complete... never shows anything and stays hung indefinitely.
>>> [...]
>>>> It only seem to happen on $HOME.... how very odd.
>>>> Anyone else seen that or have an idea what might be the cause?
>>> 
>>> No. But maybe 'strace ls' will show something?
>>> 
>>> Is /home on a separate partition? I'd do a fsck on it. touch /forcefsck
>>> or use a live cd for this. Good luck,
>> 
>> Just to close this thread... a reboot swept away all `ls' problems so
>> still not sure what caused it, but am happily having normal experience
>> with `ls' once again.
>> 
>> The reboot was strictly unplanned, as the machine locked up
>> overnight... no console access or by ssh, resulting in a hard manual
>> reboot.
>> 
>> When the machine came up, the `ls' problem had disappeared as well as
>> sendmail problems discussed in a different thread.
> 
> It sounds to me like you've got hardware problems.  I'd at least run
> memtest86 overnight if I were you.
> 
> -- 
> Grant Edwards               grant.b.edwards        Yow! I feel partially
>                                  at               hydrogenated!
>                              gmail.com            
> 
> 

William Brown

pgp.mit.edu



-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)

iQIcBAEBAgAGBQJM1JirAAoJEHF16AnLoz6J9JgP/1JkcLdsdqsDAgt3IJE/BDhz
S3/8e7IghJ75t/fPMoVqZKrgDt264hx6Paj5Qr4HLeEVNlFVV6Xm4+AjsHauHbZa
P8qoFkE7G/yAsCXxwFQG4LGUOSHL6uRj3MZX1lJTQiN9h4qNqnl1rkwl045YLEdY
ZXcIwqebwbtfGPDWFqbWeam4Dd14G/F2l/IxfiOZwD6G9Qcm9B1d8gZt3HnsvbAx
GnQTSEG0KAa/e3XPV2V8Z+V9MNeJ+rForBtvAy5QRmk3cRMxdEF6AGkTmEyYwnUB
SVoocBmtdxSMw3IZETpkW8r0Hq78OJMjzszrHrs6cVFVlNZHMh1aCkpuBh7hNz4K
fQORkPoeHrgxzkwEq30RLlADY+PMn10hGBEfhZuI3VSBtUqv6yY4eNO7kAF3az2R
MDE9W+ek8D4RDAjXZq/zdogg6WYN2Qi3fpRqpnE1iCsh4eWkQElUQ1BtoPh876wK
6o7MvGKB389DvG6Snsrjs+A/XaNayIL0zR4dtdwdNXFN6tdmNyVhaGdhE3J/OuKK
9bfXiDybdwr/JoAhw0UZCpv5ZiS/+8n7KuENUpLUzVSoAUl5S1FAF75AsKgf8mzZ
Zz3ofz3d8BG2+pBcxSJtgLOrsPC2xwd2yyWzfP68HC39sb5WDgvH4Zocnzr9d5rL
bF7chWDhEaVWePnchRf6
=3ufH
-----END PGP SIGNATURE-----

Re: [gentoo-user] Re: When ls command fails but only on $HOME

[Alex Schuster]

Indexer writes:

> Another thing to check, is that the folder is marked +x in chmod.
> It may be that on reboot some automated cleaning script re-added
> that flag.
> 
> Folders can only be listed if they are +x btw

Right, but Harry would have gotten a permission denied error in this
case, not a hanging ls process.

	Alex

Re: [gentoo-user] Re: When ls command fails but only on $HOME

[Enrico Weigelt]

* Harry Putnam <reader@newsguy.com> wrote:

> Just to close this thread... a reboot swept away all `ls' problems so
> still not sure what caused it, but am happily having normal experience
> with `ls' once again.

Might well be that the reboot caused an fsck run, which fixed
the problems.


cu
-- 
----------------------------------------------------------------------
 Enrico Weigelt, metux IT service -- http://www.metux.de/

 phone:  +49 36207 519931  email: weigelt@metux.de
 mobile: +49 151 27565287  icq:   210169427         skype: nekrad666
----------------------------------------------------------------------
 Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
----------------------------------------------------------------------