ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67096
|
Tue Jul 26 21:50:05 2011 |
| Alan Grant | netman311@mts.net | Info | All | 2.9.0 | Re: Elog client usage |
Andreas Luedeke wrote: |
Alan Grant wrote: |
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.
|
I suppose you have your demon "elogd" running and you can connect to your logbook via the web interface?
Then you can use the "elog" command to upload a text file as one entry.
If you want to split the text file to one-entry-per-line, you need to write a batch script to do that.
The usage of the "elog" command is descibed in the ELOG User's Guide: https://midas.psi.ch/elog/userguide.html#misc
The command line for "elog" has to define all "Required attributes" with "-a ..."
elog -h <host> -p <port> -l <logbook> -u <user> <password> -a <attribute>=<value> -n 1 -m <text-file>
<port> can be omitted if port 80 is used, "-u <user> <password>" can be omitted if anonymous entry creation is allowed.
Here's an example to write to the demo logbook at midas (local text file /tmp/hello.txt contains "hello world")
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.
PS: please never refer to a location as "somewhere on the site".
|
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
|
Attachment 1: elogd.cfg
|
[global]
port = 8080
SMTP host = citygw
Display mode = summary
Self register = 1
[Tartan Tow Log]
Theme = default
Entries per page = 30
List Menu commands = New, Find, <a href=?cmd=Find>Print</a>
Menu commands = List, Edit, Duplicate, Delete, Back
Attributes = Ticket Date, Ticket Time, System Rec'd Date, System Rec'd Time, Ticket, Plate, Make, VIN, Pick Up Location, Officer, Violation, Work Type, Pick Up Date, Pick Up Time, Tow Unit, Drop Date, Drop Time, Drop Location, GOA, Cancel
List Display = ID, Ticket Date, Ticket Time, Ticket, Plate, VIN, Pick Up Location, Work Type, Pick Up Time, Drop Time, Drop Location, GOA
Summary lines = 0
Options Work Type = Rush Hour AM, Rush Hour PM, Street Work, Snow Route, ROPB, General
Options GOA = boolean
Options Cancel = boolean
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, ID, Ticket Date, Ticket, Plate, VIN, Pick Up Location, Work Type, Drop Location, Subtext
|
67097
|
Wed Jul 27 04:36:40 2011 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Info | All | 2.9.0 | Re: Elog client usage |
Alan Grant wrote: |
Andreas Luedeke wrote: |
Alan Grant wrote: |
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). [...]
|
[...] The usage of the "elog" command is descibed in the ELOG User's Guide: https://midas.psi.ch/elog/userguide.html#misc |
[...] 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"
|
You wrote you want to upload a text file, then you need to add at the end "-m <file>". E.g. if the text-file is named "C:text.txt", then write:
elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -a Ticket+date="Jul26/11" -n 1 -m C:text.txt
The "-n 1" is just to tell elog to upload plain text. If you do not specify "-m <file>" then it expects input from a pipe and therefore hangs. If you don't know what "input from a pipe" means then ALWAYS use the "-m <file>" option.
PS: if "Ticket date" is of the format "date" then it is sensitive to the formatting of the date string. "Jul26/11" is likely not a legal date format. Better do not specify it for the first test. Write instead:
elog -h localhost -p 8080 -l Tartan+Tow+Log -d elog -n 1 -m C:text.txt
PPS: do you really use a sub-directory "elog" instead of the default location "logbooks" for your ELOG logbook files? If not, then leave out this option, too.
elog -h localhost -p 8080 -l Tartan+Tow+Log -n 1 -m C:text.txt
|
2067
|
Thu Nov 9 23:52:26 2006 |
| An Thai | thaithan@gmx.de | Info | Windows | V2.6.2-175 | Outlook, Outlook Express and Free Webmail have problem with <br /> | If users reply an entry, the notification email cannot be displayed correctly in Outlook, Outlook Express and Webmail.
I look at the source code and see <br />. It could be the reason. |
Attachment 1: Reply.PNG
|
|
66910
|
Fri Sep 17 14:54:51 2010 |
| marco meneghelli | marco.meneghelli@bo.infn.it | Info | Linux | 2.8.0 | Cannot bind to port 8080 | good morning,
I have installed elog 2.8.0 from terminal but when I type
elogd -p 80
or simply
elogd
the system tells me
Cannot bind to port 8080
Can someone help me?
Thanks
Marco M |
1003
|
Wed Mar 23 11:19:51 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Info | Linux | | Re: New Debian package (2.5.8+r1592) -- needs testing | > Hi to all,
>
> I've prepared a new Debian package. This version will probably be the one
> which you'll find in Sarge/stable.
>
> There are some invasive changes in this version which call for a serious
> test. In accordance with a suggestion, I've changed the configuration
> mechanism. For details, please read the NEWS.Debian file attached.
>
> Could the Debian users who follow this forum test it and give some feedback?
> You can download the package from the following link:
>
> http://l10n-turkish.alioth.debian.org/debian/elog_2.5.8+r1592-1_i386.deb
>
> Thanks in advance for your participation,
It seems to work nice to me.
Just another suggestion: I think it would be better to insert a commented out
example for all allowed parameters in the distributed /etc/default/elog
nice work :-) |
1006
|
Wed Mar 23 16:44:32 2005 |
| Recai Oktas | roktas@omu.edu.tr | Info | Linux | | Re: New Debian package (2.5.8+r1592) -- needs testing | > It seems to work nice to me.
> Just another suggestion: I think it would be better to insert a commented out
> example for all allowed parameters in the distributed /etc/default/elog
Thanks for the test. Please note that, /etc/default/elog is partially auto
created during the installation. All options except PIDFILE and CONFFILE are
currently listed (as configured or commented out). If you didn't see these
options (after the update), there must be a problem. Did you mean the lack of
PIDFILE and CONFFILE in the default file? |
1016
|
Thu Mar 24 12:26:46 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Info | Linux | | Re: New Debian package (2.5.8+r1592) -- needs testing | > > It seems to work nice to me.
> > Just another suggestion: I think it would be better to insert a commented out
> > example for all allowed parameters in the distributed /etc/default/elog
>
> Thanks for the test. Please note that, /etc/default/elog is partially auto
> created during the installation. All options except PIDFILE and CONFFILE are
> currently listed (as configured or commented out). If you didn't see these
> options (after the update), there must be a problem. Did you mean the lack of
> PIDFILE and CONFFILE in the default file?
no, my bad (it seems :-P) .. I re-installed the package now on my laptop and seems
to work fine... maybe I have swapped the diff result when installed yesterday.
Making tests I found another problem, her is the report:
####
root@emc2:/home/albert# apt-get remove elog
Lettura della lista dei pacchetti in corso... Fatto
Generazione dell'albero delle dipendenze in corso... Fatto
I seguenti pacchetti saranno RIMOSSI:
elog
0 aggiornati, 0 installati, 1 da rimuovere e 0 non aggiornati.
È necessario prendere 0B di archivi.
Dopo l'estrazione, verranno liberati 2444kB di spazio su disco.
Continuare? [S/n]
(Lettura del database ... 152033 file e directory attualmente installati.)
Rimuovo elog ...
Stopping ELOG daemon: elogd.
root@emc2:/home/albert# rm /etc/default/elog
rm: rimuovere regular file `/etc/default/elog'? y
root@emc2:/home/albert# apt-get install elog
Lettura della lista dei pacchetti in corso... Fatto
Generazione dell'albero delle dipendenze in corso... Fatto
I seguenti pacchetti NUOVI (NEW) saranno installati:
elog
0 aggiornati, 1 installati, 0 da rimuovere e 0 non aggiornati.
È necessario prendere 0B/530kB di archivi.
Dopo l'estrazione, verranno occupati 2444kB di spazio su disco.
Selezionato il pacchetto elog, che non lo era.
(Lettura del database ... 151926 file e directory attualmente installati.)
Spacchetto elog (da .../elog_2.5.8+r1592-1_i386.deb) ...
Configuro elog (2.5.8+r1592-1) ...
cat: /etc/default/elog: No such file or directory
Starting ELOG daemon: elogd.
####
So, removing an existing elog (not purging) and installing again raise the error.
Why installation creates the default/elog file only the first time ? I think it
shoud do the job everytime (and everytime ask the user is there is a diff to be
checked) |
1233
|
Thu Jul 7 04:49:19 2005 |
| Gary Clayson | imppster@gmail.com | Info | Windows | latest | Re: A comprehensive listing of all commands elog performs |
Emiliano Gabrielli wrote: |
Gary Clayson wrote: | Can someone please enter a comprehensive list of the commands eLog will honor. I'm trying to build a 'decent' start page and am not totally familiar with eLog just yet. Thanks Stefan for an awesome application. The documentation is really decent, too. I just have been unable to locate a list of all commands available.
Thanks in advance.
Gary ;-> |
there's a link in the main elog web page.. it's under the Admin guide and it is the elog.cfg syntax guide |
thanks for the advice. DuH on me, I just needed to read the syntax page a little more closely. |
|