| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | busyflag problem |
I've run across a peculiar behaviour from squish with regard to busyflags (see below). Let's say I am sending a lot of mail to Node A. Node B calls on another line and drops off a lot of mail Squish starts processing the mail and puts any mail for Node A into outbound.sq as a single .OUT file. This .OUT file can be up to 10 Mb On the next squish pass, when Node A is no longer .BSY, squish packs up this .OUT file as 1 large packet and compresses it, Totally ignoring the squish.cfg settings limiting maxmsg and maxpkt. Normally maxmsg limits the size of a packet (which is good) but in this circumstance it is ignored (this is BAD). Is it supposed to work this way? here is the squish command: c:\max\squishp in out squash link -f\max\echotoss.log -q from squish.cfg: ; The MaxMsgs keyword instructs Squish to create a new set of outbound packets after processing every messages. MaxMsgs 50 ;The MaxPkt keyword informs Squish that there may be up to packets queued in the OUTBOUND.SQ directory. MaxPkt 256 ; specifies the approximate size, in kilobytes, of the largest ARCmail file that Squish should create. Maxarchive 100 From squish/2 v1.11 docs BusyFlags Squish has full support for the busy flag mechanism. To further help throughput, Squish also performs most of its operations in a separate holding directory, outside of the main zoned outbound directories. Files are only transferred to the outbound directories as necessary, which minimizes the "down time" for any given node. In addition, if Squish attempts to send mail to a node which is busy due to mailer activity on another line, the packet will be simply queued for later use, as opposed to waiting for that node to become free again. Unlike other mail processors, this means that Squish never has to wait because of mail activity occurring on other lines of a multi-line system, which makes Squish the ideal choice for a multi-line installation. When using BinkleyTerm, make sure to turn on busy flag support by enabling the "Flags" directory and setting a non-zero task number. --- Maximus/2 2.02* Origin: StarStream BBS: Kingston ON/CAN 613-546-6403 V.34/V.FC (1:249/112) SEEN-BY: 50/99 249/99 100 104 106 112 201 254/1 620/243 623/630 625/100 SEEN-BY: 626/660 632/348 640/205 206 230 297 305 702 820 821 822 823 649/312 SEEN-BY: 690/660 711/409 413 430 808 809 934 949 955 712/515 713/888 714/906 SEEN-BY: 800/1 @PATH: 249/112 99 106 640/206 820 711/409 808 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.