Re: auto pre-fill fields issue, posted by Gys Wuyts on Mon Apr 12 14:17:52 2021
|
Super, overlooked that one. Works now
g
| Stefan Ritt wrote: |
|
"Subst xxx" replaces after you submit an entry, while "Preset xxx" replaces before you create an entry. I believe you want the second one.
Stefan
| Gys Wuyts wrote: |
|
[global]
port = 8080
ssl = 0
Password file = passwords.txt
Admin user = user1
SMTP host = smtp. mail.com
SMTP port = 25
SMTP username = user1@mail.com
SMTP Password = GIwbx7UbmkWs5J0P8lVztX7Anje0/21BU/Tmk0aPm.
Logfile = ELog_log.txt
Logging level = 3
[Server]
Logbook dir = Server
Theme = default
Comment = Server Change Log
Attributes = Author, Email, Type, Category, Subject
Subst Author = $long_name from $remote_host
Subst Email = $user_email
Options Type = SRV 1, SRV 2, SRV Sup, BMS content, BMS setpoints, BMS new
Options Category = Config, User, Access, Connection, Change, New, Delete
Extendable Options =
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
| Andreas Luedeke wrote: |
|
If you would post a minimal config file where the problem occurs, then we could look what the problem is.
| Gys Wuyts wrote: |
|
Thank you but that is already in place. I have the same issue on both Windows 10 and Windows Server 2016 and 2019.
tnks
g
| Stefan Ritt wrote: |
|
You need user-level access control, using
Password file = ...
Stefan
| Gys Wuyts wrote: |
|
Hello,
what are the pre-requisites to automatically fill the Author and Author Email fields. The documented method:
Subst Author = $long_name from $remote_host
Subst Email = $user_email
in the elogd.cfg file does not seem to work.
(I see it works here on this platform)
Tnks
G
|
|
|
|
|
|
|
"User stamp" icon like Time Stamp in Body, posted by Gys Wuyts on Tue Apr 12 08:55:55 2022
|
Hello,
Is there a possibility to use like the time stamp a user stamp: by clicking the button in the main text entry it adds the username, just like the time stamp button does: Tue Apr 12 08:58:46 2022 ?
I searched but I'm not sure how this would be correctly named.
Thanks,
G |
Step by step AD/Kerberos authentication setup, posted by Gys Wuyts on Fri May 26 13:48:14 2023
|
Newby/noob Q: anybody have a resource other then the orignal doc on how to get ELog working using the domain users/passwords with a Win2K19 AD |
|
Step by step AD/Kerberos authentication setup, posted by Gys Wuyts on Fri May 26 13:51:16 2023
|
Newby/noob Q: anybody have a resource other then the orignal doc on how to get ELog working using the domain users/passwords with a Win2K19 AD ?
thanks
G |
|
Running elog as ordinnary user, posted by G. Vandemoortele on Fri Jan 27 20:40:00 2006
|
Hello,
I've configured elog with some commands running a shell :
Preset R-Date = $shell(/usr/bin/date +"%Y/%m/%d %H:%S")
; for testing :
Preset $text = $shell(whoami && set)
Preset $text = Some fixed text
That worked well when elog was started by root (and falling to user elog),
but later, I moved all the elog tree to /home/my_name/.elog,
(I'd like to start it only when I'm logged, it's only for personnal data)
changed all the attributes/permissions ($chown -R my_name:my_group .elog)
and none of these commands still works ! I use the -x option to allow
shell substitution.
More surprisingly, even the fixed text doesn't work (???)
Any explanation ?
By the way, I also seen that it is necessary to set Usr and Grp to "elog"
via the config file even when it's started by root, because otherwise,
you always get the strings 'Falling back to default group "elog"' and
Falling back to default user "elog" in the output of the shell substitutions.
Regards,
Gauthier
|
|
Re: Running elog as ordinnary user, posted by G. Vandemoortele on Sat Jan 28 10:40:18 2006
|
| Stefan Ritt wrote: |
First of all, you could use
Preset R-Date = $date
instead of the shell command. Secondly, the command
Preset $text = $shell(whoami && set)
is wrong. Replace it by
Preset text = $shell(whoami && set)
without the "$".
|
I'm sorry ; even with this correction, none of the preset strings created with
a substitution mechanism (shell or built-in) works when elogd is started as
ordinnary user. I've tried the same config file /home/gv/.elog/elogd.cfg :
port = 8080
Language = french
Main Tab = Accueil
Usr = gv
Grp = users
Logbook dir = /home/gv/.elog/logbooks
[gauthier]
Self register = 1
Password file = passwd
Theme = default
Comment = Logbook personnel
Default encoding = 1
Time format = %a, %d/%m/%Y %H:%M
Attributes = Type, Statut, Priorité, Sujet, R-Date
Preset R-Date = $shell(/usr/bin/date +"%Y/%m/%d %H:%S")
Preset text = $shell(whoami && set)
;Preset text = Blablabla
;Preset text = $date
Start page = ?rsort=Record date
List display = R-Date, Type, Statut, Priorité, Sujet
Options Type = Divers, Lectures, Musique, Aca, Finances, Santé
Options Statut = A faire, Exécuté, Journal
Options Priorité = 0, 1, 2, 3
Preset Priorité = 0
Extendable Options = Type
Thread display = $sujet ($entry time)
Required Attributes = Type, Sujet
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = R-Date, Statut, Type
Sort Attributes = Priorité, R-Date
Started via root (# /usr/sbin/elogd -c /home/gv/.elog/elogd.cfg -x), it works,
but via "gv" ($ /usr/sbin/elogd -c /home/gv/.elog/elogd.cfg -x), it doesn't.
Regards,
Gauthier |
|
Incrementation of attribute is not functioning, help needed to fix this., posted by Guido Böing on Wed Jan 28 18:30:03 2009
|
Hello all,
I appear to be doing something wrong or not..
In my configuration I use an incrementation of a certain attribute (Melding)
For some weird reason it won't increment in this place, while it does in another place...
Below is my configuration (at least the part that gives me headaches..)
[Onderhoud Diversen]
Theme = default
Attributes = Melding, Auteur, Type, Planning, Categorie, Status, Onderwerp
Options Type = Preventief, Regulier, Nav Storing, Overig
Options Categorie = SensorProbes, Overig
Options Status = Wachtend, Gepland, In behandeling, Update, Afgerond
Type Planning = date
Extendable Options = Categorie, Status
Required Attributes = Auteur, Type, Unit-Lokatie, Status
Page Title = ELOG - $onderwerp
Reverse sort = 1
Quick filter = Date, Type, Status
Preset Melding= DIVOH: %d%m%y-####
Subst on edit Auteur = $long_name
List Display = ID, Melding, Datum, Status, Auteur, Type, Planning, Categorie, Onderwerp
Summary lines = 0
Display Email recipients = 0
Email All = aapie@sukkeltje.com
Use Email Subject = $Melding, $Onderwerp - $Status
Style Status In behandeling = background-color:red
Style Status Update = background-color:orange
Style Status Afgerond = background-color:lime
Login user = person1, person2
The goal of this part of the configuration is a way to notify and log maintenance on not specified equipment.
I expect a message-tag with: DIVOH: 280109-0001, where 280109 stands for 28th of January, 2009, the 0001 is the message number of that day.
Now when I enter something in it, submit the message it will display DIV-OH: 280109-0001 as I expect, but...
When I start with a new entry I would expect DIVOH: 280109-0002 as it is the second message.. Well, simply put.. I don't get DIVOH: 280109-0002 but instead I get DIVOH: 280109-0001 again.Below the part that does work correctly:
The following part of my configuration does work..
[Onderhoud Windows]
Theme = default
Attributes = Melding, Auteur, Type, Planning, Categorie, Status, Onderwerp
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Categorie = Algemeen, Hardware, Software, Netwerk, Telefonie, Overig
Options Status = Wachtend, Gepland, In behandeling, Update, Opgelost
Type Planning = date
Extendable Options = Categorie, Status
Required Attributes = Auteur, Type, Status
Page Title = ELOG - $onderwerp
Reverse sort = 1
Quick filter = Date, Type, Status
Preset Melding= WSOH: %d%m%y-####
Subst on edit Auteur = $long_name
List Display = ID, Melding, Datum, Status, Auteur, Type, Planning, Categorie, Onderwerp
Summary lines = 0
Style Status In behandeling = background-color:red
Style Status Update = background-color:orange
Style Status Afgerond = background-color:lime
When I copy this one, adjust it to be the same as the first one, but then without the extra things it doesn't work, and with them, well.. it still won't.. :(
I am at a loss here where the mistake is, can someone shed some light on this? I would appreciate that very much.
Best regards,
Guido
|
|
chain.crt, posted by Gerhard Schneider on Thu Sep 3 21:55:52 2009
|
Like many educational institutions we get "educational certificates" that are chain certificates..
With apache the full certificate chain is working as expected..
For elog I copied the appropriate files to server.crt and server.key
Netscape 3 is happy with that setup, Internet Explorer and Opera are mentioning the open certificate chain.
When I tried to copy the file known as SSLCACertificateFile in Apache to chain.crt elogd does not longer work and
openssl s_client -showcerts -connect <myserver>:<elogd_port>
only shows:
CONNECTED(00000003)
25523:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:s23_clnt.c:562:
What do I do wrong?
Gerhard Schneider |
|