ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67763
|
Mon Jan 26 10:30:40 2015 |
| Maikolk Kein | javier.sanchez@wincor-nixdorf.com | Question | Linux | 3.0.0 | Kerberos auth not available on 3.0 ? |
Hi all !!!
i have just updated and 2.9.2-1 elog instance, and i have problems with the kerberos configuration.
I was surprised to see on the logs, that the 3.0 daemon was refusing to start because the system
config has kerberos listed as an authentication method. I saw on the logs that the current daemon
didnt have kerberos support compiled in.
Ive seen that there is ldap support, but couldnt find anything about configuring this auth sytem, does
amnyone have any example i could check ?
Did i have to use a patched version ? or compile it on my own ?
Regards |
67764
|
Mon Jan 26 15:04:38 2015 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 3.0.0 | Re: Kerberos auth not available on 3.0 ? |
Hi Maikolk,
I have elogd 3.0 running with kerberos: I had no problems with that.
Maybe you forgot to change the Makefile before compiling?
Uncomment line 28 to:
# flag for Kerberos support, please turn on if you need Kerberos
USE_KRB5 = 1
and then "make clean" and "make install" (or "make update").
Regards, Andreas
Maikolk Kein wrote: |
Hi all !!!
i have just updated and 2.9.2-1 elog instance, and i have problems with the kerberos configuration.
I was surprised to see on the logs, that the 3.0 daemon was refusing to start because the system
config has kerberos listed as an authentication method. I saw on the logs that the current daemon
didnt have kerberos support compiled in.
Ive seen that there is ldap support, but couldnt find anything about configuring this auth sytem, does
amnyone have any example i could check ?
Did i have to use a patched version ? or compile it on my own ?
Regards
|
|
67765
|
Mon Jan 26 15:06:49 2015 |
| Maikolk Kein | javier.sanchez@wincor-nixdorf.com | Question | Linux | 3.0.0 | Re: Kerberos auth not available on 3.0 ? |
No no, i used the rpm form the website... I was thinking on having the bianries compiled, im downloading the server install dvd
to replicate the environment and have the same functionality.
Thanks for the answer ;-)
Regards
Andreas Luedeke wrote: |
Hi Maikolk,
I have elogd 3.0 running with kerberos: I had no problems with that.
Maybe you forgot to change the Makefile before compiling?
Uncomment line 28 to:
# flag for Kerberos support, please turn on if you need Kerberos
USE_KRB5 = 1
and then "make clean" and "make install" (or "make update").
Regards, Andreas
Maikolk Kein wrote: |
Hi all !!!
i have just updated and 2.9.2-1 elog instance, and i have problems with the kerberos configuration.
I was surprised to see on the logs, that the 3.0 daemon was refusing to start because the system
config has kerberos listed as an authentication method. I saw on the logs that the current daemon
didnt have kerberos support compiled in.
Ive seen that there is ldap support, but couldnt find anything about configuring this auth sytem, does
amnyone have any example i could check ?
Did i have to use a patched version ? or compile it on my own ?
Regards
|
|
|
67772
|
Tue Jan 27 17:16:46 2015 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.0.0 | Re: Kerberos auth not available on 3.0 ? |
Kerberos support is not compiled into the binary RPM. You have to comile from sources to get that. The reason is that there are different Kerberos libraries around, and different people need different ones.
/Stefan
|
67811
|
Fri Feb 20 11:04:03 2015 |
| rob | rob@5db.nl | Question | Linux | 2.7.1 | maximum attributes for drop down menu. |
We use a servername field to be able to select a server.
When i entered my entire serverlist (574 entries), only 250 of them show up.
Looking at the online documentation about attributes, it is stated that there is a maximum of 100 entries.
With the version we are using (2.7.1) it seems the limit is 250
Can someone tell me if version 3 has the same limitation, or that the max has been increased?
Rob. |
67812
|
Fri Feb 20 16:18:36 2015 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Linux | 2.7.1 | Re: maximum attributes for drop down menu. |
Hi Rob,
I don't think the default number of 100 has ever changed. However, you can change the number in the source
code and recompile. This was discussed in elog:67674
I increased my maximum from 100 to 120 and recompiled. At some point, though, you'll overflow some stack or other, and maybe that's why you've got the limit of 250. You might also want to consider Andreas's alternative (which I am also thinking about).
rob wrote: | We use a servername field to be able to select a server.
When i entered my entire serverlist (574 entries), only 250 of them show up.
Looking at the online documentation about attributes, it is stated that there is a maximum of 100 entries.
With the version we are using (2.7.1) it seems the limit is 250
Can someone tell me if version 3 has the same limitation, or that the max has been increased?
Rob. |
|
67856
|
Wed Apr 8 11:40:27 2015 |
| Oliver Kleinau | oliver.kleinau@it.niedersachsen.de | Question | Linux | 3.1 | Max Logbooks for Email notify |
Hi,
we've got 109 logbooks in Elog. Whenever I set a notify for all logbooks in configuration menu it is limited to 73 entrys. After saving the changes the rest of the entrys are cut off.
I've already searched in the sourcecode if I can find some limitation for that but without success.
When I change the password file by hand, it is working as long as I don't change anything in the configuration that rewrites the file.
Regards,
Oliver
|
67857
|
Fri Apr 10 08:37:19 2015 |
| Oliver Kleinau | oliver.kleinau@it.niedersachsen.de | Question | Linux | 3.1 | Re: Max Logbooks for Email notify |
It seems to be the GET buffer of the elog-Server. The GET statement is cut off after &sub_lb72=1&sub_ eg. 1000 chars.
Oliver Kleinau wrote: |
Hi,
we've got 109 logbooks in Elog. Whenever I set a notify for all logbooks in configuration menu it is limited to 73 entrys. After saving the changes the rest of the entrys are cut off.
I've already searched in the sourcecode if I can find some limitation for that but without success.
When I change the password file by hand, it is working as long as I don't change anything in the configuration that rewrites the file.
Regards,
Oliver
|
|