Date conversion, posted by Martin Neumann on Tue Feb 23 12:12:14 2021
|
Hi,
I am trying to figure out how ELOG works and I have a problem.
I have one datetime attribute, where I want the user to be able to enter the time in ISO8601 format (YYYY-MM-DD HH:MM) instead of the buttons.
How do I manage that this input is converted correctly into the internal format?
I tried adding a hidden locked Attribute called IntDate and use "Subst IntDate = $start" but the result is dates in 1970, even though I have set the Time Format to "%F %H:%M" |
Re: Date conversion, posted by Martin Neumann on Wed Feb 24 08:44:42 2021
|
I don't feel comfortable allowing the elog daemon to execute random shell scripts. Is there no other way?
| Andreas Luedeke wrote: |
|
If you define a field as "datetime" then you'll get the standard ELOG input field for datetime. It will be stored as seconds of the epoch (seconds since 1.1.1970).
You can define a field as a default string input, then it is stored as a string. But you can convert that string by a shell scripts into seconds of the epoch. See "subst" command in the documentation of the elog syntax:
|
|
password forgot kills elogd, posted by Martin Lindjärv on Wed Aug 31 22:02:46 2005
|
Hi!
At first, thanx for this software!
But i found a bug or something like that. I installed elog on win2003 and winxp with default settings. And everywhere i had same problem - when forgot password is used it kills elogd. Error what is reported in EventLog is "Faulting application elogd.exe, version 0.0.0.0, faulting module elogd.exe, version 0.0.0.0, fault address 0x0002f1ee." and thats all. For testing tried newest beta too but it seems to have same problem.
i can insert my email address and when i click submit it wait's for some time and then gives 404.
Any kind of info would be good... |
|
password forgot kills elogd, posted by Martin Lindjärv on Wed Aug 31 22:03:04 2005
|
Hi!
At first, thanx for this software!
But i found a bug or something like that. I installed elog on win2003 and winxp with default settings. And everywhere i had same problem - when forgot password is used it kills elogd. Error what is reported in EventLog is "Faulting application elogd.exe, version 0.0.0.0, faulting module elogd.exe, version 0.0.0.0, fault address 0x0002f1ee." and thats all. For testing tried newest beta too but it seems to have same problem.
i can insert my email address and when i click submit it wait's for some time and then gives 404.
But tried under linux (gentoo) and everything works like charm.
Any kind of info would be good... |
|
Hardcoded Path in Makefile, posted by Martin Killenberg on Tue Feb 20 18:41:31 2007
|
I tried to compile ELOG on Scientific Linux Cern 4.4 and found that make quits because uname is not located in /usr/bin (like it is hardcoded in the makefile) but in /bin.
Later I found that this is only the case in the svn version, in the "latest.tar.gz" from 2007/02/20 the path is /bin.
Why do you have the absolute path in the Makefile? uname should be in the default path on any system. (The same applies to "rm")
I also was confused that you only provide one rpm Package (except for debian) without mentioning for which distribution. You try to avoid dependencies, but the elogd is linked against the basic libraries libc and ld-linux, which might vary. |
|
Adaptation of the language, posted by Markus Grosse-Kock on Thu Feb 20 12:27:42 2014
|
Hello,
I want to change the language to German. But it does not work.
Here my config:
Theme = default
Resource dir = D:\Elog
Language = german
Where is the problem? Or is it not possible to change the language in Windows?
Best regards,
Markus
|
Re: Adaptation of the language, posted by Markus Grosse-Kock on Thu Feb 20 17:37:06 2014
|
| Stefan Ritt wrote: |
|
| Markus Grosse-Kock wrote: |
|
Hello,
I want to change the language to German. But it does not work.
Here my config:
Theme = default
Resource dir = D:\Elog
Language = german
Where is the problem? Or is it not possible to change the language in Windows?
Best regards,
Markus
|
You put the "Language = german" statement into the logbook section, but it has to be placed in the [global] section as written in the documentation. Unfortunately this section of the configuration file cannot be accessed through the web interface, so you have to edit the elogd.cfg file manually, which might require admin rights.
Viele Grüsse nach Reken,
Stefan
|
Danke, hat funktioniert.
Gruß Markus |
Problem with ELOG, posted by Markus Grosse-Kock on Thu Mar 13 11:34:58 2014
|
Hi,
we have a problem. After windows updates, the elog service doesn´t start:
What can we do?
Best regards,
Markus |