Hello Joseph!

21 Nov 16, Joseph Larsen wrote to Jeff Smith:

 JS>> session completed? Here mail is tossed when the mail session is
 JS>> completed regar how many mail files have been received using the
 JS>> EXEC command in BinkD config file.

 JL> When a packet/bundle is received. Only then will it toss.

 JL> The problem is that HPT is doing absolutely nothing. Even when I
 JL> invoke it manually.

Without a new packet/bundle, what should hpt do?
I don't understand your problem exactly.

There are two ways for binkd process workflow control. External by flag
file or directly by binkd with the exec command.

The exec command allows via the "!" parameter the immediate start
after receiving a file. That one was build in for request processors with
SRIF standard but can be used for other things too.

# Run an external program.
# The "*S" macro in command line substed with S.R.I.F., see !SRIF.TXT
# The "!" before program pathname means immediate program execution
#   after receiving the file.
#exec "my-freq-processor.exe /options *S" *.req
#exec "my-pkt-unpacker.exe /options *S" *.pkt

If you use that exec for starting hpt, the ! may be what you are searching for.


With the flagfile workflow control binkd creates flagfiles like

# Create a flag file after receiving a file
#
flag .../flags/do.toss *.pkt *.mo?  ...

Those flagfiles are created at the end of the session:

- 09:19 [16069] receiving NEW.mo0 (2378 byte(s), off 0)
+ 09:19 [16069] NEW.mo0 -> /inbound/NEW.mo0
  09:19 [16069] got *.mo?, delayed creating /flags/do.toss
+ 09:19 [16069] rcvd: NEW.mo0 (2378, 2378.00 CPS, nodeaka)
+ 09:19 [16069] done (from nodeaka, OK, S/R: 0/1 (0/2378 bytes))
  09:19 [16069] Creating /flags/do.toss

Now this flagfile can be used to start the tosser by an external script or
daemon tool. A script could be started by a cronjob every x minutes.

It doesn't have to check for the do.toss flagfile if it forces the tosser
run. Then you may have empty logfile entries and system load for nothing.
If you check for the do.toss flagfile don't forget to let your script
delete it.

It's a good idea to have the script check for the mailers busy flagfiles
and do not start the tosser if the mailer is still busy.

I don't remember the exact names for the busy files, they end with *.bsy
and will be deleted normally after the sessions ends. You may adjust your
loglevel to find the correct filenames.

# Path and name for the logfile, loglevel (1-10)
#
log /binkd.log
loglevel 4
#loglevel 10

#
# Uncomment it if you want binkd's log at your console
#
conlog 4
#conlog 10


Regards

Kai

--- GoldED+/LNX 1.1.4.7