On Thursday 05 February 2009 16:42:48 Randall R Schulz wrote:
On Thursday February 5 2009, Anders Johansson wrote:
On Thursday 05 February 2009 16:23:24 Jan Karjalainen wrote:
On Thu, Feb 5, 2009 at 16:14, Anders Johansson wrote:
On Thursday 05 February 2009 16:09:45 Jan Karjalainen wrote:
But the original problem still exists, I can't make a "ls -a /home/jan" without hanging the console...
That is stranger.
Can you do "strace ls -a /home/jan" and see where it hangs?
Anders
Hm, that doesn't seem to show a hang. It seems to be exiting normally
My first thought was "exit hung?"
Na, strace gives that output on my system too, and ls doesn't hang here.
Perhaps the place to look is in what BASH is doing after the child process exits. E.g., that "command_not_found_handle" business (presumably not relevant here, since the command _was_ found) or PROMPT_COMMAND, or even something it does apart from user-configurable options or parameters?
I don't think that would be affected by an strace. The main difference between running with strace and without it, is that strace messes with interrupts. I'm not 100% sure how that plays in here though I'd bugzilla it Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org