Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

augeas: use checkconf #977

Closed
markus2330 opened this issue Sep 21, 2016 · 1 comment
Closed

augeas: use checkconf #977

markus2330 opened this issue Sep 21, 2016 · 1 comment
Assignees

Comments

@markus2330
Copy link
Contributor

Describe what you wanted to do

Mount an augeas plugin by giving the .aug filename, e.g.:

kdb mount /etc/network/interfaces system/network/interfaces augeas lens=interfaces.aug
kdb mount /etc/network/interfaces system/network/interfaces augeas lens=/usr/share/augeas/lenses/dist/interfaces.aug

Describe what you expected

That augeas checks its configuration via checkconf at mount time and rejects (or at least warn) wrongly specified lenses. (Or even better: rename "interfaces" or "interfaces.aug" to "Interfaces.lns").

Describe what actually happened

Mount is successful, but the mountpoint does not work:

kdb ls system/network/interfaces
The command ls failed while accessing the key database with the info:
Error (#85) occurred!
Description: an Augeas error occurred
Ingroup: plugin
Module: storage
At: /home/jenkins/workspace/workspace/elektra-git-buildpackage-jessie/libelektra/src/plugins/augeas/augeas.c:461
Reason: Lens not found
Mountpoint: system/network/interfaces
Configfile: /etc/network/interfaces

The error message also does not show which Lens was tried.

System Information

  • Elektra Version: master
  • libaugeas 1.2.0-0.2+deb8u1

Further Log Files and Output

For Infos about checkconf see:

  • doc/help/elektra-plugins-framework.md
  • src/plugins/doc/doc.c
  • doc/tutorials/plugins.md
@markus2330
Copy link
Contributor Author

As discussed in #1006 we also need a way for to list every possible configuration for augeas plugins. Can you also implement a way to query every possible configuration?

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants