bash weirdness

[VirginSnow at vfemail.net]

> Date: Thu, 24 Jul 2008 18:44:28 -0400 (EDT)
> From: "John Abreau" <jabr at blu.org>

>     xlogo &
> 
> doesn't work; I get
> 
>     [1]+  Broken pipe             xlogo

That's what I was expecting would happen.

> When i login with tcsh instead of bash, I get a lot of broken pipes:
> 
>     ssh -t -Y server.example.com /bin/tcsh
>     Broken pipe

Does this happen when you ssh -t into a bash shell?

> So fork() is broken for users defined in LDAP, but not for users
> defined locally in /etc/passwd? I still can't imagine what could
> cause that behavior.

Are there any differences in the resource limits? try: ulimit -a

> Any thoughts on what I can try next?

I'd try running test commands non-interactively, i.e. from cron or ssh
without -t, and direct the results to a file.  That will tell you if
the terminal is having any effect.

After those tests, you can try trapping/stracing signals to see
exactly who's throwing that SIGPIPE.