Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon1.gif   Message ID and trouble ticketing system, posted by lance on Sat Nov 24 03:16:46 2007 
    icon2.gif   Re: Message ID and trouble ticketing system, posted by Stefan Ritt on Mon Nov 26 14:33:59 2007 
       icon2.gif   Re: Message ID and trouble ticketing system, posted by lance on Mon Nov 26 16:58:26 2007 
          icon2.gif   Re: Message ID and trouble ticketing system, posted by Richard Ecclestone on Fri Feb 15 15:46:38 2008 
             icon2.gif   Re: Message ID and trouble ticketing system, posted by Stefan Ritt on Thu Feb 21 08:04:50 2008 
                icon2.gif   Re: Message ID and trouble ticketing system, posted by Stefan Ritt on Fri Mar 7 14:29:00 2008 
                   icon2.gif   Re: Message ID and trouble ticketing system, posted by Stefan Ritt on Fri Mar 7 14:45:02 2008 
                      icon2.gif   Re: Message ID and trouble ticketing system, posted by Stefan Ritt on Fri Mar 7 20:42:39 2008 
                         icon14.gif   Re: Message ID and trouble ticketing system, posted by David Pilgram on Fri Mar 7 21:26:18 2008 
                            icon5.gif   Re: Message ID and trouble ticketing system, posted by David Pilgram on Fri Mar 7 21:53:28 2008 
Message ID: 65779     Entry time: Fri Mar 7 20:42:39 2008     In reply to: 65778     Reply to this: 65780
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Info  OS: Windows  ELOG Version: ELOG V2.7. 
Subject: Re: Message ID and trouble ticketing system 

Ok, now I got the point, also Richard had the same problem. Assume we have 10 threads, and thus ticket numbers 1-10. Now we get a reply to #2, which then pops up to the top of the list. A new message increments the top entry of all entries, and then wrongly gives a new #3, instead of #11.

I fixed this in SVN revision 2073, where elogd searches all logbook entries for the largest index, then increments this one by one. The fix will be contained in the next release.

ELOG V3.1.5-fe60aaf