Subj : bbs shut down http log
To   : Deuce
From : DieselMan
Date : Tue Jun 28 2005 03:24 am

  Re: bbs shut down http log
  By: Deuce to DieselMan on Mon Jun 27 2005 04:06 pm

 >   Re: bbs shut down http log
 >   By: DieselMan to All on Mon Jun 27 2005 04:17:00
 > 
 >  > for you that know what you are looking for at approx 2:39 the system was 
 >  > for lack of a better word or caused to crash by a buffer overload or what
 >  > I'm a mechanic not an computer expert at all. I assure you i am sober and
 >  > watched it with my own eyes
 > 
 > I suspect your terminals answerback string was sent to sbbs because of a
 > character in a bit of logged console data.
 > 
 > specifically, the UNKNOWN USER bit.
 > 
 > Here's how it happened:
 > 1) You were running sbbs in foreground mode from a console that honours the
 > answerback string
 > 2) An ASCII 5 was sent to the log output which happened to be your terminal.
 > 3) Your terminal returned with an id string that contained at LEAST the char
 > , x, and t in that order.
 > 4) This was sent out by the terminal and therefore recieved by sbbs proper.
 > 5) The t caused termination.
 > 
 > workaround: Run as a daemon, or use a terminal that does nto send an answerb
 > string.
 > 

Very Sharp! 

when i tried the same command $'\005' under rxvt it returned bash: : command
not found. And some character's before and after prompt. hit return again and a
regular prompt. Then I brought up the bbs. and it's running well so far for 12
or so hours
Being new to linux and also running a pre-release. i didn't know what was
happeneing. hell the first time i saw it. i partitioned my disk and
reinstalled the OS figuring someone had gained access and no telling what they
may have done :) 

thanks again very much!

       Have a great day,
       DieselMan

---
 þ Synchronet þ There Is A Solutionhttp://thesolution.homelinux.org

.