Hi Rick,

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

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

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

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

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

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

ok, still not tossing but now the test.txt isnt being created with the 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)

Greetings Wilfred!

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

* Forwarded from area 'BINKD'
Hi Rick,

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

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

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

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

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

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

ok, still not tossing but now the test.txt isnt being created
with the 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.

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)

Hi Rick,

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

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

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

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

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

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

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

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

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

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)

Greetings Wilfred!

Thursday January 12 2023 15:30, you wrote to me about an urgent matter!:

* Forwarded from area 'BINKD'
Hi Rick,

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

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

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

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

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

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

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

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

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

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.

I rebuilt husky and all is fine now... wish I had started there, thank you for all your help


----
Regards,


Rick Smith (Nitro)

... I love BBSing: All the social dynamics of kindergarten!
--- GoldED+/LNX 1.1.5-b20220504
* Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)