Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to General discussion on Husky Soft...  <--  <--- Return to Home Page
   Networked Database  General discussion on Husky Soft...   [98 / 150] RSS
 From   To   Subject   Date/Time 
Message   Nicholas Boel    All   Question..   December 15, 2016
 9:03 AM *  

Hello All,

On 14 Dec 16 09:48, Nicholas Boel wrote to All:

 NB> Just have a couple questions regarding some configuration options in
 NB> fidoconfig:

 NB> 1) When using "hpt pack" sometimes it seems to mark recently written
 NB> echomail messages with the "Snt" flag, whether or not
 NB> "PackNetmailOnScan" is set anywhere (even though that would be reverse
 NB> from what seems to be happening here, so shouldn't matter anyways).

This is still puzzling to me, but..

 NB> 2) ProcessPkt - Can (or should) this be used for processing Filefix
 NB> requests? As of right now, I have a script executed from binkd called
 NB> poll.sh that runs:

 NB> /usr/local/bin/hpt toss link
 NB> /usr/local/bin/hpt ffix!
 NB> /usr/local/bin/hpt pack

I have shortened this process by using "/usr/local/bin/hpt scan -f" together
with "PackNetmailOnScan yes" in my config. At least now if echoscan.log (what I
 use for "echotosslog", since it's actually misrepresented. "importlog" should
be echotoss.log) is not there it will stop and do nothing.

 NB> Which seems to work fine, but if ProcessPkt can be used to run
 NB> "/usr/local/bin/hpt ffix!" I may not need it in my polling script, and
 NB> could just run "hpt toss link" directly.

Still wonder if this is a possibility.

 NB> Also, feature request: When "hpt ffix[!]" actually does process a
 NB> filefix request, can we have an option to automatically pack the
 NB> netmail replies? This would save time and resources on running "hpt
 NB> pack" every time when it is not needed most of the time. This would or
 NB> could somewhat mimic the "Areafix requests on the fly" method.
 NB> htick.texi seems to say "Filefix requests on the fly" but the same
 NB> options areafix has are not available for filefix (ie: AreafixFromPkt
 NB> is available, while FilefixFromPkt is not an option).

 NB> With the feature request, then the need/want for ProcessPkt wouldn't
 NB> be necessary.

 NB> Thank you in advance.

I'm going to assume this echo is more or less the Z1 version; with a couple of
courageous Z2 fellas connected to it, as I've seen cross posts to other echos
regarding the Husky software. If someone has a link to the others, I'm
interested in receiving them as well.

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20160827
 * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to General discussion on Husky Soft...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0807 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_cqjqvslt2mpf1hpplt3b6vrbv4, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_cqjqvslt2mpf1hpplt3b6vrbv4, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_cqjqvslt2mpf1hpplt3b6vrbv4, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0