| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1989
|
Sat Oct 14 10:01:17 2006 |
 | Gregory M. Caughey | caugheygm@aol.com | Bug report | Windows | 2.6.2-1722 | Re: Elog v2.6.2-1722 appears to have broken "Suppress default [0|1|2|3]" option on Windows XP box |
| Stefan Ritt wrote: |
| Gregory M. Caughey wrote: | | Hope this helps a little... |
Yepp it helped. I could reproduce your problem and fix it. Can you try elog262-4.exe (Revision 1729)? |
Hi Stefan!
Just installed elog-2.6.2-1729 and it's working perfectly. I haven't had enough time to test it thoroughly yet but will report any problems I might find. As always thanks for your excellent work, I appreciate it.
Regards, Greg |
|
2000
|
Tue Oct 17 12:14:27 2006 |
 | deletoille | xavier.deletoille@synchrotron-soleil.fr | Bug report | Linux | Windows | 2.6.2-1723 | Date format in Threaded display |
hello,
I have a problem with the Date format in the Threaded display. The Date Format appears normally in the full and the summary displays but not in the threaded one.
I have found a similar Entry in the forum posted by Steve Jones on Friday July 16 16:53:01 2004 and you answered :" That should be fixed by the current version. Please update."
Did I make a mistake?
Here is a part of my program:
Show Attributes = Date evenement, Heure evenement, Auteur, Icone, Groupe
Time format = %d/%m/%Y, %T
Type Date evenement= datetime
Start page = ?rsort= Date evenement
Thanks in advance |
| Attachment 1: Elog1.JPG
|
|
| Attachment 2: Elog2.JPG
|
|
|
2001
|
Tue Oct 17 13:03:22 2006 |
 | Ibrahim Genc | ig004@hotmail.com | Bug report | Linux | Windows | 2.6.2-1723 | Re: Date format in Threaded display |
| deletoille wrote: | hello,
Time format = %d/%m/%Y, %T
Thanks in advance |
I think "date format" and "time format" are different tags.
you may try to use date format here. |
|
2002
|
Tue Oct 17 13:12:52 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | Windows | 2.6.2-1723 | Re: Date format in Threaded display |
That fix for Steve Jones was slightly different, it had to do with substitutions in threaded display. I fixed yours now in revision 1734, so give it a try.
Salut,
Stefan |
|
2008
|
Thu Oct 19 12:26:16 2006 |
 | deletoille | xavier.deletoille@synchrotron-soleil.fr | Bug report | Linux | Windows | 2.6.2-1723 | Re: Date format in Threaded display |
| Stefan Ritt wrote: | That fix for Steve Jones was slightly different, it had to do with substitutions in threaded display. I fixed yours now in revision 1734, so give it a try.
Salut,
Stefan |
Hello,
I’ve tried on the last available release (revision 1732) and I have the same problem.
You said in you previous message that: “I fixed yours now in revision 1734, so give it a try.”
Could you tell me when this one will be available?
Thanks in advance |
|
2009
|
Thu Oct 19 12:32:11 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | Windows | 2.6.2-1723 | Re: Date format in Threaded display |
| deletoille wrote: | I’ve tried on the last available release (revision 1732) and I have the same problem.
You said in you previous message that: “I fixed yours now in revision 1734, so give it a try.”
Could you tell me when this one will be available? |
Since you checked "Linux" in the "OS" of this entry, I was under the assumption that you were able to compile elog from the Subversion repository (http://savannah.psi.ch/websvn/filedetails.php?repname=elog&path=%2Ftrunk%2Fsrc%2Felogd.c).
If you need the Windows executable, I made http://midas/elog/download/windows/elog262-6.exe for you. |
|
2010
|
Thu Oct 19 12:42:42 2006 |
 | deletoille | xavier.deletoille@synchrotron-soleil.fr | Bug report | Linux | Windows | 2.6.2-1723 | Re: Date format in Threaded display |
IT WORKS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
THANKS A LOT |
|
2021
|
Thu Oct 26 21:54:40 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | Other | 2.6.2-1714 | SVN1723-overiding logbook directory causes eLog to bomb when going into daemon mode (was SVN1714 will not run in 'daemon" mode on Solaris8) |
| Stefan Ritt wrote: |
| Steve Jones wrote: | | There are also strange system calls that differ, and I thought it might be due to the setuid(60001) -nobody- but the the non-daemn mode also sets to nobody and works fine. |
The elogd program opens the port (which might be below 1024 and thus needs privileges), then either become daemon or not, then changes to the user and group specified in elogd.cfg. So this behaviour should be the same on both cases.
| Steve Jones wrote: | | I just compiled SVN1723 and tried the generic elogd.cfg -- of course *that works!*. Something in my complex config that causes elog to barf when it is attempting to fork the daemon process. |
That's a good starting point. Take your config file, strip one option after the other, and see which is the offending one. This helps us tracking down the problem.
| Steve Jones wrote: | | I have no idea what "/var/run/syslog_door" is. |
I have not either. But one thing which is different in the daemon mode that all output is redirected to the syslog facility via the function call redirect_to_syslog();. This routine was not written by myself so I don't know 100% what it's doing, just under Linux it works fine. Try to outcomment this function and try again. |
| Steve Jones wrote: |
Ok, I've narrowed down the problem to a single attribute. I edited elogd_fancy.cfg as it ships with SVN1723 and found a real bug and an issue:
BUG: In the initial comment section of elogd_fancy.cfg the line # This [global] section contains settings common to all logbooks is not parsed correctly as a comment and the embedded [global] is picked up and confuses elogd, eg., elogd will not pickup the port=8080 option. Taking "[global]" out of the comment restores fucntionality. I recommend checking to make sure that the config file checking routine ignores *entire* lines starting with a comment char;
ISSUE: The option Logbook dir = causes an enormous amount of problems, and this may be limited to elog installs that exist in NFS space (as opposed to local disk). If the default is left alone elogd appears to work fine; Try and override and the fun begins. The previous attached traces show that once going into daemon mode none of the logbook dirs can be found nor indexed. The workaround is to use the default "logbooks" dir. Perhaps the routine that creates the default (if not found) should be the same as the one that creates the override (?).
I reproduced this behavior using the elogd_fancy.cfg that ships.
|
|