Hi All,

I did a fresh build of htick (and nltools) using these instructions:

"""
2.4 Installing Husky on Other UNIX-like Operating Systems ---------------------------------------------------------

To start the installation, follow these steps:

wget https://raw.githubusercontent.com/huskyproject/huskybse/master/script/init_build
chmod 0755 init_build
./init_build

[...]
"""

From: husky/huskybse/INSTALL.asciidoc

If I build with:

DYNLIBS=0

I get a couple of these errors:

/usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../x86_64-suse-linux/bin/ld: cannot find -l:libz.a
collect2: error: ld returned 1 exit status
nltools/Makefile:80: recipe for target 'nltools/Build/nlupd' failed
make: *** [nltools/Build/nlupd] Error 1

I don't have 'libz.a', so that explains it. And I found out it's required by libzip. And probably also hptzip...

When I build with DYNLIBS=1 everything is ok, so that is what I'm stuck with for now.


Second issue. When I have these lines in my config:

set basedir=/home/fido
...

FileFixHelp [basedir]/etc/filefix.hlp

I get this error, when I run htick:

"/home/fido/etc/husky.config", line 90: unrecognized: FileFixHelp [basedir]/etc/filefix.hlp
Please correct above error(s) first!

That is strange! And I suspect this is why my links don't get a response to their '%help' commands!?


Third issue:

With this line in my configuration:

FileFixReportsAttr loc pvt

The default also includes 'npd k/s'. But I don't want the report msg's auto killed, so I removed the 'k/s', but this isn't honered by htick, the 'k/s' flag is still added to the report message. :-(

Btw: What is the 'npd' flag? I can't find it explained in the husky docs or other files, nor is it mentioned in any ftsc document.


Bye, Wilfred.

--- FMail-lnx64 2.3.2.3-B20240423
* Origin: FMail development HQ (2:280/464)

Hello Wilfred,

Monday May 20 2024, Wilfred van Velzen wrote to All:

If I build with:
DYNLIBS=0
I get a couple of these errors:

/usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../x86_64-suse-linux/bin /ld: cannot find -l:libz.a

I don't have 'libz.a'

RedHat distributions have libz.a in the 'zlib-static' package. You have to determine which package contains libz.a in your distribution.

Second issue.
FileFixHelp [basedir]/etc/filefix.hlp

Third issue:
FileFixReportsAttr loc pvt

You should read section "3.7 Robot definition keywords (Robot section)" in the fidoconfig documentation. You define

Robot FileFix
Helpfile [basedir]/etc/filefix.hlp
ReportsAttr pvt loc


Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20240309
* Origin: Moscow, Russia (2:5020/1042)

Hi Michael,

On 2024-05-20 22:26:02, you wrote to me:

If I build with:
DYNLIBS=0
I get a couple of these errors:

/usr/lib64/gcc/x86_64-suse-linux/4.8/../../../../x86_64-suse-linux/bin
/ld: cannot find -l:libz.a

I don't have 'libz.a'

RedHat distributions have libz.a in the 'zlib-static' package. You have to determine which package contains libz.a in your distribution.

Thanks for the clue! I was just looking for packages with "libz" in the name. libz.a Was in a package named 'zlib-devel-static' in my distribution.

Second issue.
FileFixHelp [basedir]/etc/filefix.hlp

Third issue:
FileFixReportsAttr loc pvt

You should read section "3.7 Robot definition keywords (Robot section)" in the
fidoconfig documentation. You define

Robot FileFix
Helpfile [basedir]/etc/filefix.hlp
ReportsAttr pvt loc

Ok, thanks this works!

But the htick documentation doesn't mention this or the 'Robot' keyword at all! But it does mention the FileFix* configuration lines, so how I am supposed to know!? ;-)


Bye, Wilfred.

--- FMail-lnx64 2.3.2.3-B20240423
* Origin: FMail development HQ (2:280/464)

Hello Wilfred,

Monday May 20 2024, Wilfred van Velzen wrote to Michael Dukelsky:

You should read section "3.7 Robot definition keywords (Robot
section)" in the fidoconfig documentation. You define

Robot FileFix
Helpfile [basedir]/etc/filefix.hlp
ReportsAttr pvt loc

Ok, thanks this works!

You are welcome.

But the htick documentation doesn't mention this or the 'Robot'
keyword at all! But it does mention the FileFix* configuration lines,
so how I am supposed to know!? ;-)

Yes, the documentation needs updating.

Michael

... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20240309
* Origin: Moscow, Russia (2:5020/1042)

Ha die Wilfred,

In een bericht van Mon,20 May 2024.13:21:01 schreef je:

"/home/fido/etc/husky.config", line 90: unrecognized: FileFixHelp [basedir]/etc/filefix.hlp
Please correct above error(s) first!

That is strange! And I suspect this is why my links don't get a
response to their '%help' commands!?

Probably :-)

But it can also occur if you use 'RobotsArea' in your config.

I was using this in my config:

set basedir=/var/spool/ftn/
set msgbase=[basedir]msgBase/

Robot default
RobotsArea botmail
Robot Filefix
HelpFile [basedir]misc/filefix.txt

NetmailArea NetmailArea [msgbase]AcoNetmail -d "Netmail berichten"
NetmailArea botmail [msgbase]botmail -d "Netmail aan *fix robots"

which passed 'tparser' without problems, but I couldn't get Filefix to respond to messages I addressed to it, logging over and over again:

Start filefix scan...
Scanning 0 messages of botmail
End

Seeing this thread, I've started some experimenting wrt. to Filefix.
Now I've changed my config to:

# RobotsArea botmail
# NetmailArea botmail [msgbase]botmail -d "Netmail aan *fix robots"

(so it's using the defined NetmailArea) and suddenly I got tens of netmails with it's responses to the earlier messages, logging:

Start filefix scan...
Scanning 137 messages of NetmailArea
FileFix: request from 77:8500/100.1
FileFix: List sent to 77:8500/100.1
FileFix: HELP sent to Coast.1
Wrote Netmail to: 77:8500/100.1
FileFix: successfully done for 77:8500/100.1
...
End

So, thanks for asking! :-)

Greetings,
Simon.
--- WimpLink 1.05p
* Origin: Blijft u straks achter? Jezuskomtspoedig.nl (2:280/1049.1)

Hi Simon,

On 2024-05-22 13:33:58, you wrote to me:

"/home/fido/etc/husky.config", line 90: unrecognized: FileFixHelp
[basedir]/etc/filefix.hlp
Please correct above error(s) first!

That is strange! And I suspect this is why my links don't get a
response to their '%help' commands!?

Probably :-)

But it can also occur if you use 'RobotsArea' in your config.

I don't...

...

Seeing this thread, I've started some experimenting wrt. to Filefix.
Now I've changed my config to:

# RobotsArea botmail
# NetmailArea botmail [msgbase]botmail -d "Netmail aan *fix robots"

(so it's using the defined NetmailArea) and suddenly I got tens of netmails
with it's responses to the earlier messages, logging:

Start filefix scan...
Scanning 137 messages of NetmailArea
FileFix: request from 77:8500/100.1
FileFix: List sent to 77:8500/100.1
FileFix: HELP sent to Coast.1
Wrote Netmail to: 77:8500/100.1
FileFix: successfully done for 77:8500/100.1
...
End

So, thanks for asking! :-)

Glad to be of service! ;-)


Bye, Wilfred.

--- FMail-lnx64 2.3.2.3-B20240423
* Origin: FMail development HQ (2:280/464)

Hi Simon,

On 2024-05-22 13:33:58, you wrote to me:

"/home/fido/etc/husky.config", line 90: unrecognized: FileFixHelp WvV>> [basedir]/etc/filefix.hlp
Please correct above error(s) first!

That is strange! And I suspect this is why my links don't get a
response to their '%help' commands!?

Probably :-)

But it can also occur if you use 'RobotsArea' in your config.

I don't...

...

Seeing this thread, I've started some experimenting wrt. to Filefix.
Now I've changed my config to:

# RobotsArea botmail
# NetmailArea botmail [msgbase]botmail -d "Netmail aan *fix robots"

(so it's using the defined NetmailArea) and suddenly I got tens of
netmails with it's responses to the earlier messages, logging:

Start filefix scan...
Scanning 137 messages of NetmailArea
FileFix: request from 77:8500/100.1
FileFix: List sent to 77:8500/100.1
FileFix: HELP sent to Coast.1
Wrote Netmail to: 77:8500/100.1
FileFix: successfully done for 77:8500/100.1
...
End

So, thanks for asking! :-)

Glad to be of service! ;-)

I cannot find a filefix help file anywhere, anyone know where I can get one?


Regards,

Rick
--- AfterShock/Android 1.7.5
* Origin: Wormhole II BBS, Sysop Point (1:105/11.1)

Hi Rick,

On 2024-06-07 18:39:55, you wrote to me:

Start filefix scan...
Scanning 137 messages of NetmailArea
FileFix: request from 77:8500/100.1
FileFix: List sent to 77:8500/100.1
FileFix: HELP sent to Coast.1
Wrote Netmail to: 77:8500/100.1
FileFix: successfully done for 77:8500/100.1
...
End

So, thanks for asking! :-)

Glad to be of service! ;-)

I cannot find a filefix help file anywhere, anyone know where I can
get one?

https://raw.githubusercontent.com/huskyproject/htick/master/misc/filefix.hlp


Bye, Wilfred.

--- FMail-lnx64 2.3.2.4-B20240523
* Origin: FMail development HQ (2:280/464)

Hello Wilfred!

Thursday June 13 2024 22:22, you wrote to me:

* Forwarded from area 'FIDOSOFT.HUSKY'
Hi Rick,

On 2024-06-07 18:39:55, you wrote to me:

Start filefix scan...
Scanning 137 messages of NetmailArea
FileFix: request from 77:8500/100.1
FileFix: List sent to 77:8500/100.1
FileFix: HELP sent to Coast.1
Wrote Netmail to: 77:8500/100.1
FileFix: successfully done for 77:8500/100.1
...
End

So, thanks for asking! :-)

Glad to be of service! ;-)

I cannot find a filefix help file anywhere, anyone know where I
can get one?

https://raw.githubusercontent.com/huskyproject/htick/master/misc/filef

Thank you sir!


Regards,

Rick

... and suddenly, you remember why you started BBSing in the first place.
--- GoldED+/LNX 1.1.5-b20180707
* Origin: Awesome Net- Oregon FTN Hub - www.awesomenet.us (1:105/81)