Skip to content

add support for include directives #36

@zach-welch-aquabyte

Description

@zach-welch-aquabyte

I have an embedded system with a read-only filesystem, so the base configuration file cannot be edited. In another context, I might have a system that could install several optional services, each of which might need to install its own configuration fragment for rinetd.

To support these use cases, I propose adding a new include directive. This would permit adding lines similar to the following, allowing configuration fragments to be stored in a multiple separate locations.

include /etc/rinetd.d/extra-rules.conf
include /data/rinetd.d/*

If globs end up being too big an ask, a simpler directive for scanning a directory would probably be more than sufficient (e.g. includedir /path/without/globs/).

After a quick glance at the parser definition, this seems like a reasonable extension that would be fairly easy to implement (for someone that knows that code). Notably, the parseConfiguration routine simply would be called recursively by the rules that implement the include directive(s). Easy peasy, yeah?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions