I have searched the Elog forum and docs at length for actual examples of how to use the Elog client and I apologize if I missed it somehwere but could someone please provide some actual examples of how the parmeters are used? I haven't had much success setting it up just going by the Elog command syntax quide.

What I intend to do is load a raw text file into an active logbook directly, either one line at at time or batched from a text file ("m" option).

Also, I saw a Perl script contribution somewhere on the site which appears to offer the same functionality as the above util. Just wondering why there would be two methods, and which might be the best for me to use?

Thank you.

Is there any possibility to start elogd as a service under NT/2000/XP 
having local service as its user? Yes, I've read the documentation. Maybe 
things have changed.
/Torsten/

> Basically im running elog on a redhat 8 box with stunnel already installed 
> as part of OpenSSL, on the server i ran the command specified in the 
> instructions
> 
> stunnel -d 443 -r 172.16.24.108:81

I haven't tried `stunnel` with elog, but as far as I read from various
sources, stunnel requires you to create an SSL certificate. In attachment,
you'll find a sample case for stunnel and smtp (port 25) + pop3 (port 110).
Hope this helps.

Reference: http://www.tldp.org/linuxfocus/common/sart/index.html

Elog V2.9.1-2435 if it matters. 

It is time again to install the certs for SSL in Elog, and the standard openssl command line does not seem to produce the files that I need in order to get it working on my system.

I copied the file to my trusty linux server and ran the command "openssl pkcs12 -in cert.p12 -clcerts -out cert.pem " as I did last time, last time I got a nice little .crt and .key file.. this time.. no such luck.. I can get by with the guys just hitting the continue and go past the expired cert notice for a bit.. but if I cannot fix it reasonably soon.. well, it won't be pretty for me.. <grin>

Any ideas that anyone can give will be appreciated.. this is a bit outside my usual duties around here..

I am trying to use the Elog Utility to import a few thousand entries. So 
far I have run into a few problems.

a) Cannot get elog utility to speak to elogd on port 8080. Even though I 
use the -p 8080 option with elog. I was able to get it to work when I 
moved my server to port 80.

b) I cannot get elog to work with and attributes or logbooks that contain 
spaces. Please refer the the following example:

elog -v -h scotland.ccs.yorku.ca -p 80 -a "Station Number"="CC001" -a "Mac 
Address"="000874fdc895" -a "Hostname"="cc001.cnscommons.yorku.ca" -a "IP 
Address"="10.6.10.52" -a "Manufacturer"="Dell" -a "Model Line"="Optiplex" -
a "Model Number"="GX270" -a "Monitor Manufacturer"="Dell" -a "Monitor 
Model"="E151FP" -a "Memory"="512MB" -a "CPU Speed"="2.6GHz" -a "Hard 
Drive"="40GB" -a "Service Count"="-" -l WSC2 -u charles xxxxx "DD/MM/YY: 
Change Description"

This line executes fine. Except only Hostname, Manufacturer, Memory and 
text are populated in the record. All the rest of the fields are blank.

c) the only way I was able to get the transaction to work was by reducing 
the size of the log book to a single word (ie WSC2).

Do I have to reduce all my attributes to single words? Or am I missing 
something simple to use as a delimiter for entry??

Thanks in advance

-Charles-

In response to an elog-hang issue I've been having on the Windows platform, I am building a new Unbuntu 14 TLS VM machine to host the identical configuration so that I can more easily debug when the hang happens again. I don't mind beefing up the hardware resources to either eliminiate that as a factor or resolve the problem. I'll have a higher end CPU to deal with 20 to 50 clients doing searches through the data (since the elog configuration currently does not provide a setting to limit how far back it can search with Quick Filters - pretty please add this basic setting!), but the main question I have now is what is a good amount of memory to add to the VM? I suspect even with 30 concurrent searches going CPU power will have more impact than memory in the case of elog. Can someone please confirm my suspicion and also recommend a suitable amount of memory I should install? My data volume is about 25 MB, all textual (no attachmemts), and the number of daily files goes back about 5 years. Any other tips for the build is very welcome.

Hi
I have a problem here which the ELOG service get terminated unexpectedly
on the Windows Server.
Is there any way to debug this problem ?

I am using the latest version of Elog and i tried the 2.5.3 version too 
have this problem 

Thanks!

Hi
I have a problem here which the ELOG service get terminated unexpectedly
on the Windows Server.
Is there any way to debug this problem ?

I am using the latest version of Elog and i tried the 2.5.3 version too 
have this problem 

Thanks!