https://github.com/idanrosenzweig/daemond

Infrastructure for managing daemons, services, and systems. Suitable for development environments, servers, cloud services, IoT devices, and more. Offers greater flexibility and convenience compared to other daemon managers.
https://github.com/idanrosenzweig/daemond

c cpp daemon-manager design-patterns inter-process-communication linux serialization service-manager

Last synced: about 1 month ago
JSON representation

Infrastructure for managing daemons, services, and systems. Suitable for development environments, servers, cloud services, IoT devices, and more. Offers greater flexibility and convenience compared to other daemon managers.

• Host: GitHub
• URL: https://github.com/idanrosenzweig/daemond
• Owner: IdanRosenzweig
• Created: 2024-07-07T05:59:35.000Z (6 months ago)
• Default Branch: master
• Last Pushed: 2024-07-08T12:35:36.000Z (6 months ago)
• Last Synced: 2024-07-09T10:08:12.960Z (6 months ago)
• Topics: c, cpp, daemon-manager, design-patterns, inter-process-communication, linux, serialization, service-manager
• Language: C++
• Homepage:
• Size: 44.9 KB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: readme.md

Awesome Lists containing this project

README

        
# Daemond

## overview

Daemond is an infrastructure for managing daemons, services, and systems. It can be utilized for overseeing development environments, servers, cloud services, IoT devices, container orchestration, and more.

Daemond operates using the concept of units, representing any daemon, service, or system that it can control and manage, similar to systemctl units.

Supporting modern C++ for specifying units, Daemond offers greater flexibility and convenience compared to other popular daemon managers that rely on their own text file syntax.

## architecture

Daemond is composed out of two components:

* the main `daemond` program, which internally manages units

* `daemond_ctl`, a companion program providing easy access and querying of the main `daemond` program. this combination is similar to the way `systemd` and `systemctl` interact.

in order to use Daemond:

1. run the main `daemond` program on the machine (in the background or separate process etc...)

2. specify various units in any file you want

3. run the `daemond_ctl` program which will interact with the `daemond` program (via various communication channels like).

## usage

Daemond supports the following operations on units:

* load a unit (preparing it)

* start a loaded unit

* stop a loaded unit

* query the status of a unit

* unload a unit

all of these operations can be done using the `daemond_ctl` program.

## unit specification

look at the struct under `src/abstract/unit/data/unit_data.h`. to specify a unit that can be manged by `daemond`, write any valid C++ source file that contain a `unit_data` struct named `unit`, with your own values in it.

you can look at sample units under `samples`.

## build

to build the daemond program, execute `./build.sh daemond`. the `daemond` program will be found under `build` directory.

to build the daemond_ctl side program, execute `./build.sh daemond_ctl`. the `daemond_ctl` program will be found under `build` directory.

to clean all builds, execute `./build.sh clean`.

## samples

the project contains sample units found under `samples`.

to start one of these units:

1. build `daemond` and `daemond_ctl`

2. execute `daemond` in the background

3. to load the unit, execute `daemond_ctl -c load -p samples/unit_name`

4. to start the unit, execute `daemond_ctl -c start -p samples/unit_name`

## dependencies

Daemond uses the `libboost` library for serialization of data and for command line parsing. make sure you have libboost when compiling the project.

## future TODOs

* add support for unit dependencies

* add netlink IPC channel to integrate with kernel level code

* add external network IPC channel to integrate with remote systems

* add support for Windows