Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 425 of 808  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
  1415   Mon Sep 19 19:48:07 2005 Question Mario Apodacammapodaca@dimetek.comQuestionLinux2.5.9Email Notification and Icons
I have two questions:

1) When sending out email notifications, is there a way to surpress the entries that have been left on the logbook? I want to be notified that someone has posted, but not receive the posting in the email.


2) Is there a way to set icons to users, so that each user has a defined icon? I set up a new attribute called: Author Icon and then tried using conditional attributes to have an icon set to a specific user. When I tested by posting, in the Author Icon section I didn't have an icon, instead a text box appeared with the name of the icon.

Thanks in advance for your help.
  430   Mon Sep 15 19:50:21 2003 Question Mikemlmoore@pella.comInfoWindows2.3.9Re: Version 2.3.9 released today
> Version 2.3.9 of elog has been released today. Enhancements are:

Forgive me if I've missed it, but I've looked in the forum, on-line cfg docs 
and downloaded docs.  I cannot find details on how to the used 
the "Execute ..." command.  What is passed on command line, etc.

thanks in advance
mike
 
> - "Execute new/edit/delete" lets one execute shell commands on the server 
> side for new, edited or deleted messages. Since this can cause security 
> problems, a new flag "-x" has been added to the elogd daemon to enable this 
> feature. It can be used to synchronize the elog database with other 
> databases, or to send SMS messages to people.
>
  1561   Wed Dec 21 23:52:27 2005 Question Mikemlmoore@pella.comQuestion 2.6.0Compile on Windows?
What version of Visual Studio do you use for compile Elog on windows.

I have downloaded the Tar from svn and am having some errors, but then I've go VS.Net 2003. I wondering if this was done with 6.0?

thanks
  1565   Thu Dec 22 14:32:00 2005 Question Mikemlmoore@pella.comQuestion 2.6.0Maximum number of LogBooks? Bug?
Is there a Maximum number logbooks?

I have run into a problem but I'm not sure if to call it a Bug or not. We have started using Elog to keep a work log for each of our production servers. After a short trial I put generated a config file using groups for all of our servers which is 294 logbooks. Almost every thing works except the config screen. You get a list of all the logbooks with the checkboxes for the email notifications. If you click save (Doesn't make a difference if you make changes or not) you get the following.

Error: Too many parameters (> 120). Cannot perform operation.

I was able to recompile using cygwin under windows after changing MAX_PARAM from 120 to 400. That fixes the problem, but eventually you get a stack overflow.

Any suggestions? I have considered separate instances running 100 logbooks each but I would like to have a global search.

Thanks for a Great tool. I've been using it as a personal log for sometime and was finally able to convince my team we sould use it.
  1567   Thu Dec 22 15:39:23 2005 Smile Mikemlmoore@pella.comQuestion 2.6.0Re: Maximum number of LogBooks? Bug?

Stefan Ritt wrote:


You're really pushing to the limit Wink

The maximum number of logbooks is indeed 120. If you have too many logbooks, they are also hard to handle (too many check boxes in the config page etc.). What if you make not one logbook per server, but have a single logbook and use the server as an attribute, like

Attributes = ..., Server, ...
Options Server = Server1, Server2, ...

Now you can ask: How many options are possible for an attribute, and the answer is 100, which is even less than the number of logbooks. But you can make three logbooks, each covering 100 servers, and that covers your 294 servers.


Thanks for the quick reply and suggestion. I will give that a try.

You might want to consider adding a check that there aren't over 120 logbooks. I manually created the elog.cfg with 294 logbooks. Everything works, except for running into this problem.

Thanks again
  1571   Tue Jan 3 17:20:16 2006 Entry Mikemlmoore@pella.comBug report V2.6.0elogd 2.6.0 crash on password Forgot?
I have been having a repeatable crash on V2.6.0 everytime someone tries to recover a password using the option from the login screen. See attachment for a jpg of the message.

This is occuring on windows 2003. But I have also tested it on windows XP and it occurs there as well. In addition on XP I did a generic installtion and added the password option to the DEMO application and it fails there as well.

Mike
Attachment 1: elog-pw-crash.jpg
elog-pw-crash.jpg
  67216   Mon Mar 26 13:44:23 2012 Warning Achim Dreyerml10352@adreyer.comBug reportLinux2.9.1-2444segfault on empty, non-writable passwd file

 

Segfault when password file is empty and not writable a segmentation fault is generated when a new user tries to register:

 

root#  > passwd

root#  chown root.root passwd

root#  chmod 644 passwd

root#  grep -i usr elogd.cfg

root#


kernel: [515323.672377] elogd[31048]: segfault at 78 ip 00000000004ba780 sp 00007fff03cd2078 error 4 in elogd[400000+dc000]
 

I cannot reproduce this error when running within gdb.

 

  67486   Sat Apr 27 14:09:13 2013 Reply Achim Dreyerml10352@adreyer.comRequestLinux2.9.2Re: Support for modern Linux

Vinícius Ferrão wrote:

Hello folks,

Can we have a better support under modern Linux distributions?

I'm trying to install elog in our webserver and it's becoming a boring task. First of all theres only RPM packages. And we really don't like the Red Hat method, so we use Debian Servers. More package mainteners would be nice.

 

The software appears to be working correctly, but there are some bugs (or perhaps missing dependencies?); the init script put in /etc/rc.d/init.d is broken under Debian:

First of all because it's in /etc/rc.d.

 

The second problem is in this line:

 

# Source function library.

#. /etc/rc.d/init.d/functions

The file doesn't even exists.

 

The third problem is the echo_success; echo_failure commands that doesn't even exist. As I can see it's definitions are sourced in the functions file that doesn't exist.

 

After removing this missing commands or files from the init.d; I can call elogd script and start the daemon under root. Appears to be working...

 

And last but not least; there's a way to standardize the init script to run in other Linux distros, so we can put it to start automatically at boot time?

 

Many thanks in advance,

Vinícius Ferrão 

 

PS: I'm not asking to support any creepy distros, but to support the .deb package format and system style.

 

 

 

 

/etc/rc.d/init.d/functions is part of the initscripts.rpm - so only usable on RedHat/CentOS..

Can someone also update https://midas.psi.ch/elog/download.html ? It was last updated in 2001 and the download directory contains a debian package that was last updated 2004. If debian is not supported in a current version that bit should be removed from the page.

Kind regards,
Achim
ELOG V3.1.5-3fb85fa6