Thanks to visit codestin.com
Credit goes to github.com

Skip to content

config file get overwritten by the service #76

@jktjkt

Description

@jktjkt

When I start the daemon, the config file which sets up my routers gets overwritten, enforcing a particular order of statements. Since I'm managing all my config file centrally (via Ansible in my case), I'm seeing constant modifications because my centrally-manged config file has a structure which better fits my needs:

  • I start with defining the target's connection details -- hostname, username, password, etc
  • then I specify which collectors to use

I have not tried this, but I think this config overwriting will also mangle any comments, if used. Generally, I think it's better if a daemon doesn't write to its own config file.

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