Win32: stopping binkd (non-service)

[Scott Little]

Hi All,

When running BinkD in server mode but not as a Windows service, is there a way
to get it to exit a) unattended (by script), and b) gracefully (ie. stop
creating/accepting new sessions, complete any open sessions)? eg. semaphore
file, Windows event.

tskill/taskkill and such seem to only terminate it forcefully.

[Andrew Leary]

Hello Scott!

Wednesday June 18 2014 21:59, Scott Little wrote to All:

SL> When running BinkD in server mode but not as a Windows service, is
SL> there a way to get it to exit a) unattended (by script), and b)
SL> gracefully (ie. stop creating/accepting new sessions, complete any
SL> open sessions)? eg. semaphore file, Windows event.

SL> tskill/taskkill and such seem to only terminate it forcefully.

At this point there isn't a way to do it. I've been wanting this for quite a
while on the OS/2 version; but as of yet nobody has done it.

Andrew

[Tommi Koivula]

On 18.6.2014 14:59, Scott Little -> All wrote:

SL> When running BinkD in server mode but not as a Windows service, is there
SL> a way to get it to exit a) unattended (by script), and b) gracefully
SL> (ie. stop creating/accepting new sessions, complete any open sessions)?
SL> eg. semaphore file, Windows event.

SL> tskill/taskkill and such seem to only terminate it forcefully.

The cygwin compilation seems to die gracefully with
"\cygwin\bin\kill.exe @binkd.pid" :

19 Jun 10:59:34 [5620] BEGIN, binkd/1.1a-49/CYGWIN_NT-5.1 binkd.cfg
19 Jun 10:59:34 [5620] created binkd.pid
19 Jun 10:59:34 [5620] servmgr started
19 Jun 10:59:34 [2744] clientmgr started
- 19 Jun 10:59:37 [5620] servmgr listen on localhost:24554
! 19 Jun 10:59:59 [5620] got signal #15. Killing 2744 and quitting...
19 Jun 10:59:59 [5620] Closing server socket # 3
! 19 Jun 10:59:59 [2744] got signal #15.
19 Jun 10:59:59 [5620] Closing server socket # 4
19 Jun 10:59:59 [5620] Closing server socket # 5
19 Jun 10:59:59 [5620] Closing server socket # 6
19 Jun 10:59:59 [5620] unlinked `binkd.pid'

'Tommi