gpioctld: system daemon controlling GPIOs about libgpiod

[zeekhuge]

Hi ! I would like to help here. Can you please guide me ?

[brgl]

Hi @zeekhuge,

I have already started working on that. I currently need to get it to the point where it has at least basic functionalities, then I'll push a development branch (features/daemon probably) on which collaborative work can start.

What I have now is epoll-based daemon listening on multiple sockets (client connections, gpio events, signals etc.). I'm using libconfig for configuration files and libprotobuf-c for communication between the client application and the daemon.

[clemensg]

Hi @brgl,

I have a similar use case. I currently use a hash table with a pointer to each gpiod_line I need to manage from a daemon.
The chips need to stay open during the runtime of the daemon for this to work (see my PR #11). I close them at the end. With this, I can open the chips and request the lines at daemon startup act and react to various events, get and set gpios by name during the daemon runtime and close them at daemon exit.

Maybe PR #11 could be useful for your features/daemon branch too? Or do you have an alternative approach in mind to avoid opening and closing the chips for each action?