Hallo Torsten!

smanntp2.zip 293360 Area: DATENBAHN.OS2.BBS.TOSS Origin: 2:240/5832

Squish seems to work fine so far, but *sometimes* I get errors when
trying to read JAM or MSG bases.

(192.168.1.6:49827) < GROUP netmail-msg
(192.168.1.6:49827) > 211 0 0 0 netmail-msg Group selected
(192.168.1.6:49827) < GROUP rbb-test-3-s
(192.168.1.6:49827) > 211 11 1 11 rbb-test-3-s Group selected (192.168.1.6:49827) < GROUP rbb-test-2-s
(192.168.1.6:49827) > 211 6 1 6 rbb-test-2-s Group selected
(192.168.1.6:49827) < GROUP jamnntpd-squ
(192.168.1.6:49827) > 211 81 1 81 jamnntpd-squ Group selected (192.168.1.6:49827) < LIST
(192.168.1.6:49827) > 215 List of newsgroups follows
(192.168.1.6:49827) > netmail-msg 0 0 y
(192.168.1.6:49827) > netmail-husky 3 15 y
(192.168.1.6:49827) > netmail-husky-0 1 233 y

Killed by SIGSEGV
pid=0x4779 ppid=0x4627 tid=0x0002 slot=0x01ac pri=0x0200 mc=0x0001 ps=0x0010 D:\JAMNNTPD\SMAPINNTPD\VER_1_1_01\OS2BIN\SMAPINNTPD.EXE
SMAPINNT 0:000198a6
cs:eip=005b:000298a6 ss:esp=0053:0258f59c ebp=0258f7e4
ds=0053 es=0053 fs=150b gs=0000 efl=00012206
eax=00000000 ebx=00000001 ecx=0055db60 edx=0055db60 edi=00000000
esi=0000005c
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.


'Tommi

---
* Origin: SmapiNNTPd/2 (2:221/1)

On 2018 Dec 27 11:47:36, you wrote to DatenBahn BBS:

smanntp2.zip 293360 Area: DATENBAHN.OS2.BBS.TOSS Origin: 2:240/5832

Squish seems to work fine so far, but *sometimes* I get errors when
trying to read JAM or MSG bases.

i used to see similar problems on my OS/2 system when it was running... i traced them to not fully compliant message base sharing... i've never seen jamnntpd ask the tosser for access to a message base when the tosser had it locked... jamnntpd recorded an error and kept going... or not... i saw this mostly during my system's midnight maint when the message bases could be locked
for quite a while while they were being cleaned up by fastecho...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Half The People In The World Are Below Average.
---
* Origin: (1:3634/12.73)

Hi mark.

27 Dec 18 17:34:44, you wrote to me:

On 2018 Dec 27 11:47:36, you wrote to DatenBahn BBS:

smanntp2.zip 293360 Area: DATENBAHN.OS2.BBS.TOSS Origin: 2:240/5832

Squish seems to work fine so far, but *sometimes* I get errors when
trying to read JAM or MSG bases.

i used to see similar problems on my OS/2 system when it was running... i traced them to not fully compliant message base sharing...

In this case of my testing of smapinntpd, I doubt it.

I'd say it is husky smapi on OS/2. I've seen errors like this happening with HPT and JAM too.

'Tommi

... \\COW has been up for: 25 day(s), 14 hour(s), 38 minute(s), 6 second(s)
---
* Origin: *** nntp://fidonews.mine.nu *** Finland *** (2:221/6)

Hallo Tommi!

27.12.2018 11:47, Tommi Koivula schrieb an DatenBahn BBS:

smanntp2.zip

Squish seems to work fine so far, but *sometimes* I get errors when
trying to read JAM or MSG bases.

Ahm, okay.

(192.168.1.6:49827) < GROUP netmail-msg
(192.168.1.6:49827) > 211 0 0 0 netmail-msg Group selected (192.168.1.6:49827) < GROUP rbb-test-3-s
(192.168.1.6:49827) > 211 11 1 11 rbb-test-3-s Group selected (192.168.1.6:49827) < GROUP rbb-test-2-s
(192.168.1.6:49827) > 211 6 1 6 rbb-test-2-s Group selected (192.168.1.6:49827) < GROUP jamnntpd-squ
(192.168.1.6:49827) > 211 81 1 81 jamnntpd-squ Group selected (192.168.1.6:49827) < LIST
(192.168.1.6:49827) > 215 List of newsgroups follows
(192.168.1.6:49827) > netmail-msg 0 0 y
(192.168.1.6:49827) > netmail-husky 3 15 y
(192.168.1.6:49827) > netmail-husky-0 1 233 y

Killed by SIGSEGV
pid=0x4779 ppid=0x4627 tid=0x0002 slot=0x01ac pri=0x0200 mc=0x0001 ps=0x0010
D:\JAMNNTPD\SMAPINNTPD\VER_1_1_01\OS2BIN\SMAPINNTPD.EXE
SMAPINNT 0:000198a6
cs:eip=005b:000298a6 ss:esp=0053:0258f59c ebp=0258f7e4
ds=0053 es=0053 fs=150b gs=0000 efl=00012206 eax=00000000 ebx=00000001 ecx=0055db60 edx=0055db60 edi=00000000 esi=0000005c
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.

Well, there is a big bug with the filehandles. sqapi handles them by itself, but with jam and msg you have to check the filelocks by yourself.
There is also a bug with the sockets, and there is a big bug with errorhandling.

I'm currently working on this.

I've never expected, someone else than me will using smapinntp2. Thanks for testing.

'Tommi

Bye/2 Torsten

... MAILBOX01 on OS2: up 7d 10h 56m load: 37 proc, 151 threads (tbupv1.1)
--- GoldED+ 1.1.5-18
* Origin: DatenBahn BBS Hamburg (2:240/5832)

Hallo Tommi!

28.12.2018 10:29, Tommi Koivula schrieb an mark lewis:

I'd say it is husky smapi on OS/2. I've seen errors like this
happening with HPT and JAM too.

It is currently with the husky 1.3.1 api of husky.

As I have written before; I'm working on the bugs and working on adopting to husky1.9-current.

'Tommi

Bye/2 Torsten

... MAILBOX01 on OS2: up 7d 10h 56m load: 37 proc, 151 threads (tbupv1.1)
--- GoldED+ 1.1.5-18
* Origin: DatenBahn BBS Hamburg (2:240/5832)

Killed by SIGSEGV
pid=0x4779 ppid=0x4627 tid=0x0002 slot=0x01ac pri=0x0200 mc=0x0001 ps=0x0010
D:\JAMNNTPD\SMAPINNTPD\VER_1_1_01\OS2BIN\SMAPINNTPD.EXE
SMAPINNT 0:000198a6
cs:eip=005b:000298a6 ss:esp=0053:0258f59c ebp=0258f7e4
ds=0053 es=0053 fs=150b gs=0000 efl=00012206 eax=00000000 ebx=00000001 ecx=0055db60 edx=0055db60 edi=00000000 esi=0000005c
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.

Well, there is a big bug with the filehandles. sqapi handles them by
itself, but with jam and msg you have to check the filelocks by yourself. There is also a bug with the sockets, and there is a big bug with errorhandling.

Ok.

I've never expected, someone else than me will using smapinntp2. Thanks
for testing.

Sure. :)

'Tommi

---
* Origin: RBB SmapiNNTPd/2 (2:221/1.0)