Re: Attributes for message workflow., posted by Andreas Luedeke on Wed Mar 30 13:46:01 2011
|
| Ryan wrote: |
|
[...] I am even open to losing the historical "status" and beeing able to change all entries on the thread on reply. (i.e. Reply #4 changes "Status" to "Approved", and the system changed all entries in the thread to "Approved")
|
One possibility is to use the new 2.9.0 feature "Propagate attributes = OPS Approval, ENG Approval, Director Approval"
A change in any of the three listed attributes would propage to the corresponding fields of all former entires of the same thread.
So if someone creates a reply and changes "OPS Approval" to "Approved", the field "OPS Approval" of the original entry would go as well to "Approved".
I just happen to know about this feature because Stefan implemented it for me :-) |
Re: elog2sql - a script to convert elog logbooks to a MySQL database, posted by Pelle on Sat Apr 23 08:56:26 2011
|
I know this thread was started 2003 but if anyone have this MySQL export script please attach it to this thread.
Thanks,
Pelle |
|
Re: elog2sql - a script to convert elog logbooks to a MySQL database, posted by Pelle on Sat Apr 23 14:32:38 2011
|
> > I know this thread was started 2003 but if anyone have this MySQL export script please attach it to this thread. > > Thanks, > > Pelle
Sorry, found it in the contribution list https://midas.psi.ch/elogs/Contributions/5 |
Is there maximum number of entries?, posted by Hung Dao on Tue May 31 17:38:57 2011
|
Does anyone know whether ELOG has limit number of entries or it can create new entries as many as it can go? Thanks. |
|
Re: Is there maximum number of entries?, posted by Stefan Ritt on Thu Jun 2 21:28:19 2011
|
| Hung Dao wrote: |
|
Does anyone know whether ELOG has limit number of entries or it can create new entries as many as it can go? Thanks.
|
The number of entries is not limited. But if there are very many entries, searching can get a bit slow. We have installations with ~100'000 entries and they work still fine. |
|
Re: elogd crashes when running mirror cron with SSL and KRB5, posted by Andreas Luedeke on Fri Jun 3 12:06:20 2011
|
> When I run a mirror server and both logbooks using SSL/KRB5 then the cron job causes a segmentation fault.
>
> I haven't tried to check it with a simple configuration yet.
> My set-up: two elogd on same server, one running "german" on port 444, the other "english" on port 445.
> Both are behind an apache webserver configured reverse proxy, to hide the ports for external access.
> I'll try to reproduce the fault with a "minimal configuration" soon and report again.
>
I've tried to test a simpler configuration on my local PC but failed:
all simple set-ups I've tried worked fine.
I found that the mirror cron synchronization works fine in my production set-up when I remove the line:
Mirror user = luedeke
But I can have this line in my simple test set-up and it still works fine.
Anyway: bugs closed for me. |
Re: Elog client usage, posted by Andreas Luedeke on Fri Jul 22 10:31:27 2011
|
| 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". |
Re: Elog client usage, posted by Alan Grant on Tue Jul 26 21:50:05 2011 
|
| 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
|