FreeBSD and filePro weirdness

[Howard Wolowitz]

I ran into this problem when trying to test one of my cgi programs on a 
Linux box.  When I hit the break key during the debugger I ended up with 
both filepro and the shell accepting keystrokes.

The solution was to switch the script from using ksh to bash.

I know this tread is about FreeBSD but maybe switching the shell would help 
there too.

Howie

----- Original Message ----- 
From: "Brian K. White" <brian at aljex.com>
To: <filepro-list at lists.celestial.com>
Sent: Thursday, December 07, 2006 12:56 AM
Subject: Re: FreeBSD and filePro weirdness


>
> ----- Original Message ----- 
> From: "John Esak" <john at valar.com>
> To: "Filepro-List at Lists. Celestial. Com" 
> <filepro-list at lists.celestial.com>
> Sent: Wednesday, December 06, 2006 5:04 PM
> Subject: RE: FreeBSD and filePro weirdness
>
>> I can duplicate this behavior at will... It has happened since two 
>> changes
>> were made on my systems.
> ...
>> clear up the old filePro app. I have *never* seen this behavior until 
>> about
>> 6 months ago... when I did two things... put filePro 5.6 on the remote
>> system... which I am always accessing through FacetWin across a WAN. The
>> same version filePro accessed the same way on my LAN *never* exhibits 
>> this
>> behavior though.
>
> In our case I can pretty completely eliminate terminal emulator issues or 
> net connections.
> It happens on a variety of different emulators.
> (note: I haven't tried the console yet!)
> It happens on the wan (which is a T1 that has been solid for a couple 
> years.)
> It hppens on the other wan (which is verizon fios)
> It happens on the lan, and the lan uses a different nic and a different 
> switch than the wan.
>
> Besides, other machines share all the same net connections wan and lan, 
> and besides all that,
> The very same box, same fp binaries (5.0.14 linux in our case), same 
> termpcap, same everything but the data, processing & menus, doesn't have 
> the problem.
>
> It's a puzzle.
>
> Next thing I'm about to try right now atually, is putting a trap command 
> in the parent shell that tries to trap all signals and merely display the 
> signal it receives. This won't work for -9 but *shrug* what's left? 
> running the parent shell in strace? Or really the parent of that actually. 
> the instance of the shell that runs the script itself probably never knows 
> anything except it received signal or maybe not even that if it was a -9.
> But the parent of that might know something about why one of it's children 
> was killed.
>
> Brian K. White  --  brian at aljex.com  --  http://www.aljex.com/bkw/
> +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
> filePro  BBx    Linux  SCO  FreeBSD    #callahans  Satriani  Filk!
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>