Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 416 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  2127   Tue Feb 13 15:36:08 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.3-1762Re: Synchronization using https

Marcus Hauser wrote:
Would it be possible to use rsync to syncronise two elogd servers on different servers via secure synchronization on the file level?
E.g.
rsync -av -e ssh /var/lib/elog/logbooks/ elog.remote.de:/var/lib/elog/logbooks/


Do do this, you have to do the following:

  • Stop both elogd servers on each side
  • Do the rsync
  • Restart the elogd servers

This is necessary because an elogd server does not rescan the database files unless it's restarted. Note that you only can synchronize on a day level. Like if in a single day new entries are made on both sides, you have a conflict. This is not the case if you do the internal elogd synchronization, because this works on an entry level (actually that was the reason why this internal synchronization was invented). So new entries on both sides which were made as the same day will be merged intelligently.
  2135   Fri Feb 16 12:08:19 2007 Question Ben Waughwaugh@hep.ucl.ac.ukQuestionLinux2.6.3-1762Setting From: for registration/password e-mails
We had a problem, as mentioned in the documentation, with "new password" e-mails being rejected because the default From: address is invalid, so we changed this using "Use Email From".

According to the documentation, "By default, the email address of the currently logged in user is used for the "From:" field. If no user is logged in, or the current user has not specified a email address in the password database, the setting of the option Use Email From is used for the "From:" field."

However, when an address is specified in "Use Email From" we find that all e-mail notifications, even those sent automatically when a logged-in user submits a log entry, are sent from this address.

How can we set a valid address for use for "change of password" or registration e-mails, but still use the appropriate user's e-mail address for log entries?
  2136   Fri Feb 16 16:45:33 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.3-1762Re: Setting From: for registration/password e-mails

Ben Waugh wrote:
We had a problem, as mentioned in the documentation, with "new password" e-mails being rejected because the default From: address is invalid, so we changed this using "Use Email From".

According to the documentation, "By default, the email address of the currently logged in user is used for the "From:" field. If no user is logged in, or the current user has not specified a email address in the password database, the setting of the option Use Email From is used for the "From:" field."

However, when an address is specified in "Use Email From" we find that all e-mail notifications, even those sent automatically when a logged-in user submits a log entry, are sent from this address.

How can we set a valid address for use for "change of password" or registration e-mails, but still use the appropriate user's e-mail address for log entries?


Right. The logic in the program and the documentation disagreed. The program uses the "Use Email From" address always if it's there, while the documentation gives preference to the user's email address. I change that in the program so that it agrees with the documentation. The modification is in SVN revision 1789 and will be contained in the upcoming next release.
  2138   Fri Feb 16 17:14:53 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.3-1762Re: Setting From: for registration/password e-mails

Stefan Ritt wrote:
Right. The logic in the program and the documentation disagreed. The program uses the "Use Email From" address always if it's there, while the documentation gives preference to the user's email address. I change that in the program so that it agrees with the documentation. The modification is in SVN revision 1789 and will be contained in the upcoming next release.


Actually I had to change it once more. Some installations do want to have always a pre-defined email address, such as this forum, which uses noreply@psi.ch. So I added a new option Default Email From. The precedence is now in decreasing order

  • Use Email from
  • user's email address
  • Default Email from

So only when a user is not logged in, the Default Email from setting is used if present.
  2140   Sun Feb 18 10:51:13 2007 Question Tobias Baggertobiasb@trashmail.netQuestionLinux2.6.3-1762Preset of a drop-down box entry with a "%" character
How do I preset a drop-down box entry which contains a % character?

I use following lines in the elogd.cfg:

Options list->ta = K - 0%, S - 10% (text a1), F - 20% (text a2)
Preset list->ta = K - 0%

The documentation says:
If a preset value is given for an attribute which has an options list, the preset value is selected in the drop down box by default.

But this doesn't work for me. I also tried

Preset list->ta = "K - 0%"
Preset list->ta = K - 0%%
Preset list->ta = K - 0\%

without success. What's the right way to do this?


Best regards
Tobias
  2141   Mon Feb 19 11:29:03 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.3-1762Re: Preset of a drop-down box entry with a "%" character

Tobias Bagger wrote:
How do I preset a drop-down box entry which contains a % character?


The problem was that '%' is used in auto-generated preset tags like XYZ-%Y-%b-### (see documentation). I made the auto-generation a bit more clever such that it only tries to interprete any '%' if there is any '#'. The fix is in elog version 2.6.4.
  2143   Tue Feb 20 18:41:31 2007 Entry Martin Killenbergmartin.killenberg@web.deCommentLinux2.6.4Hardcoded Path in Makefile
I tried to compile ELOG on Scientific Linux Cern 4.4 and found that make quits because uname is not located in /usr/bin (like it is hardcoded in the makefile) but in /bin.
Later I found that this is only the case in the svn version, in the "latest.tar.gz" from 2007/02/20 the path is /bin.
Why do you have the absolute path in the Makefile? uname should be in the default path on any system. (The same applies to "rm")

I also was confused that you only provide one rpm Package (except for debian) without mentioning for which distribution. You try to avoid dependencies, but the elogd is linked against the basic libraries libc and ld-linux, which might vary.
  2144   Tue Feb 20 21:10:28 2007 Reply Stefan Rittstefan.ritt@psi.chCommentLinux2.6.4Re: Hardcoded Path in Makefile

Martin Killenberg wrote:
I tried to compile ELOG on Scientific Linux Cern 4.4 and found that make quits because uname is not located in /usr/bin (like it is hardcoded in the makefile) but in /bin.
Later I found that this is only the case in the svn version, in the "latest.tar.gz" from 2007/02/20 the path is /bin.
Why do you have the absolute path in the Makefile? uname should be in the default path on any system. (The same applies to "rm")

I also was confused that you only provide one rpm Package (except for debian) without mentioning for which distribution. You try to avoid dependencies, but the elogd is linked against the basic libraries libc and ld-linux, which might vary.


Ups. The hard-coded /usr/uname somehow sneaked in from some temporary test. I removed it in the current SVN.

Indeed the RPM package I provide is built under Scientific Linux. The Debian port is done by someone else. Unfortunately I don't have ten boxes with all possible distributions laying around, so my possibilities are quite limited and I depend on third party help. If you want to contribute additional RPMs you are welcome.
ELOG V3.1.5-3fb85fa6