| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
67143
|
Wed Nov 2 10:54:38 2011 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.8.0 | Re: multiple homes? |
| Christoph Kukulies wrote: |
|
Is it possible to have many roots with one elogd (or run several elogds), such that you can seaparate different groups or themes from each other:
electronics
trigger
power
mechanics
detector
support
Thanks.
Christoph
|
Have a look at "top groups" in the documentation |
|
67145
|
Mon Nov 7 10:12:04 2011 |
| Christoph Kukulies | kukulies@physik.rwth-aachen.de | Question | Linux | 2.8.0 | Re: multiple homes? |
| Stefan Ritt wrote: |
|
| Christoph Kukulies wrote: |
|
Is it possible to have many roots with one elogd (or run several elogds), such that you can seaparate different groups or themes from each other:
electronics
trigger
power
mechanics
detector
support
Thanks.
Christoph
|
Have a look at "top groups" in the documentation
|
Thanks. I got it working so far. One minor glitch:
I have one topgroup (with 2 subgroups),
electronics
trigger
power
and onother topgroup (only 1 subgroup)
mechanics
detector
When I get the login screen for the second (with the only one subgroup) it says in the header:
"Several logbooks are defined on this host. Please select the one to connect to:"
and below only the one group (detector) is shown, so actually nothing to select.
This may be possibly achieved by not defining a subgroup for the second one and leaving it as a topgroup,
but I don't know how it behaves, when the group admin decides to create a subgroup. Can he do
without requiring superuser or elog permissions?
--
Christoph
|
|
67586
|
Thu Oct 17 14:23:06 2013 |
| Oliver Kirsebom | oliver.kirsebom@gmail.com | Question | Linux | 2.8.0 | Re: automated email notification did not work for me |
| Stefan Ritt wrote: |
|
| Jianglai Liu wrote: |
|
Hi,
I am setting up an elog to organize my lab activities. I installed elog 2.8.0 on the latest CentOS 5.5, 32 bit. I got into trouble setting up the automated email notification.
According to the elog manual, I setup the smtp setting in the elogd.cfg as follows:
SMTP host = smtp.gmail.com
SMTP username = jianglai.liu
I then used "elogd -t" to encode the password into the configuration file.
But when I submit an entry, I always received: "Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. y17sm867489wfd.15"
If I switched to use my university email servers, similar things happened.
SMTP host = smtp.sjtu.edu.cn
SMTP username = jianglai.liu
I got "Error sending Email via "smtp.sjtu.edu.cn": 5.7.8 Error: authentication failed: another step is needed in authentication"
I also switched to use one of my old work server
SMTP host = smtp-server.its.caltech.edu
SMTP username = jliu
and ended up with the same error message.
I did a google search on this without much progress. I would appreciate it very much if someone could shed light on how do I fix this.
Thanks much!
|
elog only supports basic authentication, not TLS or SSL. These days more and more SMTP servers require this however. I will put this on my to-do list. In meantime you can maybe configure your CentOS machine acting as an SMTP server, and then not using TLS or SSL there. That's what most people do.
|
Hi, has this problem been fixed? (i.e does ELOG now support TLS or SSL?) Thanks, Oliver |
|
67587
|
Thu Oct 17 14:27:56 2013 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.8.0 | Re: automated email notification did not work for me |
| Oliver Kirsebom wrote: |
|
| Stefan Ritt wrote: |
|
| Jianglai Liu wrote: |
|
Hi,
I am setting up an elog to organize my lab activities. I installed elog 2.8.0 on the latest CentOS 5.5, 32 bit. I got into trouble setting up the automated email notification.
According to the elog manual, I setup the smtp setting in the elogd.cfg as follows:
SMTP host = smtp.gmail.com
SMTP username = jianglai.liu
I then used "elogd -t" to encode the password into the configuration file.
But when I submit an entry, I always received: "Error sending Email via "smtp.gmail.com": 5.7.0 Must issue a STARTTLS command first. y17sm867489wfd.15"
If I switched to use my university email servers, similar things happened.
SMTP host = smtp.sjtu.edu.cn
SMTP username = jianglai.liu
I got "Error sending Email via "smtp.sjtu.edu.cn": 5.7.8 Error: authentication failed: another step is needed in authentication"
I also switched to use one of my old work server
SMTP host = smtp-server.its.caltech.edu
SMTP username = jliu
and ended up with the same error message.
I did a google search on this without much progress. I would appreciate it very much if someone could shed light on how do I fix this.
Thanks much!
|
elog only supports basic authentication, not TLS or SSL. These days more and more SMTP servers require this however. I will put this on my to-do list. In meantime you can maybe configure your CentOS machine acting as an SMTP server, and then not using TLS or SSL there. That's what most people do.
|
Hi, has this problem been fixed? (i.e does ELOG now support TLS or SSL?) Thanks, Oliver
|
Didn't have time yet for this. |
|
66884
|
Thu Aug 26 15:37:20 2010 |
 | Robert Heine | heine@kph.uni-mainz.de | Question | Windows | 2.8.-2312 | How to make Subst run? |
Dear colleagues,
I tried to get an Subst <attrib> = $shell(<command>) to work and put this into a Preset text line, like e.g.:
Attributes = subject, ...
Options <name> = test{1}, ...
Subst myvar = $shell(dir)
{1} Preset subject = Test
{1} Preset text = $myvar
Which results in an ELOG-entry having printed "$myvar" in its body instead of the expected substitution. Changing the Subst command to: "Subst myvar = $host" or even to "Subst myvar = Test" also resulted in printing just the string "$myvar" into the submitted Elog-entry. - What am I doing wrong?
Best whishes
Robert |
|
66888
|
Fri Sep 3 14:14:07 2010 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Comment | All | 2.8.-2312 | Re: How to make Subst run? |
| Robert Heine wrote: | Dear colleagues,
I tried to get an Subst <attrib> = $shell(<command>) to work and put this into a Preset text line, like e.g.:
Attributes = subject, ...
Options <name> = test{1}, ...
Subst myvar = $shell(dir)
{1} Preset subject = Test
{1} Preset text = $myvar
Which results in an ELOG-entry having printed "$myvar" in its body instead of the expected substitution. Changing the Subst command to: "Subst myvar = $host" or even to "Subst myvar = Test" also resulted in printing just the string "$myvar" into the submitted Elog-entry. - What am I doing wrong? |
What you want to do is done simply by:{1} Preset text = $shell(dir)You expect "Subst" to create new variables, but it cannot do this.
"Subst" can overwrite the value of an existing field in an already submitted entry, while
"Preset" allows to prefill an existing entry field and the user may overwrites it before submitting (if it is not "Locked".)
In both cases you can either call a shellscript to create the desired text, or you can use
one of the predefined variables defined in the help pages "ELOG - Syntax of elogd.cfg" for "Subst".
Cheers Andreas |
|
66892
|
Mon Sep 6 16:18:41 2010 |
| Robert Heine | heine@kph.uni-mainz.de | Comment | Windows | All | 2.8.-2312 | Re: How to make Subst run? |
Thank you Andreas!
So I will generate the preset entry in a shell script.
And now to something completely different:
Is there a way to make the elogd options -x and -install work together?
Grüßli
Robert |
|
66896
|
Fri Sep 10 15:38:38 2010 |
| Robert Heine | heine@kph.uni-mainz.de | Question | Windows | 2.8.-2312 | How to setup elogd as windows service with shell execution? |
Dear colleagues,
I am trying to use the elogd as a service with activated shell-execution. Invoking 'elogd -x' on the command line works fine, as well as 'elogd -install'. The option 'elogd -x -install' does not seem to be implemented, so I followed two ways to get this to work:
1) creating my own service with instsrv/srvany and registry editing: starting 'elogd -x' does not work (error 1053), the -D option has to be added, to start the service without time out. But then shell execution seems to be not working, because no input to the elog is generated, but also no message saying shell execution was not enabled!
2) using 'elogd -install' and modifying the registry entry by adding the -x option to the command line in the 'HKLM\System\CurrentControlSet\Services\elogd\ImagePath': This enables shell execution, but instead of piping the output to the logbook, some DOS boxes pop up executing the shell command and terminate. No entries are generated.
Has anyone an idea?
Best regards
Robert
|