Native signals that can be hooked. There arn't all linux native signals due safety. * Most not listed signals are already binded by druntime (sigusr1 and sigusr2 are occupied by garbage collector) and rebinding cause a program hanging or ignoring all signal callbacks. * You can define your own signals by customSignal function. These signals are mapped to realtime signals in linux. * Note: Signal enum is based on string to map signals on winapi events.
Creating your own custom signal. Theese signals are binded to realtime signals in linux and to winapi events in Windows. *
* Signal OR composition. * * If you'd like to hook several signals by one handler, you * can use the template in place of signal in KeyValueList * signal map. * * In that case the handler should also accept a Signal value * as it second parameter.
Template for describing daemon in the package. * To describe new daemon you should set unique name and signal -> callbacks mapping. * name is used to name default pid and lock files of the daemon and also it is a service name in Windows. * pSignalMap is a KeyValueList template where keys are Signal values and values are delegates of type:
Truncated description of daemon for use with sendSignal function. You need to pass a daemon name and a list of signals to Signals expression list. *
Checks if T is a composition of signals
Duck typing Daemon description
Duck typing of DaemonClient
Platform independent parts of the library. Defines common signals that safe to catch, utilities for describing daemons and some utitility templates for duck typing. *