shell's command line locks after commands like ls

tree_buddy · 09-08-2003, 07:08 PM

I have been watching how the stuff that would clog the processor, but the thing is that I am basically the only user. My wife may hit up the internet once and a while, but never using mem/processor guzzling programs.
I am running everything out the company that I work for, could they have some sort of restrictions that would affect what I'm doing?

unSpawn · 09-09-2003, 04:41 AM

IMHO by now posting your
- system HW details,
- sshd_config, ssh_config, and Putty cfg,
- output from running (a separate!) sshd as "sshd <any options> -d -d -d2>&1|tee /tmp/sshd_log" and connecting to it with "ssh <anyoptions> -v -v -v" (try running something like "strace -v /bin/ls <problemdir>"),
- output of a local strace of "ls",
and your firewall script, and maybe some traceroutes between host and client could be helpful...

tree_buddy · 09-15-2003, 10:52 AM

guess what, because I was running the client on a secure "business" network, everything was screwy. After accessing everything from another terminal, I was able to do everything fine.
Maybe the network people here at work saw what I was doing and started blocking my IP ?!