rick@abacus:~$ cat /usr/local/bin/mail-toss.sh
#!/bin/bash
echo "processsing" > /tmp/test.txt
echo "PATH = $PATH";
echo "SHELL = $SHELL";
/usr/local/bin/hpt toss
so the test.tx still gets created, so binkd is running the script, it just doesn't execute the hpt toss?
----
Regards,
Rick Smith (Nitro)
... YKYHW: You consider BBSing better than chocolate.
* Forwarded from area 'BINKD'
rick@abacus:~$ cat /usr/local/bin/mail-toss.sh
#!/bin/bash
echo "processsing" > /tmp/test.txt
This line well echo "processing" and redirect the output to /tmp/test
echo "PATH = $PATH";
This line will echo PATH = /your path (whatever it is).
echo "SHELL = $SHELL";
This line will echo SHELL = /bin/bash, if bash is your shell but those lines won't change your path or shell in any way.
/usr/local/bin/hpt toss
I would expect /usr/local/bin/hpt toss does run if that is the path to hpt.
so the test.tx still gets created, so binkd is running the script,
it just doesn't execute the hpt toss?
Binkd doesn't run hpt, it just runs your script that needs to do what
you want it to do.
Im confused at your response, I did not ask what each line of my
script does,
I was merely looking for help as to why hpt toss isnt running. I know that binkd doesnt execute hpt, I was saying that binkd correctly runs mail-toss script and I know this because that text file gets created. However my system for whatever reason doesnt continue on with the
script.
so the test.tx still gets created, so binkd is running the script, it
just doesn't execute the hpt toss?
/usr/local/bin/hpt toss
rick@abacus:~$ cat /usr/local/bin/mail-toss.sh
#!/bin/bash
echo "processsing" > /tmp/test.txt
echo "PATH = $PATH";
echo "SHELL = $SHELL";
/usr/local/bin/hpt toss
so the test.tx still gets created, so binkd is running the script, it just doesn't execute the hpt toss?
This is getting strange, I am sure it is something I am just
overlooking
Ive know tried adding /mystic /fido/etc to the path and changed my script to be;
rick@abacus:~$ cat /usr/local/bin/mail-toss.sh
#!/bin/bash
echo "processsing" > /tmp/test.txt
echo "PATH = $PATH";
echo "SHELL = $SHELL";
/usr/local/bin/hpt toss
* Forwarded from area 'BINKD'
Hi Rick,
On 2023-01-07 19:45:08, you wrote to All:
This is getting strange, I am sure it is something I am just
overlooking
Ive know tried adding /mystic /fido/etc to the path and changed
my script to be;
rick@abacus:~$ cat /usr/local/bin/mail-toss.sh
#!/bin/bash
echo "processsing" > /tmp/test.txt
echo "PATH = $PATH";
echo "SHELL = $SHELL";
/usr/local/bin/hpt toss
{
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
{
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..
rick@abacus:~$ cat /usr/local/bin/mail-toss.sh
#!/bin/bash
echo "processsing" > /tmp/test.txt
echo "PATH = $PATH";
echo "SHELL = $SHELL";
/usr/local/bin/hpt toss
{
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..
* Forwarded from area 'BINKD'
Hi Rick,
On 08 Jan 23 15:02, Rick Smith wrote to Wilfred van Velzen:
about: "still not tossing":
rick@abacus:~$ cat /usr/local/bin/mail-toss.sh
#!/bin/bash
echo "processsing" > /tmp/test.txt
echo "PATH = $PATH";
echo "SHELL = $SHELL";
/usr/local/bin/hpt toss
{
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...
Wilfred.
* Forwarded from area 'BINKD'
Hi Rick,
On 08 Jan 23 15:02, Rick Smith wrote to Wilfred van Velzen:
about: "still not tossing":
rick@abacus:~$ cat /usr/local/bin/mail-toss.sh
#!/bin/bash
echo "processsing" > /tmp/test.txt
echo "PATH = $PATH";
echo "SHELL = $SHELL";
/usr/local/bin/hpt toss
{
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...
Wilfred.
{
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?
* 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.
{
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
* 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.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 410 |
Nodes: | 16 (2 / 14) |
Uptime: | 98:08:48 |
Calls: | 8,588 |
Calls today: | 1 |
Files: | 13,228 |
Messages: | 5,934,265 |