I noticed on my new setup (working almost perfectly) that binkd starts
to
execute my toss command but I get the rc code
05 Jan 06:42:59 [46710] Running nice -n 19 /usr/local/bin/hpt toss afix
05 Jan 06:42:59 [46710] executing `nice -n 19 /usr/local/bin/hpt toss afix'
05 Jan 06:42:59 [46710] rc=17664
this is my binkd.cfg line, which worked fine on bbs when it was on the RPI now on VM does not appear to
exec "nice -n 19 /usr/local/bin/hpt toss afix" /mystic/echomail/in/*.[STFWMstfwm][ouaherOUAHER][0-9A-Za-z] exec "nice -n 19 /usr/local/bin/htick toss scan" /mystic/echomail/in/*.tic *.TIC
* Forwarded from area 'BINKD'
Rick wrote (2023-01-05):
Greetings All!
I noticed on my new setup (working almost perfectly) that binkd
starts to execute my toss command but I get the rc code
05 Jan 06:42:59 [46710] Running nice -n 19 /usr/local/bin/hpt
toss afix 05 Jan 06:42:59 [46710] executing `nice -n 19
/usr/local/bin/hpt toss afix' 05 Jan 06:42:59 [46710] rc=17664
Maybe look at the hpt logs?
The first thing I would check are user permissions.
Greetings Oli!
Thursday January 05 2023 17:49, you wrote to me about an urgent matter!:
* Forwarded from area 'BINKD'
Rick wrote (2023-01-05):
Greetings All!
I noticed on my new setup (working almost perfectly) that binkd
starts to execute my toss command but I get the rc code
05 Jan 06:42:59 [46710] Running nice -n 19 /usr/local/bin/hpt
toss afix 05 Jan 06:42:59 [46710] executing `nice -n 19
/usr/local/bin/hpt toss afix' 05 Jan 06:42:59 [46710] rc=17664
Maybe look at the hpt logs?So still is not working. I can do it manually and it runs without errors. Binkd for some reason cannot seem to kick it off, I have tried doing a script in /usr/local/bin for binkd to run and it wont fire, but if I run it from any prompt it works as expected. Everything binkd or husky uses is in /fido/etc which my user owns and the bbs is in /mystic also which my user owns... ?
The first thing I would check are user permissions.
* Forwarded from area 'BINKD'
Hello, Rick Smith.
On 06/01/2023 15.34 you wrote:
Greetings Oli!
Thursday January 05 2023 17:49, you wrote to me about an urgent
matter!:
* Forwarded from area 'BINKD'
Rick wrote (2023-01-05):
run and it wont fire, but if I run it from any prompt it works asGreetings All!
expected. Everything binkd or husky uses is in /fido/etc which
my user owns and the bbs is in /mystic also which my user owns...
?
I would remove that 'nice' first. Do you really need it?
I did, no not needed as it turns out. Still wouldnt work however. So
I made just a mail script and tried to have bink call that, still not working
06 Jan 14:30:01 [59431] executing `/usr/local/bin/mail-toss'
- 06 Jan 14:30:01 [59431] rc=17664
However I can run mail-toss from anywhere and it works... bizarre.
Friday January 06 2023 16:09, you wrote to me about an urgent matter!:
I did, no not needed as it turns out. Still wouldnt work however. So I made just a mail script and tried to have bink call that, still not working
06 Jan 14:30:01 [59431] executing `/usr/local/bin/mail-toss'
- 06 Jan 14:30:01 [59431] rc=17664
However I can run mail-toss from anywhere and it works... bizarre.
* Forwarded from area 'BINKD'
Hi Rick,
On 2023-01-06 07:57:32, you wrote to Tommi Koivula:
I did, no not needed as it turns out. Still wouldnt work
however. So I made just a mail script and tried to have bink
call that, still not working
06 Jan 14:30:01 [59431] executing `/usr/local/bin/mail-toss'
- 06 Jan 14:30:01 [59431] rc=17664
However I can run mail-toss from anywhere and it works...
bizarre.
What does:
# sudo ps -C binkd -o euser,ruser,suser,fuser,pid,args
* Forwarded from area 'BINKD'
Rick wrote (2023-01-06):
Friday January 06 2023 16:09, you wrote to me about an urgent
matter!: I did, no not needed as it turns out. Still wouldnt
Because the script would work without it from the shell, but might not work if it is executed by another process.
Greetings Oli!
Friday January 06 2023 17:47, you wrote to me about an urgent matter!:
* Forwarded from area 'BINKD'
Rick wrote (2023-01-06):
Friday January 06 2023 16:09, you wrote to me about an urgent
matter!: I did, no not needed as it turns out. Still wouldnt
Because the script would work without it from the shell, but might
not work if it is executed by another process.
#!/bin/bash
echo "processsing" > /tmp/test.txt
cd /mystic/echomail/in
hpt toss afix
Here is my line in binkd.cfg^^ ^^
exec /usr/local/bin/mail-toss"
/mystic/echomail/in/*.[STFWMstfwm][ouaherOUAHER][0-9A-Za-z] *.[pP][kK][t>
06 Jan 14:30:01 [59431] executing `/usr/local/bin/mail-toss'
- 06 Jan 14:30:01 [59431] rc=17664
However I can run mail-toss from anywhere and it works...
bizarre.
What does:
# sudo ps -C binkd -o euser,ruser,suser,fuser,pid,args
EUSER RUSER SUSER FUSER PID COMMAND
rick rick rick rick 596 binkd: server manager (listen 24554) rick rick rick rick 650 binkd: client manager
Here is my line in binkd.cfg
exec /usr/local/bin/mail-toss"^^ ^^
Now the line is missing an opening " character
I doubt it would fix the problem, but I don't have any better ideas.
Hi Oli,
On 2023-01-07 09:39:41, you wrote to Rick Smith:
Here is my line in binkd.cfg
exec /usr/local/bin/mail-toss"
^^ ^^
Now the line is missing an opening " character
I doubt it would fix the problem, but I don't have any better
ideas.
* Forwarded from area 'BINKD'
Rick wrote (2023-01-06):
Greetings Oli!
Friday January 06 2023 17:47, you wrote to me about an urgent
matter!:
* Forwarded from area 'BINKD'
Rick wrote (2023-01-06):
Friday January 06 2023 16:09, you wrote to me about an urgent
matter!: I did, no not needed as it turns out. Still wouldnt
Because the script would work without it from the shell, but
might not work if it is executed by another process.
#!/bin/bash
echo "processsing" > /tmp/test.txt
cd /mystic/echomail/in
hpt toss afix
shebang is there, that was not the problem.
Maybe try it with the full path for hpt
/usr/local/bin/hpt toss afix
Here is my line in binkd.cfg
exec /usr/local/bin/mail-toss"^^ ^^
Now the line is missing an opening " character
/mystic/echomail/in/*.[STFWMstfwm][ouaherOUAHER][0-9A-Za-z]
*.[pP][kK][t>
05 Jan 06:42:59 [46710] Running nice -n 19 /usr/local/bin/hpt toss afix
05 Jan 06:42:59 [46710] executing `nice -n 19 /usr/local/bin/hpt toss afix' 05 Jan 06:42:59 [46710] rc=17664
05 Jan 06:42:59 [46710] Running nice -n 19 /usr/local/bin/hpt toss
afix 05 Jan 06:42:59 [46710] executing `nice -n 19 /usr/local/bin/hpt
toss afix' 05 Jan 06:42:59 [46710] rc=17664
Btw, how does this exit code happen? Is the script / hpt really returning this value or is it some weirdness in binkd? (I don't know if values > 255 can be returned at all).
I noticed on my new setup (working almost perfectly) that binkd starts
to execute my toss command but I get the rc code
05 Jan 06:42:59 [46710] Running nice -n 19 /usr/local/bin/hpt toss
afix
05 Jan 06:42:59 [46710] executing `nice -n 19 /usr/local/bin/hpt
toss afix'
05 Jan 06:42:59 [46710] rc=17664
* Forwarded from area 'BINKD'
Hello Rick,
Thursday January 05 2023, Rick Smith wrote to All:
I noticed on my new setup (working almost perfectly) that binkd
starts to execute my toss command but I get the rc code
05 Jan 06:42:59 [46710] Running nice -n 19 /usr/local/bin/hpt
toss afix 05 Jan 06:42:59 [46710] executing `nice -n 19
/usr/local/bin/hpt toss afix' 05 Jan 06:42:59 [46710] rc=17664
17664=0x4500
The exit code returned by hpt is the higher byte, that is 0x45.
Something was wrong. Could you please set the log levels in your hpt config: LogLevels 1-90A-Za-z and specify the path to your hpt config
on the command line: /usr/local/bin/hpt -c /path/to/config toss afix
I noticed on my new setup (working almost perfectly) that binkd
starts to execute my toss command but I get the rc code
05 Jan 06:42:59 [46710] Running nice -n 19 /usr/local/bin/hpt
toss afix 05 Jan 06:42:59 [46710] executing `nice -n 19
/usr/local/bin/hpt toss afix' 05 Jan 06:42:59 [46710] rc=17664
17664=0x4500
The exit code returned by hpt is the higher byte, that is 0x45.
Something was wrong. Could you please set the log levels in your
hpt
config: LogLevels 1-90A-Za-z and specify the path to your hpt
config on the command line: /usr/local/bin/hpt -c /path/to/config
toss afix
I did as you suggested, I still have to run the script manually. I
will send you a netmail with the hpt.log attached.
* Forwarded from area 'BINKD'OK I add this to binkd will report back
Hello Rick,
Sunday January 08 2023, Rick Smith wrote to Michael Dukelsky:
I noticed on my new setup (working almost perfectly) that binkd
starts to execute my toss command but I get the rc code
05 Jan 06:42:59 [46710] Running nice -n 19 /usr/local/bin/hpt
toss afix 05 Jan 06:42:59 [46710] executing `nice -n 19
/usr/local/bin/hpt toss afix' 05 Jan 06:42:59 [46710] rc=17664
Everything looks good in the log I've received from you. So, when you
run the script manually, it works. And what happens if you put the following line to your binkd config: exec "/usr/local/bin/hpt -c /path/to/hpt/config toss afix" /mystic/echomail/in/*.[STFWMstfwm][ouaherOUAHER][0-9A-Za-z]
BTW, if SELinux is on, it is better to switch it off for now.
* Forwarded from area 'BINKD'
Hello Rick,
Sunday January 08 2023, Rick Smith wrote to Michael Dukelsky:
I noticed on my new setup (working almost perfectly) that binkd
starts to execute my toss command but I get the rc code
run the script manually, it works. And what happens if you put the
* Forwarded from area 'BINKD'
Hello Rick,
Sunday January 08 2023, Rick Smith wrote to Michael Dukelsky:
following line to your binkd config: exec "/usr/local/bin/hpt -c /path/to/hpt/config toss afix" /mystic/echomail/in/*.[STFWMstfwm][ouaherOUAHER][0-9A-Za-z]
* Forwarded from area 'BINKD'
Hello Rick,
Thursday January 05 2023, Rick Smith wrote to All:
I noticed on my new setup (working almost perfectly) that binkd
starts to execute my toss command but I get the rc code
05 Jan 06:42:59 [46710] Running nice -n 19 /usr/local/bin/hpt
toss afix 05 Jan 06:42:59 [46710] executing `nice -n 19
/usr/local/bin/hpt toss afix' 05 Jan 06:42:59 [46710] rc=17664
17664=0x4500
The exit code returned by hpt is the higher byte, that is 0x45.
Something was wrong. Could you please set the log levels in your hpt config: LogLevels 1-90A-Za-z and specify the path to your hpt config
on the command line: /usr/local/bin/hpt -c /path/to/config toss afix
* Forwarded from area 'BINKD'
Hello Rick,
Sunday January 08 2023, Rick Smith wrote to Michael Dukelsky:
I noticed on my new setup (working almost perfectly) that binkd
starts to execute my toss command but I get the rc code
05 Jan 06:42:59 [46710] Running nice -n 19 /usr/local/bin/hpt
toss afix 05 Jan 06:42:59 [46710] executing `nice -n 19
/usr/local/bin/hpt toss afix' 05 Jan 06:42:59 [46710] rc=17664
17664=0x4500
The exit code returned by hpt is the higher byte, that is 0x45.
Something was wrong. Could you please set the log levels in your
hpt
config: LogLevels 1-90A-Za-z and specify the path to your hpt
config on the command line: /usr/local/bin/hpt -c
/path/to/config toss afix
I did as you suggested, I still have to run the script manually.
I will send you a netmail with the hpt.log attached.
Everything looks good in the log I've received from you. So, when you
run the script manually, it works. And what happens if you put the following line to your binkd config: exec "/usr/local/bin/hpt -c /path/to/hpt/config toss afix" /mystic/echomail/in/*.[STFWMstfwm][ouaherOUAHER][0-9A-Za-z]
Everything looks good in the log I've received from you. So, when
you run the script manually, it works. And what happens if you
put the following line to your binkd config: exec
"/usr/local/bin/hpt -c /path/to/hpt/config toss afix"
/mystic/echomail/in/*.[STFWMstfwm][ouaherOUAHER][0-9A-Za-z]
got it working by adding config path to the script.. I have an "export FIDOCONFIG=/etc/ftn/config" in .bashrc is that not sufficient?
got it working by adding config path to the script.. I have an "export FIDOCONFIG=/etc/ftn/config" in .bashrc is that not sufficient?
* Forwarded from area 'BINKD'
Hi Rick,
On 22 Jan 23 09:11, Rick Smith wrote to Michael Dukelsky:
about: "mail not tossing":
got it working by adding config path to the script.. I have an
"export FIDOCONFIG=/etc/ftn/config" in .bashrc is that not
sufficient?
No. From `man bash`:
"When an interactive shell that is not a login shell is started, bash reads and executes commands from /etc/bash.bashrc then ~/.bashrc when those files exist and are readable. This may be inhibited by using the --norc option. The --rcfile file option will force bash to read and execute commands from file instead of ~/.bashrc.
When bash is started non-interactively, to run a shell script, for example, ..."
Sysop: | Fercho |
---|---|
Lugar: | La Plata, Buenos Aires |
Usuarios: | 33 |
Nodos: | 10 (0 / 10) |
Uptime: | 03:19:47 |
Llamadas: | 119 |
Archivoss: | 15,607 |
Mensajes: | 32,804 |