Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 8274  |
|  Rick Smith to Wilfred van Velzen  |
|  still not tossing  |
|  11 Jan 23 20:06:38  |
 
REPLY: 2:280/464.112 63bc03b3
MSGID: 1:105/10 63bf8785
CHRS: UTF-8 2
TZUTC: -0800
Greetings Wilfred!
Monday January 09 2023 13:07, you wrote to me about an urgent matter!:
WV> * Forwarded from area 'BINKD'
WV> Hi Rick,
WV> On 08 Jan 23 15:02, Rick Smith wrote to Wilfred van Velzen:
WV> about: "still not tossing":
RS>>>> rick@abacus:~$ cat /usr/local/bin/mail-toss.sh
RS>>>> #!/bin/bash
RS>>>> echo "processsing" > /tmp/test.txt
RS>>>> echo "PATH = $PATH";
RS>>>> echo "SHELL = $SHELL";
RS>>>> /usr/local/bin/hpt toss
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 (normal
WV> and errors). It's now redirected to the /tmp/test.txt file...
WV> Wilfred.
ok, still not tossing but now the test.txt isnt being created with the script
above that you suggested?
----
Regards,
Rick Smith (Nitro)
... A job is nice, but it interferes with my BBSing...
--- 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
|
[ << oldest | < older | list | newer > | newest >> ]