Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 8275  |
|  Wilfred van Velzen to Rick Smith  |
|  Re: still not tossing  |
|  12 Jan 23 08:18:52  |
 
RFC-X-No-Archive: Yes
TZUTC: 0100
CHRS: CP437 2
PID: GED+W64 1.1.5-b20170303
MSGID: 2:280/464.112 63bfb502
REPLY: 1:105/10 63bf8785
Hi Rick,
On 11 Jan 23 20:06, Rick Smith wrote to Wilfred van Velzen:
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 (normal
WV>> and errors). It's now redirected to the /tmp/test.txt file...
RS> ok, still not tossing but now the test.txt isnt being created with the
RS> script above that you suggested?
You don't quote the first line:
#!/bin/bash
Did you include that in the script?
Does it work on the commandline, and creating the /tmp/test.txt file?
Wilfred.
--- FMail-W32 2.0.1.4
* Origin: point@work (2:280/464.112)
SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 114/709 120/340 123/131
SEEN-BY: 124/5016 129/305 153/757 7715 154/10 203/0 218/700 221/0
SEEN-BY: 221/1 226/30 227/114 229/110 111 112 113 114 200 206 307
SEEN-BY: 229/317 424 426 428 470 550 664 700 240/1120 5832 266/512
SEEN-BY: 280/464 5003 5555 282/1038 292/789 854 8125 301/1 310/31
SEEN-BY: 317/3 320/219 322/757 335/364 341/66 234 342/200 396/45 410/9
SEEN-BY: 423/120 460/58 633/280 712/848 770/1
PATH: 280/464 292/854 229/426
|
[ << oldest | < older | list | newer > | newest >> ]