REPLY: 2:280/464.112 63bfb502
MSGID: 1:105/10 63c00f0a
CHRS: UTF-8 2
TZUTC: -0800
Greetings Wilfred!

Thursday January 12 2023 08:18, you wrote to me about an urgent matter!:

 WV>  * Forwarded from area 'BINKD'
 WV> Hi Rick,

 WV> On 11 Jan 23 20:06, Rick Smith wrote to Wilfred van Velzen:
 WV>   about: "still not tossing":


 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> You don't quote the first line:

 WV> #!/bin/bash

 WV> Did you include that in the script?

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


 WV> Wilfred.

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


----
Regards,


 Rick Smith (Nitro)

... YKYHW: You consider BBSing better than chocolate.
--- GoldED+/LNX 1.1.5-b20220504
 * Origin:  ----> Abacus BBS! --->>>>bbs.abon.us:2323  (1:105/10)
SEEN-BY: 1/123 15/0 90/1 105/7 10 11 81 85 500 106/201 114/709 120/340
SEEN-BY: 123/131 129/305 153/7715 218/700 226/30 227/114 229/110 111
SEEN-BY: 229/112 113 114 200 206 307 317 424 426 428 470 550 664 700
SEEN-BY: 266/512 282/1038 292/854 317/3 320/219 322/757 342/200 396/45
SEEN-BY: 633/280 712/848
PATH: 105/10 81 229/426