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: | Tetrazocine |
---|---|
Location: | Melbourne, VIC, Australia |
Users: | 6 |
Nodes: | 8 (0 / 8) |
Uptime: | 24:15:14 |
Calls: | 51 |
Files: | 21,492 |
Messages: | 68,153 |