DaemonSystemdInstallerUnit

[Чебурашка]

Hello,
 
the unit DaemonSystemdInstallerUnit mentioned in

https://wiki.freepascal.org/Daemons_and_Services

that is supposed to create the systemd control files, is also part of the deamon stuff units or is it a custom unit belonging to the writer of the article?

I did not find in my filesystem.

[Thaddy]

That wiki entry is ,well, not very good.
Stick with:

from the official FPC documentation here:
https://www.freepascal.org/docs-html/current/fcl/daemonapp/tdaemoncontroller.html

The example in the fcl-extra directory here:
packages\fcl-extra\examples

and this article by Michael van Canneyt here:
https://www.freepascal.org/~michael/articles/#daemons (also covers Windows services)

and ignore the wiki. (well, it is not that bad and may help you a bit when you first read and understand official sources).
The wiki is an abberation of "components" where there need not be components at all, just classes. You can just as well turn 'Hello, World' into a component < sigh>, but OTOH it may be that Michael also contributed a bit to the wiki to keep at least some control...
(And yes, Michael's articles are an official source)

[Чебурашка]

That wiki entry is ,well, not very good.
Stick with:

from the official FPC documentation here:
https://www.freepascal.org/docs-html/current/fcl/daemonapp/tdaemoncontroller.html

The example in the fcl-extra directory here:
packages\fcl-extra\examples

and this article by Michael van Canneyt here:
https://www.freepascal.org/~michael/articles/#daemons (also covers Windows services)

and ignore the wiki. (well, it is not that bad and may help you a bit when you first read and understand official sources).
The wiki is an abberation of "components" where there need not be components at all, just classes. You can just as well turn 'Hello, World' into a component < sigh>, but OTOH it may be that Michael also contributed a bit to the wiki to keep at least some control...
(And yes, Michael's articles are an official source)

Thanks, in reality I had no problem in writing a deamonized application (and as you say I did it just looking at the sources/pdfs). Only now I also need this deamon to get along with systemd and I was wondering if the cited unit is public or not, so that I don't have to create a custom tool to generate systemd configuration files.

From your answer I understand it is not public. 

[dbannon]

The content you are looking for (I think) is in an example included with trunk but not yet the release versions of Lazarus.

If you are not using Trunk, the content can be found here - https://gitlab.com/dbannon/laz_examples/-/tree/main/General/TDaemon

Davo

[Чебурашка]

The content you are looking for (I think) is in an example included with trunk but not yet the release versions of Lazarus.

If you are not using Trunk, the content can be found here - https://gitlab.com/dbannon/laz_examples/-/tree/main/General/TDaemon

Davo

Thank you.

[AlexTP]

Added the found URL to the wiki topic.

[Чебурашка]

At the end what I did was:

- make the daemon (easy, just see the examples)
- create a systemd config file and make sure to have:

Code: INI  [Select][+][-]

1. [Unit]
2. Description=TT daemon
3.  
4. [Service]
5. Type=forking
6. WorkingDirectory=/home/user_tt/.tt_daemon
7. ExecStart=/usr/local/bin/tt_daemon -r -b
8. User=user_tt
9. Group=users
10.  
11.  

- the option -r in the ExecStart line tells the daemon to run
- the option -b in the ExecStart line tells the daemon created with fpc to daemonize itself = fork and become background process
- the Type=forking is designed to deal with processes capable of daemonizing

in alternative

Code: INI  [Select][+][-]

1. [Unit]
2. Description=TT daemon
3.  
4. [Service]
5. Type=simple
6. WorkingDirectory=/home/user_tt/.tt_daemon
7. ExecStart=/usr/local/bin/tt_daemon -r
8. User=user_tt
9. Group=users
10.  
11.  

- skip the option -b in the ExecStart so that the daemon will start and not daemonize itself (it will keep runnig until stopped from outside or it crashes)
- in this case I have to use Type=simple (is the default) which is designed to deal with processes that do not daemonize, and systemd will go ahead with other services without being locked by my process.