binkd OS2 klibc

[mark lewis]

where can i get daily builds of binkd for OS2 of the klibc flavor? all of the
recent emx versions are cauing lockups with my allfix installation... once i
close/kill binkd, the allfix carries on as if nothing was ever the matter...
the klibc stuff doesn't cause this problem...

thanks!

)\/(ark

[Max Vasilyev]

Hello mark!

31 Jul 13 21:10, you wrote to all:

ml> where can i get daily builds of binkd for OS2 of the klibc flavor?
binkd1.1a28-binkd2klibc-bwlim.zip is downloadable from
http://sites.google.com/site/vasilyevmax/fido

WBR, Max. piwamoto!писем-нет

[mark lewis]

On Fri, 02 Aug 2013, Max Vasilyev wrote to mark lewis:

ml> where can i get daily builds of binkd for OS2 of the klibc flavor?

MV> binkd1.1a28-binkd2klibc-bwlim.zip is downloadable from
MV> http://sites.google.com/site/vasilyevmax/fido

thank you, sir...

is there also a klibc flavor of the latest release? 1.0.2?? i didn't find one
that was apparent on the above site...

specifically what i'm having a problem with is

1. changing a config file in the background
(try to free already freed memory - libc panic - exitcode 1)
2. exitcodes different from 1 and 127

for #2, i've written a wrapper script around binkd so that hopefully i could
restart binkd after a crash of #1 or others... i quickly found that crashes and
normal termination via CTRL-C or CTRL-BREAK all exit with exitcode 1... so i
have no way to distinquish a normal termination via CTRL-C or CTRL-BREAK and a
crash... if i could then i would be able to exit the wrapper or loop to the top
and start binkd again...

i have tried all of the following which i have access to via an emx library...


Usage: SENDSIGNAL signalName|signalNumber pidfile

Signals: Name Number Description
SIGHUP 1 Hangup
SIGINT 2 Interrupt (Ctrl-C)
SIGQUIT 3 Quit
SIGILL 4 Illegal instruction
SIGTRAP 5 Single step (debugging)
SIGABRT 6 abort ()
SIGEMT 7 EMT instruction
SIGFPE 8 Floating point
SIGKILL 9 Kill process
SIGBUS 10 Bus error
SIGSEGV 11 Segmentation fault
SIGSYS 12 Invalid argument to system call
SIGPIPE 13 Broken pipe
SIGALRM 14 Alarm
SIGTERM 15 Termination, process killed
SIGUSR1 16 User-defined signal #1
SIGUSR2 17 User-defined signal #2
SIGCHLD 18 Death of a child process
SIGBREAK 21 Break (Ctrl-Break)


thanks for any assistance you can give on these problems my system faces...


)\/(ark

[Michiel van der Vlist]

Hello mark,

On Friday August 02 2013 13:26, you wrote to Max Vasilyev:

ml> for #2, i've written a wrapper script around binkd so that hopefully i
ml> could restart binkd after a crash of #1 or others... i quickly found
ml> that crashes and normal termination via CTRL-C or CTRL-BREAK all exit
ml> with exitcode 1... so i have no way to distinquish a normal
ml> termination via CTRL-C or CTRL-BREAK and a crash...

This is how I automatically restart Irex after termination. By crash or
otherwise:

:loop
del \sema\*.0
rexw -daemon
choice /C:yn /T:n,5 Quit Rex
if errorlevel 2 goto loop

After exiting, I have 5 seconds to push the 'Y' key to exit the loop. If I do
nothing, it loops after 5 seconds.

This may or may not work on your OS.


Cheers, Michiel

[mark lewis]

On Fri, 02 Aug 2013, Michiel van der Vlist wrote to mark lewis:

ml> for #2, i've written a wrapper script around binkd so that hopefully i
ml> could restart binkd after a crash of #1 or others... i quickly found
ml> that crashes and normal termination via CTRL-C or CTRL-BREAK all exit
ml> with exitcode 1... so i have no way to distinquish a normal
ml> termination via CTRL-C or CTRL-BREAK and a crash...

MvdV> This is how I automatically restart Irex after termination. By
MvdV> crash or otherwise:

thanks for the idea... it will work but human intervention should not be needed
with binkd... it isn't needed with any of the other FTN software i use... all
of them set "proper" exitcodes related to the exit situation... even my SMTP,
FTP and NEWS servers have different exitcodes for crashes as compared to
"normal" and expected exit triggers...

it would be nice and easy to handle if each of the signal numbers that binkd
catches and handles are set as the exitcode... i just saw today that CTRL-C and
CTRL-BREAK are apparently caught as the same signal when done by keyboard...
IIRC, they were different when sent as SIGblurg entries and they are definitely
different in the list of SIG codes i posted...

)\/(ark

[mark lewis]

ml> specifically what i'm having a problem with is

here is the exact crash... i believe it is the same for previous versions... it
is always triggered when one of the included config files changes...


2013-08-03 14:59:37 BNKDWRAP VER : Binkd 1.1a-28 (Aug 2 2013 09:13:43/OS2)
2013-08-03 14:59:39 BNKDWRAP EXTRA : Compilation flags: gcc (klibc), https,
ntlm, amiga_4d_outbound, bwlim.
2013-08-03 14:59:39 BNKDWRAP EXTRA : Facilities: fsp1035 rfc2553emu
2013-08-03 14:59:39 BNKDWRAP _WINTITL: "Binkd 1.1a-28 gcc (klibc) Aug 2 2013
09:13:43/OS2 (0)"

2013-08-03 14:59:39 BNKDWRAP setting default parameters "-C binkd.cfg"
2013-08-03 14:59:39 BNKDWRAP BNKDWRAP starting process round 0 with PARMS="-C
binkd.cfg"
2013-08-03 14:59:40 BNKDWRAP Executing binkd2klibc.exe -C binkd.cfg
[trim - note the above date and the one below - no conf changes until now]
+ 19:05 [11629] mybinkd.txt changed!
+ 19:05 [11629] Reloading configuration...
19:05 [11629] previous config is no longer in use, unloading

LIBC PANIC!!
_um_free_maybe_lock: Tried to free block twice - block=025521c0 lock=0x1
pid=0x2d6d ppid=0x2d6c tid=0x0001 slot=0x0168 pri=0x0200 mc=0x0000
X:\BINKD\BINKD2KLIBC.EXE
+ 19:05 [11628] mybinkd.txt changed!
+ 19:05 [11628] Reloading configuration...
19:05 [11628] previous config is no longer in use, unloading
- 19:05 [11628] servmgr listen on *:24554
Process has been dumped
! 19:05 [11628] client manager (pid=11629) exited by signal 9
2013-08-05 19:05:42 BNKDWRAP binkd2klibc.exe exited
2013-08-05 19:05:43 BNKDWRAP exitcode 1 detected
2013-08-05 19:05:43 BNKDWRAP Terminating...
2013-08-05 19:05:44 BNKDWRAP process terminating

)\/(ark

[Tommi Koivula]

On 31.7.2013 21:10, mark lewis -> all wrote:

ml> where can i get daily builds of binkd for OS2 of the klibc flavor? all
ml> of the recent emx versions are cauing lockups with my allfix
ml> installation... once i close/kill binkd, the allfix carries on as if
ml> nothing was ever the matter... the klibc stuff doesn't cause this
ml> problem...

My everynight compilation is in fact klibc, not emx as stated in the faq. ;)

Just FREQ magic BINKD2E from 2:221/360.

'Tommi

[mark lewis]

On Fri, 02 Aug 2013, Tommi Koivula wrote to mark lewis:

ml> where can i get daily builds of binkd for OS2 of the klibc flavor?
ml> all of the recent emx versions are cauing lockups with my allfix
ml> installation... once i close/kill binkd, the allfix carries on as
ml> if nothing was ever the matter... the klibc stuff doesn't cause
ml> this problem...

TK> My everynight compilation is in fact klibc, not emx as stated in
TK> the faq. ;)

TK> Just FREQ magic BINKD2E from 2:221/360.

ahh! maybe yours was one i was running? it is hard to tell the difference from
the name binkd2e when e many mean emx or klibc... i've had to resort to naming
the exe with a date so i could copy a known working one back in place when a
newer one causes problems...

perhaps the OS/2 klibc binaries could be named binkd2k.exe to differentiate
them from the emx one named binkd2e.exe? the '2' indicating OS/2, of course ;)

in the same thought, is it possible to have either emx or klibc added to the
version string returned from "binkd -v"? all i get is a version string with a
date and time but no library name... it took me several hours to realize that
the emx compile was what was causing my old allfix universal to hang :(

eg: Binkd 1.1a-27 (Jun 1 2013 01:00:19/OS2)
could be
Binkd 1.1a-27 emx (Jun 1 2013 01:00:19/OS2)
or
Binkd 1.1a-27 klibc (Jun 1 2013 01:00:19/OS2)


is there a URL i can send wget after to pull your compile above? i have to jump
thru some hoops in order to send FREQ via binkd on my hybrid frontdoor/binkd
system... sadly, it is easier to kick wget into play when needed for things
like this :?

thanks!

)\/(ark

[Tommi Koivula]

mark lewis -> Tommi Koivula wrote:

ml> ahh! maybe yours was one i was running? it is hard to tell the
ml> difference from the name binkd2e when e many mean emx or klibc... i've
ml> had to resort to naming the exe with a date so i could copy a known
ml> working one back in place when a newer one causes problems...

ml> perhaps the OS/2 klibc binaries could be named binkd2k.exe to
ml> differentiate them from the emx one named binkd2e.exe? the '2'
ml> indicating OS/2, of course ;)

ml> in the same thought, is it possible to have either emx or klibc added to
ml> the version string returned from "binkd -v"? all i get is a version
ml> string with a date and time but no library name...

-vv tells you the compilation flags. ;)

ml> is there a URL i can send wget after to pull your compile above? i have

If you check the FAQ you can find this:

http://rbb.homeip.net/pub/os2/comm/bbs/binkd2e.rar ;)

Also the 1.0.2 can be found there:

http://rbb.homeip.net/pub/os2/comm/bbs/BINKD2E_102-KLIBC.RAR

'Tommi

[mark lewis]

On Sat, 03 Aug 2013, Tommi Koivula wrote to mark lewis:

ml> perhaps the OS/2 klibc binaries could be named binkd2k.exe to
ml> differentiate them from the emx one named binkd2e.exe? the '2'
ml> indicating OS/2, of course ;)

any thoughts on the above? i pulled one from max's site yesterday but it has
the full name of binkdklibc.exe... that's easy enough to handle on the OS/2
native side but the file is invisible from the DOS side of OS/2 :?

ml> in the same thought, is it possible to have either emx or klibc
ml> added to the version string returned from "binkd -v"? all i get is
ml> a version string with a date and time but no library name...

TK> -vv tells you the compilation flags. ;)

right... i was hoping to not have to root about to find it but i guess i can ;)

ml> is there a URL i can send wget after to pull your compile above? i
ml> have

TK> If you check the FAQ you can find this:

TK> http://rbb.homeip.net/pub/os2/comm/bbs/binkd2e.rar ;)

i kinda missed that one because the FAQ said it was EMX...

TK> Also the 1.0.2 can be found there:

TK> http://rbb.homeip.net/pub/os2/comm/bbs/BINKD2E_102-KLIBC.RAR

thank you... i will be dropping by sometime :)

)\/(ark

[Tommi Koivula]

Hello mark.

ml>> perhaps the OS/2 klibc binaries could be named binkd2k.exe to
ml>> differentiate them from the emx one named binkd2e.exe? the '2'
ml>> indicating OS/2, of course ;)

ml> any thoughts on the above? i pulled one from max's site yesterday but
ml> it has the full name of binkdklibc.exe... that's easy enough to handle
ml> on the OS/2 native side but the file is invisible from the DOS side of
ml> OS/2 :?

The default target in mkfls/os2-emx/makefile.klibc is binkd2e.exe. Anyone can
rename it to whatever. :)

'Tommi

[mark lewis]

On Sat, 03 Aug 2013, Tommi Koivula wrote to mark lewis:

ml>> perhaps the OS/2 klibc binaries could be named binkd2k.exe to
ml>> differentiate them from the emx one named binkd2e.exe? the '2'
ml>> indicating OS/2, of course ;)

ml> any thoughts on the above? i pulled one from max's site yesterday
ml> but it has the full name of binkdklibc.exe... that's easy enough
ml> to handle on the OS/2 native side but the file is invisible from
ml> the DOS side of OS/2 :?

TK> The default target in mkfls/os2-emx/makefile.klibc is binkd2e.exe.
TK> Anyone can rename it to whatever. :)

you are right, of course... i was thinking of the official naming convention
mentioned in the FAQ... it would be nice for the emx and klibc stuff to be
named differently for the binary as well as the distribution archive...

for now i use this bit of convoluted 4OS2 code to tell me the version and
flavor of the chosen binkd exe... it gives strings like

Binkd 0.9.6 Oct 28 2003 09:11:27/OS2
Binkd 1.0a-446 watcom Jun 06 2005 21:12:06/OS2
Binkd 1.0a-607 gcc (emx) Feb 20 2012 09:12:20/OS2
Binkd 1.0a-612 gcc (klibc) Jun 18 2012 22:18:08/OS2
Binkd 1.0.0 gcc (emx) Jun 26 2012 11:41:41/OS2
Binkd 1.0.0 gcc (klibc) Jun 23 2012 12:15:46/OS2
Binkd 1.1a-27 gcc (klibc) Jun 1 2013 01:00:19/OS2
Binkd 1.1a-27 gcc (emx) Jun 26 2013 17:04:09/OS2
Binkd 1.0a-612 gcc (emx) Jun 18 2012 16:40:22/OS2

the above last one is a binkd2eo.exe but i don't see anything to tell the
difference between it and non-omf non-multithreaded flavors from the "normal"
emx ones...

4OS2 scripting code follows...

===== snip =====
:chkver
%EXENAME% -v > %EXENAME%.ver
iff %@FILESIZE[%EXENAME%.ver,b] EQ 0 then
echo VER : *NO DATA*
del /q %EXENAME%.ver
else
echo VER : %@LINE[%EXENAME%.ver,0]
%EXENAME% -vv > %EXENAME%.ver.extra
iff %@FILESIZE[%EXENAME%.ver.extra,b] EQ 0 .OR.
%@FILESIZE[%EXENAME%.ver.extra,b] EQ %@FILESIZE[%EXENAME%.ver,b] then
echo EXTRA : *NO DATA*
del /q %EXENAME%.ver.extra
echo %@word[0,%@LINE[%EXENAME%.ver,0]] %@word[1,%@LINE[%EXENAME%.ver,0]]
%@STRIP["()",%@INSTR[%@INDEX[%@LINE[%EXENAME%.ver,0],(],%@LINE[%EXENAME%.ver,0]
]]
else
do cnt = 1 to %@LINES[%EXENAME%.ver.extra]
echo EXTRA : %@LINE[%EXENAME%.ver.extra,%cnt]
enddo
echo %@word[0,%@LINE[%EXENAME%.ver,0]] %@word[1,%@LINE[%EXENAME%.ver,0]]
%@trim[%@word[":,",1,%@LINE[%EXENAME%.ver.extra,1]]]
%@STRIP["()",%@INSTR[%@INDEX[%@LINE[%EXENAME%.ver,0],(],%@LINE[%EXENAME%.ver,0]
]]
endiff
endiff
return
===== snip =====

)\/(ark

[Tommi Koivula]

On 4.8.2013 8:10, mark lewis -> Tommi Koivula wrote:

ml> On Sat, 03 Aug 2013, Tommi Koivula wrote to mark lewis:

ml>>> perhaps the OS/2 klibc binaries could be named binkd2k.exe to
ml>>> differentiate them from the emx one named binkd2e.exe? the '2'
ml>>> indicating OS/2, of course ;)

ml>> any thoughts on the above? i pulled one from max's site yesterday
ml>> but it has the full name of binkdklibc.exe... that's easy enough
ml>> to handle on the OS/2 native side but the file is invisible from
ml>> the DOS side of OS/2 :?

TK>> The default target in mkfls/os2-emx/makefile.klibc is binkd2e.exe.
TK>> Anyone can rename it to whatever. :)

ml> you are right, of course... i was thinking of the official naming
ml> convention mentioned in the FAQ... it would be nice for the emx and
ml> klibc stuff to be named differently for the binary as well as the
ml> distribution archive...

I knew what you meant. ;) But I think it's up to the developers to
change the default .exe name.

'Tommi

[mark lewis]

On Sat, 10 Aug 2013, Tommi Koivula wrote to mark lewis:

ml> you are right, of course... i was thinking of the official naming
ml> convention mentioned in the FAQ... it would be nice for the emx
ml> and klibc stuff to be named differently for the binary as well as
ml> the distribution archive...

TK> I knew what you meant. ;) But I think it's up to the developers to
TK> change the default .exe name.

i'm sorry... i thought you were one of the developers to some degree...

)\/(ark

[Tommi Koivula]

Hello mark!

10 Aug 13 15:39, you wrote to me:

TK>> I knew what you meant. ;) But I think it's up to the developers
TK>> to change the default .exe name.

ml> i'm sorry... i thought you were one of the developers to some
ml> degree...

Nope, I just compile the os/2 executable for myself and share it with anyone
who needs it.

'Tommi

[mark lewis]

On Mon, 12 Aug 2013, Tommi Koivula wrote to mark lewis:

TK>> I knew what you meant. ;) But I think it's up to the developers
TK>> to change the default .exe name.

ml> i'm sorry... i thought you were one of the developers to some
ml> degree...

TK> Nope, I just compile the os/2 executable for myself and share it
TK> with anyone who needs it.

ahh! it is appreciated, that's for sure... do you know of any work done to fix
the bug/crash i posted the other day?

)\/(ark