> > > Was just wondering about the status of the multi-line attributes in Elog, are 
> > > they implemented in elog yet? If not is that something you are planning to do 
> > > in the future?
> > 
> > In order to have multi-line attributes, the whole format of the logbooks has to be
> > changed. I plan to use XML for the logbook format in the future. We would not have
> > any more one file per day, but one big file per logbook. I have already some XML
> > functionality in elog, but this one requires a major rewrite of the whole code. On
> > the other hand, searching etc. will become much faster afterwards. I plan to start
> > this development soon, but it might take quite some time, so don't expect it
> > before summer or fall.
> > 
> > Best regards,
> > 
> >   Stefan
> 
> Thanks for your help, thats useful to know.
> 
> Paul

Hi Stefan,

any update on the multi-line request?

cheers,

Paolo

> > > > Was just wondering about the status of the multi-line attributes in Elog, are 
> > > > they implemented in elog yet? If not is that something you are planning to do 
> > > > in the future?
> > > 
> > > In order to have multi-line attributes, the whole format of the logbooks has to be
> > > changed. I plan to use XML for the logbook format in the future. We would not have
> > > any more one file per day, but one big file per logbook. I have already some XML
> > > functionality in elog, but this one requires a major rewrite of the whole code. On
> > > the other hand, searching etc. will become much faster afterwards. I plan to start
> > > this development soon, but it might take quite some time, so don't expect it
> > > before summer or fall.
> > > 
> > > Best regards,
> > > 
> > >   Stefan
> > 
> > Thanks for your help, thats useful to know.
> > 
> > Paul
> 
> Hi Stefan,
> 
> any update on the multi-line request?

Nope. Too many other things to do during my "day job".

Stefan

> > > > > Was just wondering about the status of the multi-line attributes in Elog, are 
> > > > > they implemented in elog yet? If not is that something you are planning to do 
> > > > > in the future?
> > > > 
> > > > In order to have multi-line attributes, the whole format of the logbooks has to be
> > > > changed. I plan to use XML for the logbook format in the future. We would not have
> > > > any more one file per day, but one big file per logbook. I have already some XML
> > > > functionality in elog, but this one requires a major rewrite of the whole code. On
> > > > the other hand, searching etc. will become much faster afterwards. I plan to start
> > > > this development soon, but it might take quite some time, so don't expect it
> > > > before summer or fall.
> > > > 
> > > > Best regards,
> > > > 
> > > >   Stefan
> > > 
> > > Thanks for your help, thats useful to know.
> > > 
> > > Paul
> > 
> > Hi Stefan,
> > 
> > any update on the multi-line request?
> 
> Nope. Too many other things to do during my "day job".
> 
> Stefan

Thank you, your eLog is already a very good instrument!

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-

> 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-

As a followup, this occurs not only in the Linux environment, but also under 
Windows XP. I get the same results...

-Charles-

> 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.

That problem has been fixed in revision 1.16 from Feb. 19th. Please get the
newest version from release 2.5.2 issued today.

> 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"

There was also some bug which has been fixed, plus you need following syntax:

elog -h ... -p 8080 -a "Station Number=CC001" ...

note the "" are around the whole attribute=value string, not only the attribute.

> > 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.
> 
> That problem has been fixed in revision 1.16 from Feb. 19th. Please get the
> newest version from release 2.5.2 issued today.
> 
> > 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"
> 
> There was also some bug which has been fixed, plus you need following syntax:
> 
> elog -h ... -p 8080 -a "Station Number=CC001" ...
> 
> note the "" are around the whole attribute=value string, not only the attribute.

Steve,

Thank you for the updates!!!

everything works great... -p 8080 and all my attribs get set. 

The only part that does not work is -l "Log Book" the -l variable has to stay as 
one word. If I submit 2 words (in quotes) it only looks for a logbook of the first 
word and fails.

-Charles-

> The only part that does not work is -l "Log Book" the -l variable has to stay as 
> one word. If I submit 2 words (in quotes) it only looks for a logbook of the first 
> word and fails.

I fixed that as well, please obtain the updated version at

http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elog.c?rev=1.20

Let me know if you cannot compile the C file and need an executable.