Subj : All looks good, but...
To   : Angus Mcleod
From : Digital Man
Date : Mon Jan 03 2005 06:19 pm

  Re: All looks good, but...
  By: Angus Mcleod to Digital Man on Tue Jan 04 2005 01:44 am

 >   Re: All looks good, but...
 >   By: Digital Man to Angus Mcleod on Mon Jan 03 2005 15:39:00
 > 
 >  >  >   evnt QNET-FTP: VERT dove.synchro.net XXXXXXXX
 >  >  >   evnt QNET-FTP: /sbbs/data/VERT.rep size 1009
 >  >  >   evnt QNET-FTP: REP size exceeds 500!
 >  >  >   evnt QNET-FTP: Aborting... No transfer.
 >  >  >   evnt QNET-FTP: Done.
 >  >  >
 >  >  > Seems to be OK!  :-)  Now to set MAX_REPSIZE back up so I can get this
 >  >  > out.  I suppose the ideal size would vary from board to board...
 >  >
 >  > What's it do with the REP file in this case? Just keep appending to it?
 > 
 > It does nothing with it; it just aborts the script.  I presume that just
 > leaves it there.  Subsequent calls will cause it to get bigger, but the
 > SysOp can override the MAX_REPSIZE and recompile if he wants it to go, or
 > delete the packet if it is in fact 36 meg of dups.
 > 
 > I suppose it would be good if it sent a telegrap/message to the SysOp when
 > it aborted, rather than just dropping a line in the logfile.  Is there a
 > BAJA verb to do that?  

There's no specific function to do that in Baja, no. It could create/append the
data/msgs/0001.msg file though.

 > Can't remember -- will check.  Also, there
 > should be an easy way to set LIMIT_REPSIZE off without recompiling, in the
 > event you sometime get an unusually large, but still legitimate packet.

Yeah, via the command-line. :-)

                                                  digital man

Snapple "Real Fact" #2:
Animals that lay eggs dont have belly buttons.

.