Dear colleagues,

I am trying to use the elogd as a service with activated shell-execution. Invoking 'elogd -x' on the command line works fine, as well as 'elogd -install'. The option 'elogd -x -install' does not seem to be implemented, so I followed two ways to get this to work:

1) creating my own service with instsrv/srvany and registry editing: starting 'elogd -x' does not work (error 1053), the -D option has to be added, to start the service without time out. But then shell execution seems to be not working, because no input to the elog is generated, but also no message saying shell execution was not enabled!

2) using 'elogd -install' and modifying the registry entry by adding the -x option to the command line in the 'HKLM\System\CurrentControlSet\Services\elogd\ImagePath': This enables shell execution, but instead of piping the output to the logbook, some DOS boxes pop up executing the shell command and terminate. No entries are generated.

Has anyone an idea?

Best regards

 Robert

I could never get shell execution work when elogd is started as a service. This has probably to do with system permissions or so under Windows. If anybody has a clue, please let me know. Under Linux this works nicely, but this is probably not an option for you...

Hi.

I have ELOG V2.8.0-2313 installed on a SLC 5.5 release and all works fine, Users can register them-self and I see for each of them in the passwd file:

<name>test</name>

<password>***something***</password>

....

after a '/etc/rc.d/init.d/elogd restart' the logins don't work anymore (they did before the restart)

and the passwd file changed:

<name>test</name>

<password encoding="SHA256">***something else***</password>

....

Any idea what goes wrong?

Cheers, Jack

Please have a look at https://midas.psi.ch/elogs/Forum/66872 

Running through a SQL database requires a major rework of the software. I'm planning this in the long run, but not for this year. I'm also not sure how much this would buy you. If you do a full-text search on 140k entries in a SQL database (not index search), this might also take some time.

But what you can do is to "archive" part of your logbooks. Since the files are named YYMMDDa.log, you can move all 09XXXXXa.log files into a separate "archive" which you then do not include in your search.  

> Hi Stefan,
> 
> I'm starting to get a similar problem to Lance's ("SQL Database").  Searching is beginning to take time.
> 
> In searching, I either can search one logbook (still relatively quick), or all of them.
> 
> I have my logbooks in groups, and often I know which group I want to search, and it would make the searching
> much quicker were the search confined to just that group.  I don't think I've missed anything in the
> documentation on this matter.  
> 
> If not a change to the elog program, is there another way of (say) arranging the logbooks that will achieve this?

You can't do that right now. I would have to extend the functionality to allow searching in groups. Also have a look 
at https://midas.psi.ch/elogs/Forum/66901. Maybe that helps a bit in meantime.

Uh, thank you for teaching me that something like B.E. exists. I didn't know before. Unfortunately elog relied on the underlying operating system date functions. I guess you have to convince Windows or Linux to switch to B.E., then elog will do as well. 

This is not implemented at the moment.