Daemons and Services
- 1 What are daemons, services and agents?
- 2 Install LazDaemon
- 3 Classes
- 4 Daemon - Step by Step
- 5 Daemon Methods
- 6 Example
- 7 Service Installation
- 8 See also
What are daemons, services and agents?
Unix daemons and Windows services are system-wide programs running without user interaction; macOS agents are per user programs (cf system-wide daemons) that may or may not run without user interaction. Although the nomenclature differs, their function is similar: for example www or ftp servers are called daemons under Linux and services under Windows. Because they do not interact with the user directly, they close their stdin, stdout, stderr descriptors at start.
With Free Pascal, Lazarus it is possible to write these daemons/services platform-independent via the Lazarus lazdaemon package. To avoid name conflicts with the Delphi components these classes are called 'daemons'.
Before you can start, install the lazdaemon package. Either via Components / Configure installed packages or by opening/installing the lpk file directly: lazarus/components/daemon/lazdaemon.lpk. This package installs some new components and menu items in the IDE:
Under File - New: 3 items appear in the dialog, under the heading: "Daemon(service) applications":
This is a TDataModule descendant that does all the work. There can be several TCustomDaemons classes and/or instances running at the same time and in the same process (multi threaded).
This is a TCustomApplication descendant which creates the TCustomDaemons. This does not need any change. It runs under Windows until it receives the Stop call or under Linux until the TERM signal.
This component handles the service registration. Each instance needs one entry in the property DaemonDefs.
Daemon - Step by Step
- When the daemon is started the command line parameters are parsed. The following are predefined:
- -i --install: register the daemon. This has no effect under unix.
- -u --uninstall: unregister the daemon. This has no effect under unix.
- -r --run: start the daemon. Windows does this normally itself.
- Create the TDaemonMapper
- Create one TCustomDaemon for each entry of DaemonDefs.
- install, uninstall or run every instance.
- if run: start every instance in its own thread and then wait for Stop/TERM signal.
- Called when daemon should start. This method must return immediately with True.
- Called when daemon should stop. This method must return immediately with True.
- Called when daemon should be killed. This method must stop the daemon immediately and return with True. This is not triggered under Linux. Linux simply kills the daemon.
- Called when daemon should pause. This method must return immediately with True. Under Linux this is not triggered because the kernel stops the whole daemon on STOP and continues it on CONT.
- Called when daemon should continue after a pause. This method must return immediately with True. Under Linux this is not triggered.
- Called when daemon is registered as a Windows service. This method should return True on success.
- Called when daemon is unregistered as a Windows service. This method should return True on success.
- Called after daemon was unregistered as a Windows service. This method should return True on success.
- Called when a special signal was sent to the daemon. This method should return True on success.
Before you are able to create a Service or Daemon application you must first ensure that the Lazarus Daemon package "lazdaemon" is installed.
There is a simple example in examples/cleandir/. Read the README.txt.
You can install the service by executing the process with the Install parameter. Windows service manager will do the rest for you. You can configure the service and its options from the service manager.
See also: ServiceManager
Linux (only for older Debian)
Download, configure, and "Save As" - the sample script located at Web Archive:  (The original link is dead for a long time).
- SVC_ALIAS is the long description of your application
- SVC_FILENAME is the actual file name of your compiled service application
- SVC_DIR is the place your you copied the service application
- SVC_SERVICE_SCRIPT is the final name of the service.sh when you "Save As" the customized debian-service.sh script.
Place your script in the /etc/init.d/ folder
start the service by running "sudo service Name_Of_Your_Script start"
In order to auto-run the service at startup you can try update-rc.d or else will need a third party tool that will do this.
sudo update-rc.d Name_Of_Your_Script defaults
sudo apt-get install chkconfig sudo chkconfig --add Name_Of_Your_Script sudo chkconfig --level 2345 Name_Of_Your_Script on
systemd (Fedora, Debian, SLES12)
Presently, linux flavors are trending away from differing daemon launching and into a unified service model.
Fedora and SuSE Enterprise Linux Server 12 use systemd and with that commands to start/stop services are the same as on debian but there are differences on the configuration files.
- From the command prompt sudo gedit
- Copy and Paste
[Unit] Description=Long description of your application After=network.target [Service] Type=simple ExecStart=complete_path_and_file_name -r RemainAfterExit=yes TimeoutSec=25 [Install] WantedBy=multi-user.target
- Edit the following values
- Description - Long Description of your service application
- ExecStart - complete-path_and_file_name is the name of your compiled service application with its complete path
- Save As Dialog
- Navigate to /lib/systemd/system/
- Name the file the name_of_your_service.service
- ServiceManager Example for the Free Pascal unit for managing Windows services
- macOS daemons and agents - macOS native using launchd
- Office Automation
- Taming the daemon: PDF by Michaël Van Canneyt
- Useful discussion with small working daemon application
- Docker Containerization - Containerization as a means to create daemons / services easily