Bash not responding after running ping or piping something to more HELP?

[jat190]

I'm serial'd in and tried running a ping command "ping 10.10.10.1". After running that, nothing happens. I don't get a prompt back or failure. I can type, but I can't break out of this state.
Tried CTRL-C, ctrl-d,ctrl-z,exit,quit

excerpt
************
bash-2.02# ping 10.10.10.1
PING 10.10.10.1 (10.10.10.1): 56 data bytes


************

If I reboot, I can get out, but I'd rather not do that.
The same thing happened to me when I tried to cat a file and pipe it to more.

cat rc.sysinit.author |more

Any ideas?

[PlainBill]

The first idea I had was to flame you. Instead I will point out that you have not given us any useful information, thus it is almost impossible to help you. About all I can suggest is to restore a known good image to the drive, hack it, and see if the problem persists.

PlainBill

[Jamie]

... I can't break out of this state.
Tried CTRL-C, ctrl-d,ctrl-z,exit,quitI'm not sure this is your issue, but you might look at using setsid (http://www.dealdatabase.com/forum/showthread.php?p=189425&highlight=setsid#post189425) when starting your serial bash if you are having trouble getting control keys to work to interrupt processes.

[ljvk61]

In addition to Jamie's suggestion, if you have telnet working at the same time, you can kill the offending process. However, if it is tivosh , you will reboot anyhow with many software versions (Wish they'd implement the up arrow history in tivosh. I've been bitten too many times).