-
Notifications
You must be signed in to change notification settings - Fork 15
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
Bind file not actually loading on start #11
Comments
Good find, I have only tested making changes in /etc/g13/default.bind so it has not occured to me the loading might fail |
To be clear that is the file I am passing to |
I haven't had any issues loading config (apart from the comment thing) using the included bindfiles examples and can't see any reference to /etc/g13/default.bind - this has to be explicitly passed, right? What are the contents of your default.bind file? |
I tried putting only binds in it (no comments or other commands) and it still didn't work. Yes it is being passed via |
This should be quite easy to test with verbose debugging turned on. I can not access my Arch Linux right. I decided to work on my thesis in FreeBSD as Arch is full of distractions... like work on g13d... which I also have looked into porting to FreeBSD but try really hard not to look at right now |
I did turn on verbose debugging (assuming that's what |
I'm happy to take a look, but as I said, I am unable to reproduce the issue - it's working fine for me (in PopOS, a Ubuntu derivative). I could fire up Arch in Vagrant to see if it's distro related, but this is pretty low level file reading? I don't see how. |
I tried |
Yes, both relative and absolute worked for me. I even created one in /etc/g13/default.bind |
I tried |
There's not actually any further debug messages produced in that branch of code, maybe we could add something like: |
Hello, I don't understand how you do to pass your command. I use script to run different config like this:
|
Simple as that. The bind file passed via
--config
is not actually loading, despite the log claiming that it is. I enabled DEBUG and didn't get anything more than this:The text was updated successfully, but these errors were encountered: