TID: FMail-lnx64 2.1.5.1-B20230107
RFC-X-No-Archive: Yes
TZUTC: 0100
CHRS: UTF-8 2
PID: GED+LNX 1.1.5-b20161221
MSGID: 2:280/464 63c01aa0
REPLY: 1:105/10 63c00f0a
Hi Rick,

On 2023-01-12 05:44:34, you wrote to me:

 WV>>>>>> {
 WV>>>>>>   echo "processsing"
 WV>>>>>>   echo "PATH = $PATH";
 WV>>>>>>   echo "SHELL = $SHELL";
 WV>>>>>>   /usr/local/bin/hpt toss

 WV>>>>>> } >/tmp/test.txt 2>&1

 WV>>>>>> So you can see everything that is written to stdout and stderr

 RS>>>>> I am giving this a go thankyou... Where will I see the errors
 RS>>>>> from it?  I am unfamiliar with stdout and stderr..

 WV>>>> It is what the software normally outputs to the console screen
 WV>>>> (normal and errors). It's now redirected to the /tmp/test.txt
 WV>>>> file...

 RS>>> ok, still not tossing but now the test.txt isnt being created
 RS>>> with the script above that you suggested?

 WV>> Does it work on the commandline, and creating the /tmp/test.txt file?

 RS> works fine on command line.. I noticed that it ran last night at
 RS> midnight on one packet but /in was still full of pkts... Crazy

And what was in the /tmp/test.txt file after it ran?

And you should probably change the > to >> so the output of previous runs
don't get overwritten. And change the 'echo "processing"' to 'date +"%F
%T%tprocessing"', so you can put a timestamp on when things are happening.


Bye, Wilfred.

--- FMail-lnx64 2.1.5.1-B20230107
 * Origin: FMail development HQ (2:280/464)
SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 114/705 709 120/340
SEEN-BY: 123/120 131 124/5016 129/305 153/757 7715 154/10 203/0 218/700
SEEN-BY: 218/840 220/70 221/0 226/17 30 227/114 229/110 111 112 113
SEEN-BY: 229/114 200 206 307 317 424 426 428 470 550 664 700 240/1120
SEEN-BY: 240/5832 250/5 8 266/512 267/800 280/464 5003 5555 282/1038
SEEN-BY: 292/854 8125 298/25 301/1 305/3 310/31 317/3 320/219 322/757
SEEN-BY: 341/66 234 342/200 396/45 423/120 460/58 633/280 712/848
SEEN-BY: 770/1 100 340 772/210 220 230
PATH: 280/464 770/1 317/3 229/426