Currently, all Request object are always owned by Manager, and freed when it is processed, especially, soon after a netlink message is sent. So, it is not necessary to introduce the reference counter. In a later commit, the Request object will _not_ be freed at the time when a netlink message is sent, but assigned to the relevant netlink slot as a userdata, and will be freed when a reply is received. So, the owner of the Request object is changed in its lifetime. In that case, it is convenient that the object has reference counter to avoid memleak or double free.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.
