Summary

BDS does not respond to standard server signals.

Steps to reproduce... (windows)

1. Download and unzip BDS
2. Download and unzip NSSM
3. Configure BDS as a service and start - ensure you enable logging for easiest eval
4. Stop the service using cmd/powershell/services.msc
5. Note in the log that the server immediately terminates rather than running a safe shutdown

What I expected to happen...

BDS should handle the termination signal gracefully to allow BDS to be configured as a service.

What actually happened...

Server immediately terminated, risking corruption etc.

How this affects admins

At the moment its possible to configure BDS as a service and it works without issue. However when restarting the host or even just the service, it terminates immediately causing an unsafe shutdown and risking corruption.