|
|
|
Demo
Discussion
|
|
Forum
Config Examples
Contributions
Vulnerabilities
|
| Discussion forum about ELOG |
Not logged in |
 |
|
|
|
|
|
Message ID: 65947
Entry time: Fri Aug 8 14:50:56 2008
In reply to: 65946
|
|
| Category: |
Question |
OS: |
Linux |
ELOG Version: |
2.7.4-2111 |
|
| Subject: |
Re: Using the command line tool to edit |
|
|
| Yoshio Imai wrote: |
| 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 formelog -a 'Attribute1=value' -x -h localhost -l 'LOG\ BOOK' -p 8080 -u USER PASSWD |
I forgot to mention that I tried both 'LOG\ BOOK' and 'LOG%20BOOK' - neither worked. Running elog with -v seemed to indicate in both cases that the correct logbook could not be found.
| Yoshio Imai wrote: |
| 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 likeMessage successfully transmitted, ID=12345 which you could e.g. redirect into a file that the editing application then reads to determine the ID. |
Good point, thanks - I'll have to generate some kind of mapping table (ID<->Attribute) when the logbook gets populated, but that should be possible. It would be very cool, though, if elog was able to identify an entry by attribute value - maybe something for a day when Stefan gets bored... 
However, none of this will have any relevance unless I can solve the non-working "edit" function...  |