[lug] ls killing ssh

[Michael Wegener]

I tried both, and can see things just fine. In fact, I can now use ls with
impunity w/o problem. May have to do with rebooting, because I stupidly
killed all the sshd processes (oops) when the machine is in colo and had to
wait for normal tech support to come in and reboot it. The mystery remains
unsolved

-----Original Message-----
From: lug-bounces at lug.boulder.co.us
[mailto:lug-bounces at lug.boulder.co.us]On Behalf Of Joseph McDonald
Sent: Friday, January 23, 2004 12:36 AM
To: Boulder (Colorado) Linux Users Group -- General Mailing List
Subject: Re: [lug] ls killing ssh



On Thu, Jan 22, 2004 at 11:46:19PM -0700, John Hernandez wrote:
> Michael Wegener wrote:
>
> >I have a machine that when you ls in /etc/init.d, it kills ssh. This
> >seems a tad weird, but it's very consistent. Of course, I can't be
> >sure I see what may be causing this unless I get on a console, but an
> >"ls l" stops at httpd. The sshd process keeps running, but not ls, and
> >the terminal stops responding. I've also seen this using another ssh
> >interface, so I don't think it's PuTTY which I'm using when I see
> >this. Any ideas what would cause this?
>
> Perhaps a non-graphic character embedded in a filename?  What happens if
> you run 'ls -lb' instead?

Yea, or what happens if you run find /etc/init.d/

_______________________________________________
Web Page:  http://lug.boulder.co.us
Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
Join us on IRC: lug.boulder.co.us port=6667 channel=#colug

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.560 / Virus Database: 352 - Release Date: 1/8/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.560 / Virus Database: 352 - Release Date: 1/8/2004