Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon4.gif   Using the command line tool to edit, posted by T. Ribbrock on Thu Aug 7 10:12:25 2008 
    icon2.gif   Re: Using the command line tool to edit, posted by Yoshio Imai on Fri Aug 8 14:27:03 2008 
       icon2.gif   Re: Using the command line tool to edit, posted by T. Ribbrock on Fri Aug 8 14:50:56 2008 
    icon2.gif   Re: Using the command line tool to edit, posted by Stefan Ritt on Mon Aug 11 11:02:18 2008 
       icon2.gif   Re: Using the command line tool to edit, posted by T. Ribbrock on Mon Aug 11 15:14:40 2008 
Message ID: 65946     Entry time: Fri Aug 8 14:27:03 2008     In reply to: 65943     Reply to this: 65947
Icon: Reply  Author: Yoshio Imai  Author Email:  
Category: Question  OS: Linux  ELOG Version: 2.7.4-2111 
Subject: Re: Using the command line tool to edit 

T. Ribbrock wrote:
NOTE: I found that this does not work if LOGBOOK has any spaces in it - I would get error messages where the logbook was not found.


You might try to escape the space in the form
elog -a 'Attribute1=value' -x -h localhost -l 'LOG\ BOOK' -p 8080 -u USER PASSWD



T. Ribbrock wrote:
What is the easiest way to retrieve an ID from the command line

I don't know if this helps you (depends on how much the application that edits the entry communicates with the application the generates the entry), but the elog client should output something like
Message successfully transmitted, ID=12345
which you could e.g. redirect into a file that the editing application then reads to determine the ID.
ELOG V3.1.5-fe60aaf