[global]
Welcome Title = <div style="text-align: center;">log-book.</div>
; Se puede poner un vinculo havcia un sitio web y cambiar la imagen
; Esta imagen debe encontrarse en el directorio \ELOG\themes\default
Title image = <img border=0 src="logo.gif">
; Para mas seguridad se puede cambiar el puerto de ELOG
port = 2
;Uso de https para la connexion
SSL = 1
; Se debe reemplazar estos datos con los datos del servidor de mail de la empresa si se debe (o quiere) mandar emails
SMTP host = toto.com
Language = spanish
Main Tab = Accueil
Bottom text = <div style="text-align: center;">Elog backups <img src="logo.png"></div>
Email format = 111
logfile = Archivo_de_logs.txt
Logging level = 2
;Display mode = threaded
; Los usuarios deben crear una cuenta para poder utilizar la nueva herramienta
Password file = Usuarios.txt
Self register = 2
; La contraseña nominal es: admin, se puede cambiar si necesario
Admin user = administrador
; Si se quiere restringir los derechos de delete
Allow Delete = administrador
; Si se quiere restringir los derechos de modificacion
; Allow Edit = administrador
; Si se quiere restringir los derechos de créacion
; Allow New = administrador
Menu commands = List, Find, New, Delete, Reply, Logout, Help
List Menu commands = Find, New, Logout, Help
Guest Menu commands = List, Find, Login, Help
Guest List Menu commands = Find, Login, Help
[Backups del sistema]
Theme = default
Comment = test backup - Logbook Program
Welcome title = <img src="logo.gif"><p><font size=5 color=white>Welcome to our Elog</font>
Attributes = Usuario, Tarea, Fecha Operacion, Status, Subsistema, Base de Datos
IOptions Status= "Delete-icon.png", "Check-icon.png"
Icon comment Delete-icon.png = Failed
Icon comment Check-icon.png = OK
Thread Icon = Status
Thread Display = $Fecha Operacion,$Tarea,$Subsistema
Locked Attributes = Usuario
Required Attributes = Usuario, Tarea, Fecha Operacion, Status, Subsistema, Base de Datos
Preset Usuario = $long_name
Options Tarea = Backup, Restore
Options Subsistema = DBMGR {a}, MCH {b}, ALL {c}
{a}MOptions Base de Datos = ALL BASES, base1, base2, base3, base4
{b}MOptions Base de Datos = ALL, BD1, BD2, BD3
{c} Locked Attributes = Usuario
{c} Show Attributes Edit= Usuario, Tarea, Fecha Operacion, Status, Subsistema
{c} Required Attributes = Usuario, Tarea, Fecha Operacion, Status, Subsistema
Message comment = Commentarios:
Type Fecha Operacion = date
Preset Fecha Operacion = $date
Mode commands = 1
Display Mode = threaded
Page Title = Backups del sistema - $subject
;Reverse sort = 1
;Quick filter = Date, Tarea, Subsistema
|
Hi again,
I was wondering if one could use a conditional statement on an IOption attribute? Indeed i try to do a visual logbook (a green check for OK result, a red cross for NOK result), unfortunately i cannot refer to the attributes value for conditional test, e.g:
IOptions Status= "Delete-icon.png" {1}, "Check-icon.png"{2}
Icon comment Delete-icon.png = Failed
Icon comment Check-icon.png = OK
{1} Show Attribute Edit = Attribute1, Attribute2
Thread Icon = Status
Attribute1 and 2 do not have any sense if the result was successful,
ELOG interprets the {1} and {2} as being part of the icon name!
thanks again for your help
FX |
We recently installed ELOG and it works pretty well, but the load times are rather inconsistent. Most of the time
it is very fast, but it also often hangs for around 5-10 seconds while loading. It seems to affect all parts of
the page that are returned at random, so sometimes the main html file will hang, sometimes the css file and
sometimes the images.
The hardware it is running on is nothing special, an older 3 GHz Celeron, but it should be fast enough. It is
running on Debian 7.
Any ideas what the problem could be, or how I could investigate it further to find the bottleneck? |
Hi guys,
we configured a kdc server using OPENLDAP as backend. We installed on it elog and configured the Kerberos Authentication on one logbook as follows:
Authentication = Kerberos, File
Kerberos Realm = TEST.COM
Password file = ./pwd.xml
⇄
Detect language » Italian
Even if the kinit comand is retrieving correctly a ticket for the user tsearch@TEST.COM(we see it using klist and tcpdump on lo interface), elogd kerberos authentication is not working.
We tried using tcpdump for troubleshooting but no traffic is generated on the loopback interface.
Did someone solve this problem or do you have an idea on how to make the kerberos authentication working?
Thanks |
I would like to know, if the command "Admin restrict edit time = " does really work as intended.
In my case I have the following global configuration:
Admin user = <me>
Restrict edit = 1
Restrict edit time = 1
Admin restrict edit time = 10000
And every time, when I want to edit an entry (as admin), that is older than 1 hour, i get the following error message:
"Entry can only be edited 1 hours after creation"
|