Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 184 of 807  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  2079   Wed Nov 15 19:33:17 2006 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.6.1Re: add field type to automatically email CC

Arckonit wrote:
mmmm when i try your suggestion, it doesn't work :
error from the smtp server
Erreur lors de l'envoi d'un mél. via "172.20.0.2": Issue RCPT TO: command before DATA command


You get this error if no valid receiver is specified. I tried your config file and it worked fine. You need however a recent version of elog (2.6.2-7). Probably you have to upgrade.


Arckonit wrote:
you can remark the commented line
i would like to have one fixed list, so those users will be always alerted, and to be able to add and adress email in the notification attribute, but i really don't know how to do it
thx for any suggestions


You can do that with

Preset Notification = someone@mail.com, someoneelse@mail.com

So Notification gets preset with a pre-defined list, which you can edit before submission.
  2080   Wed Nov 15 20:22:29 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.6.2.1723Re: Conditional Email Notification by a text file

Grant Jeffcote wrote:
Can you reproduce this?


Yes, I get the same error. Shell substitution does not work when elogd is started as a service. This is a problem deep inside the service management of Windows and I do not know any solution for that. Sorry.
  2083   Sat Nov 18 17:13:22 2006 Reply Stefan Rittstefan.ritt@psi.chQuestion  Re: Attributes according to users

ather khan wrote:
Hi,
Is it possible to have certain attributtes available to certain user in one log boolk.
We have log book where the supervisor assign jobs to employees and we want only supervisor to have assign to attributes available and others only to view it.


You cannot restrict the modification if certain attributes, but you can restrict edits in general with the command
Allow edit = <name of admin>

You can also restrict the New, Delete, etc. commands to be only executable by the supervisor.
  2085   Mon Nov 20 22:20:22 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.6.2-1734Re: Re: $long_name in Moptions

Fergus Lynch wrote:
Hi,

Is there a way of having $long_name in 'Moptions'?

We use ELOG (amongst other things!) to allocate work out to Developers (who are all configured as ELOG users) I would like to use 'checkbox' functionality to allocate out a task to more than one developer. Currently only a single developer is chosen from a drop down list.


This was not possible until now, so I implemented the option
Type <attribute> = muserlist

which gives you checkboxes (= multi-userlist) for all users instead of a drop down list. This feature is implemented starting from revision 1758 and it will be contained in the next release of elog.
  2094   Tue Nov 28 10:20:12 2006 Reply Stefan Rittstefan.ritt@psi.chRequestWindows Re: Tool Tips

Grant Jeffcote wrote:
Hi Stefan,

Is there a way to add a 'Tool Tips' to individual 'Options' similar to that currently available for Attributes? I have several checkboxes under an attribute for predefined email groups and would like to see if I can make the recipient list viewable via a mouse hover using the 'Tool tip' feature.
If not possible can it be added to the wishlist?


Ok, I implemented this. It is in revision 1760 and will be contained in the next release.
  2096   Tue Nov 28 10:26:33 2006 Reply Stefan Rittstefan.ritt@psi.chRequestWindows Re: Tool Tips

Grant Jeffcote wrote:
What will the configuration line be?


If you have
MOptions item = value_1, value_2

you can do a
Tooltip value_1 = text
  2097   Tue Nov 28 10:34:54 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux2.6.1+r164Re: elog (2.6.1+r1642 ubuntu/debian) regularly becomes non-responsive (w/o crashing)

Peter Kovac wrote:
First, the problem. Fairly regularly (at least once a week, perhaps more), our elog daemon seems to quietly die. The process is still running but anyone attempting to access the server gets "connection refused." The elog log doesn't show anything and the apache logs just show "proxy: Error reading from remote server returned by [path]". Calling a daemon restart doesn't seem to kill the daemon -- I get a "could not bind to port" error. Using kill and then starting the daemon again fixes the problem for a few days and then we start over.

The particulars:
We are running elog on an Ubuntu (6.06 Dapper Drake LTS) web server.
It's currently version 2.6.1+r1642 pulled via apt-get from the Debian repositories.
elog is hiding behind an apache2+SSL proxy.

Any thoughts? Has anyone else seen this behavior? My next step is probably to compile 2.6.2 and remove the packaged flavor but I wanted to see if this was a known bug...


There are three reasons why an elog server can go into an infinite loop:

  • A bug which has been fixed in meantime. If you can give a try to 2.6.2-1750 or so that could help. I'm not sure if this version is already in the Debian distribution since I'm not the maintainer there.
  • A corrupted log file. If one of the YYMMDDa.log file get some garbage (maybe due to hard disk problems etc.) the elogd server can run into an infinite loop. In that case examine all log files to see if there is anything wrong. If so, edit it manually and restart elogd.
  • Some not yet found bug. One never can exclude this of course, but at this forum I have elogd running under similar conditions like you, and it runs for months without problems.
  2098   Tue Nov 28 12:48:47 2006 Idea Stefan Rittstefan.ritt@psi.chInfoAll2.6.3Version 2.6.3 released today
Dear ELOG users,

ELOG version 2.6.3 has been released today. It contains all the bug fixes, security fixes and a few new features collected since the last release which was actually almost half a year ago. The changelog contains all the details.

Due to the security fixes it is recommended to upgrade from any version prior to 2.6.3. Please note that the location of all password and log files has been moved from the main elog directory to the logbook directory. This means that after upgrading you have to move your password file manually, otherwise you cannot log in any more. This modification was requested because some ELOG installations (especially ones with top groups) can now have a read-only main directory.

Stefan Ritt
ELOG V3.1.5-3fb85fa6