Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon1.gif   Converting logs, posted by Kutlay Topatan on Fri Apr 18 21:32:59 2003 
    icon1.gif   Re: Converting logs, posted by Marcus Meyer on Tue Apr 22 19:27:28 2003 
       icon1.gif   Re: Converting logs, posted by Recai Oktas on Tue Apr 22 19:58:13 2003 
          icon2.gif   Re: Converting logs, posted by Stefan Ritt on Tue Apr 22 20:06:51 2003 
Message ID: 301     Entry time: Tue Apr 22 20:06:51 2003     In reply to: 300
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Question  OS:   ELOG Version:  
Subject: Re: Converting logs 
> `elconv' is just a simple tool to convert pre 2.0 log files to the current
> format. (Well, after all these confusions, dropping it from the future
> releases won't be surprising -at least for me- ;) You might try some
> well-known text-processing tools ie. preferably awk or perl to make the
> required conversions. But I think using comma or tab as the delimiter is 
not
> suitable due to the content of logs. If all you want is importing them to
> excel/word, you should play with the delimiter options of mentioned 
programs
> before trying a solution.

Hi Recai. I have several requests of this kind. "Want to import/export to 
comma separated text" or "XML". So one option is to extend elconv to handle 
all kind of conversions 1.x -> 2.x, 2.x -> CSV, 2.x -> XML. An alternative 
would be to write some awk/perl scripts as you noted. The disadvantage of 
this solution would be that they rely on the installation of awk/perl which 
is not given on windows systems. But nevertheless, if anyone volunteers to 
write a conversion tool, I would be happy to include it in the distribution. 
If not, I can put it into elconv.c, but that could take until June, given my 
current work load.
ELOG V3.1.5-3fb85fa6