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.

elog -h midas.psi.ch -l Linux+Demo -d elogs -a Author=nobody -a Type=Other -a Category=test -a "Subject=hello" -m /tmp/hello.txt

I hope this helps.

elog -h midas.psi.ch -l Linux+Demo -d elogs -a Author=nobody -a Type=Other -a Category=test -a "Subject=hello" -m /tmp/hello.txt

 It seems straight forward enough but I must be missing something in my elog command string. I run the client utiltiy but it always hangs after pressing Enter from the cmd window. It could be the way I specifying the host or subdir but I'm not sure. I tried multiple variations.

Some more info: For the prototype I'm just running Elog locally. I installed it to my XP in "c:\program files\elog". I verified tht elogd process is running. With the Elog page already open (ref my attached cfg file) I typed the following, observing case sensitivity, then press enter and at this point it just hangs:

elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -a Ticket+date="Jul26/11"

Note since all attributes are optional I only included "Ticket Date" for now until I can get this cmd working.

Please bear with me as I don't have an extensive technical background but I would be very grateful for any help as it's for a project at work. Soonest response would be greatly appreciated.

Thanks.

Alan

elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -a Ticket+date="Jul26/11" -n 1 -m C:text.txt

elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -n 1 -m C:text.txt

elog -h localhost -p 8080 -l Tartan+Tow+Log -n 1 -m C:text.txt

elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -a Ticket+date="Jul26/11" -n 1 -m C:text.txt

elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -n 1 -m C:text.txt

elog -h localhost -p 8080 -l Tartan+Tow+Log -n 1 -m C:text.txt

 Andreas, thank you very much. I was able to get the stand alone function working fine on my site, including a number of add'l attributes and options (SSL, etc).

I have define a MOption  BACKUP = Server, Switch, Router any now i link to use the Status of the Backup Option to display diffrent html file in the Text field, i the a posible way to do this ?

sample:

MOption  BACKUP = Server, Switch, Router

{Server&Switch&Router} Present Text = file1

{Server&Switch} Present Text  = file2

I would like to have different header for 'Text' internal attribute: e.g. an alias "Notes". So on the list page header of Text attribute column is Notes.

Is it already possible? I couldn't find it in Administrator's Guide. 

If not is it possible to add this feature?

No, this is not possible. I put this on the wish list. 

Dear all,

I wonder if anyone of you already tried to  change raw style in case of empty attribute value.

In my configuration file I have defined attribute "End date" (without quotation marks) and it's type is datetime.

How should I configure extra style for entries where this attribute doesn't have value.

My tries were:

Style End date = background-color:red

Style End date "" = background-color:red

Style End date " " = background-color:red

Style End date - = background-color:red

But they didn't work.

Any ideas?

This functionality was not implemented. I added it in SVN revision #2420, so it will be contained in the next release.

Thanks a lot Stefan

Is it possible to have an attachment to an entry in a different directory to the working directory of the logbook being used?

By which I mean, if you have in logbook hidden the attachment files

../logbooks/hidden/110705_235520_whatthis-0.png
../logbooks/hidden/110705_235520_whatthis.pdf

that an entry in another logbook, public, can use the entries in hidden to show them (and do everything that you can do with an attachment)
without making another copy in public?

I see that if, working in public, you attach the .pdf file in hidden, the files get copied across as

../logbooks/public/110705_235520_whatthis-0.png
../logbooks/public/110705_235520_whatthis.pdf

that is, with the original (hidden) timestamp, and no second time stamp superimposed.  From which you can gather I've been playing around, manually editing a yymmdda.log file to try and get the result I want, even if for the moment it cannot be done via elog; but without success, although there were some bizarre interpretations by the elog program of the edited yymmdda.log file, depending upon what I tried.

For one entry, it is of course no big deal, copying the files into the public directory, but if you are dealing with multiple huge entries, it does seem wasteful of HD space

But my reason for this is that hidden has restricted access, whereas public has general access.  The attachments themselves are not restricted, but comments, history etc around them in the restricted access logbook should not become available to the general viewer.

ELOG seems to enter a loop when you do certain opeations on certain messages: I moved a message to a different logbook and the deamon just gets stuck.

If I restart the daemon, the message was in fact moved: I can move it back to its original destination without problems.

I started in GDB and break with ctrl-C when the process gets stuck, to be told :

Program received signal SIGINT, Interrupt.
0x000000000040a968 in find_thread_head ()

I then made a core dump.

I put the files here: http://cern.ch/poulsen2/elog-error-report-110430.zip (they are too big to upload).

I get into the same problem in other circumstances such as when opening some threads (maybe because they contain "Reply-to" references to non-existing messages, but I have problems reproducing this on the test installation.

I should maybe also submit the incriminating thread.

Soren

 1. It appears that some times find_thread_head is called with message references that do not exist. That is not good.

I put in a little check like this  before seeing if the message has an "in_reply_to" reference:

The line:

if (lbs->el_index[i].in_reply_to)

becomes:

if (i < *lbs->n_el_index && lbs->el_index[i].in_reply_to)
 

2. The trouble started when I deleted a message in the middle of a thread, which left the thread badly "connected" (references to a deleted message).

3. Also, when a thread is badly connected, it is a problem moving messages to a different logbook. ELOG complains that it cannot access the message (with the invalid reference). But ELOG should ignore it, since the message was deleted.

Soren

 It would be nice to have this corrected. The problem occurs when you select (read) a message which refers to another message via "In-reply-to", and this message does not exist.

Soren

Soren, you're not alone!  I've had similar problems, as did Sara Vanini (elog:67077).

In my case, it is because the "move" or "copy" function does not move all the messages in very long threads.   To be more precise, elog will crash in the attempt to move a long thread - say over 40 replies, I don't know for sure.  Sometimes it has already moved the entire thread before it crashes, sometimes not.  I'd not flagged it up as an issue because I could not be sure it was not a memory issue with the old (>12 years) linux box I was using earlier this year, but it still happens on this new (to me, only 3 years old) linux box.

Whether it is the number of entries, the total memory size of the thread or some combination, I don't know.

I've found that in the "move" case, it has not deleted all the messages from the donor thread, so that there is a semi-thread still hidden there.  Should one by chance select that semi-thread, (because it is found during a search) elog goes into infinate loop, which requires a reboot of this linux box to fix.   Certainly the pinning down the issue to the missing entry referenced by an <i>In reply to:</i> explains this part of the issue.  Of course, deletion of one entry within a thread, or other adjustments will do the same thing, just as you (Soren) point out above.

If it happens to me, I will go in to the yymmdda.log files and fix the problem, be it deleting the entries of the semi-thread, moving across missing entries from the donor to the acceptor logbooks, adjusting the <i>Reply:</i> and <i>In reply to:</i> lines, but that is quite a time consuming and error prone exercise.

Is is possible to add formatting (such as <b> tags, etc..) to the "thread display" option?