ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66975
|
Tue Dec 14 20:16:46 2010 |
| Arno Teunisse | A.teeling3@chello.nl | Question | Windows | 280-5 | Re: How can Elog start automatically on Windows Server 2008 on startup ? |
Stefan Ritt wrote: |
Philipp W. wrote: |
Hi all,
i have a question... How can i manage it that elog starts automatically on windows startup ? I always need to type "elogd -p 85" in the console that it starts ...
Can anyone help me ? =)
Thanks
SenoX
|
If you install elog with the installer from the distribution, it installs elog as a windows service, which is started automatically when windows starts.
|
Hello
When the install did not work properly ( I've never had that problem ) you can start the elog service with the SC.EXE command like this :
sc.exe create Elog binpath= "\"c:\program files\elog\elogd.exe\" -D -c \"c:\program files\elog\elogd.cfg\"" displayname= "Elogbook services" start= auto type= own
Please notice the spaces after the = ( they are required )
You can now use :
net start elog
and
net stop elog
to start the service without a reboot.
Maybe this helps.
|
66976
|
Wed Dec 15 08:49:30 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.8 | Re: how to retrieve attachment on execute new |
Zbigniew Reszela wrote: |
Zbigniew Reszela wrote: |
Hello all,
I have a problem with retrieving attachments of an entry on "Execute new" command. In the syntax of elodg.cfg it is: In addition the list of all attachments can be referred to via $<attachment>. Could anyone explain it a little bit more explicit, or attach an example?
Thank you in advance.
|
Hello again,
I have managed with problem by using $attachments. This provides me a list o paths to attachments. If it's the correct way to use it please change elogd.cfg syntax page.
Thanks a lot.
|
Yes, indeed there was a typo in the documentation, $attachments is the correct one. I changed that in the syntax page. |
66977
|
Wed Dec 15 16:42:32 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.8 | Re: elog as a service in windows not detect Imagemagick |
Diego Obradors Campos wrote: |
I have installed elog 2.8 in a windows pc with the installer from the distribution, it installs elog as a windows service, which is started automatically when windows starts.
It is done as:
"C:\Archivos de programa\ELOG\elogd.exe" -D -c "C:\Archivos de programa\ELOG\elogd.cfg"
Moreover Imagemagick and GhostScript are in the path:
Version: ImageMagick 6.6.4-6 2010-09-21 Q16 http://www.imagemagick.org
Copyright: Copyright (C) 1999-2010 ImageMagick Studio LLC
Features: OpenMP
However the indexing loogbooks are only working fine when elog is started interactively. Is there any posiblity to start elog as a service and use thumbnails for quick preview?
Thank you in advance!
|
This is a know problem. I did not achieve to create the imagemagic subprocess and read its output when elogd is started as a service. Attached is the code doing that, I found it as an example from Microsoft. But even after hours of work, I could not get it running inside the service. If anybody has any idea, please let me know. |
66978
|
Thu Dec 16 19:20:20 2010 |
| Zbigniew Reszela | zreszela@cells.es | Question | Linux | 2.8 | Re: how to retrieve attachment on execute new |
Stefan Ritt wrote: |
Zbigniew Reszela wrote: |
Zbigniew Reszela wrote: |
Hello all,
I have a problem with retrieving attachments of an entry on "Execute new" command. In the syntax of elodg.cfg it is: In addition the list of all attachments can be referred to via $<attachment>. Could anyone explain it a little bit more explicit, or attach an example?
Thank you in advance.
|
Hello again,
I have managed with problem by using $attachments. This provides me a list o paths to attachments. If it's the correct way to use it please change elogd.cfg syntax page.
Thanks a lot.
|
Yes, indeed there was a typo in the documentation, $attachments is the correct one. I changed that in the syntax page.
|
Hello Stefan,
first of all thanks for quick response.
However I encountered another problem, but to explain it well I need to tell you more what actually I want to do with these substitutions.
So I would like to have a python script which on add new entry will create a new entry in another logbook with the same data (Only for certain attributes' values). That's why I need attachments.
These substitutions will be used as command line arguments of the script.
Since I started using $attachments, all the substitutions used before it, are passed twice? Without using $attachments substitution, it works fine - they are passed only once.
Furthermore I tested it without script, just passing them to a text file, and it seems that it really doesn't work well. Could you check that?
-------------------
Execute new = echo $message id '$long_name' '$System' '$Equipment' '$Subject' '$text' > /tmp/zzz_elog.log WORKS GOOD
Execute new = echo $message id '$long_name' '$System' '$Equipment' '$Subject' '$text' $attachments> /tmp/zzz_elog.log DOESN'T WORK GOOD
------------------
Thank you a lot in advance.
|
66979
|
Thu Dec 23 10:42:05 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.8 | Re: how to retrieve attachment on execute new |
Zbigniew Reszela wrote: |
Hello Stefan,
first of all thanks for quick response.
However I encountered another problem, but to explain it well I need to tell you more what actually I want to do with these substitutions.
So I would like to have a python script which on add new entry will create a new entry in another logbook with the same data (Only for certain attributes' values). That's why I need attachments.
These substitutions will be used as command line arguments of the script.
Since I started using $attachments, all the substitutions used before it, are passed twice? Without using $attachments substitution, it works fine - they are passed only once.
Furthermore I tested it without script, just passing them to a text file, and it seems that it really doesn't work well. Could you check that?
-------------------
Execute new = echo $message id '$long_name' '$System' '$Equipment' '$Subject' '$text' > /tmp/zzz_elog.log WORKS GOOD
Execute new = echo $message id '$long_name' '$System' '$Equipment' '$Subject' '$text' $attachments> /tmp/zzz_elog.log DOESN'T WORK GOOD
------------------
Thank you a lot in advance.
|
Thanks for reporting this bug. I fixed this in SVN revision 2348. |
66980
|
Fri Jan 7 05:45:41 2011 |
| Behdad D | behdad@inbox.com | Question | Windows | 2.8 | Multiple Insances of eLog on the same machine |
Hello,
Is it possible to run multiple instance of elog on the same windows box where each instance listens on a different port?
Thanks.
Behdad. |
66981
|
Fri Jan 7 08:37:49 2011 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.8 | Re: Multiple Insances of eLog on the same machine |
Behdad D wrote: |
Hello,
Is it possible to run multiple instance of elog on the same windows box where each instance listens on a different port?
Thanks.
Behdad.
|
Sure. Just start with one subdirectory for each instance with a separate elogd.cfg file, where you specify a different port. Note however that there is also the concept of "top groups" (see documentation) which lets a single instance of elog look like several independent installations. |
66982
|
Sun Jan 9 07:04:00 2011 |
| Behdad D | behdad@inbox.com | Question | Windows | 2.8 | Re: Multiple Insances of eLog on the same machine |
Stefan Ritt wrote: |
Behdad D wrote: |
Hello,
Is it possible to run multiple instance of elog on the same windows box where each instance listens on a different port?
Thanks.
Behdad.
|
Sure. Just start with one subdirectory for each instance with a separate elogd.cfg file, where you specify a different port. Note however that there is also the concept of "top groups" (see documentation) which lets a single instance of elog look like several independent installations.
|
Great. Thanks Stefan.
I also am already using the top groups. This is just to totally separate my work and home elog.....I have to admit I am really an elog addict. 
This elog and the idea behind it is absolutely brilliant. Very useful, easy to maintain, migrate, configure, easy to use, versatile, etc... Good on you all.
Cheers,
Behdad. |