Preset ticket = TCK-#####

Preset on reply ticket = TCK-#####

Preset ticket = TCK-#####

Preset on reply ticket = TCK-#####

When I was browsing this forum about my previous problem, I found 
this thread. A ticket number that applies to all entries in a 
thread, but is unique to that thread.

But I have the same problem as Richard Ecclestone reported, and the
"Preset on reply ticket" line from your reply has not had any effect.

It appears that on starting a new thread (which is to have that
ticket number), the ticket number is just incremented by one from
that of the previous (as in previous ID number) entry.  This is
fine if each thread is completed before a new one started, but if
there are more than one active thread, which can be progressed
further in any order, new threads are likely to be issued with a
ticket number which has already been issued (see Richards's example).

An alternative source of unique numbers would be the Entry number (as
in "696 Entries", top right of the midas.psi.ch/elogs/Forum page),
which would be the seed for the ticket number on new entry.  Not sure
of the syntax for that, or for the replies to have *that* number for
the config file.  I know there is a problem if you move a number of
threads away, but the only alternative (that I can think of) is to
store the seed number somewhere, and increment it every time a new
thread is started.

Or have I got something wrong here? 
Thanks.

Regards,

David.

[demo]
Theme = default
Attributes = Ticket, Author, Subject
Preset Ticket = TCK-####

The the first entry gets TCK-0001. Any reply to that stays with TCK-0001. Then I do another "new" entry, which gets TCK-0002. Even if I then do another reply to the first thread, that will just stay with TCK-0001. So avoid using 'Preset on reply Ticket". The post from Richard was different, he wanted a new number also for replies (if I understand correctly).

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.

Hello

Sometimes it can come in handy to start a temporary elog service on the Windows platform. ( Maybe for testing purposes )

You can use the SC.exe utility to do that. If it is not on you're system you may download it from : ftp://ftp.microsoft.com/reskit/win2000/sc.zip

For this you can use the following procedure ( from the dos prompt ) :

 sc.exe create AIX-elog binPath= "\"c:\ELOG2.7.3\elogd.exe\" -D -c c:\ELOG2.7.3\security.cfg" DisPlayname= "AIX Elog Security" start= auto

If all went well the system answers :

 [SC] CreateService SUCCESS

Please notice the strange way the double quotes are used and the space after the = in the above command.

Now open the windows services ( from the prompt ) : services.msc

In the window that opens you will see the just created service with the DisPlayname you gave in the above command.

You see it is not started. You could click start, but there is an other way.

Now you can start the service from the prompt using the DisPlayname :

  net start "AIX elog security"

Press F5 ( refresh ) in the services window and you will see that the service is started.

Or stop the service :

  net stop "AIX elog security"

To remove the service ( from the registry ) :

   sc.exe delete AIX-elog

The system gives back :

  [SC] DeleteService SUCCESS

The other option is to start elogd.exe from the prompt :

  elogd.exe -c 

This is all for now

> > 2) /etc/init.d/elogd: line 10: /etc/rc.d/init.d/functions: No such file or directory (I fixed this by commenting
> > out that line).
> > 
> > 3) Starting elogd: /etc/init.d/elogd: line 34: echo_success: command not found (Fixed by search/replace "echo_"
> > to "echo ").
> 
> The elogd (or elogd.init in the distribution) is written for RedHat based systems where echo_success gives the 
> typical output with a green [OK] at the end of the line. For Debian, there is (was) in principle a Debian package 
> which has it's own startup script. Since the package maintainer is not active any more (I guess), the Debian 
> updates are heavily old. Once elog gets managed inside Debian again, that should get better again, but until then 
> one has to follow 2) and 3) from above. If I would remove it, the Scientific Linux users would complain. 

I'm actually using elog on Debian and have been rolling my own ".deb" for a while now (starting with the old Debian
one and working my way up till 2.7.5). Maybe you could add the Debian /etc/init.d/elog script to the "contrib"
directory, with a suitable note in the README or something like that? That script has not changed in a long time and
is still functional - and doing so would make it easier for people who would like to install elog on a Debian (or
Debian-based, e.g. Ubuntu) system. I'll attach the script.

Regards,

Thomas