-
Notifications
You must be signed in to change notification settings - Fork 26
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
Not reading all the options in config file #39
Comments
so sorry about the late reaction - I have to admit I've never worked with a keyring, I'm gonna have to try and reproduce this and see what happens. if you could give me a simple recipe on how to setup a keyring, I would really appreciate that (also - do i have to use gnome for the keyring thingy to work?) i'm not sure I follow your last comment, about the port - you had to leave the port option empty? if you write 443 there, it get's messed up? gonna check that out! just give me a few more days please, hopefully i will find some time to look at this. |
I am using gnome keyring. So if you use bonfire with
so I would like to be able to execute: Forget about the port, it looks fine. Cheers. |
alrighty i'm finally looking at this.
gonna look at the keyring next - do i understand correctly that it works fine when you use the command line option, the only problem is that you cannot supply it in the config file, and you would like to be able to do that? |
and would you like to supply the keyring option on a node to node basis, or should we add a new |
sorry, you caught me on vacation. |
hi,
I am using the RC2 and it doesn't read keyring and follow options asI have them here:
Also, since my graylog server is running on 443, I had to leave it empty, otherwise it is malforming a URL like
graylog.domain.com
The text was updated successfully, but these errors were encountered: