Contribution available for all who wants to make SKIN for ELOG!

You are invited to benefit from this free info!

Just click on the "Contributions" tab to find the info (look for ID6).

Or... goto          http://midas.psi.ch/elogdemo/Contributions/6

Version 2.3.9 of elog has been released today. Enhancements are:

- Added options "Use Lock", "Title image"

- New "Email format" specifies what is sent exactly in an email 
notification. This may now include also attachments

- "Format <attribute>" lets you assign separate style sheet classes to each 
attribute, making the web display more powerful (see this forum, 
the "subject" uses a separate formatting). Note that this feature requires 
an update of the old "default.css" CSS file, if a elog version prior to 
2.3.9 is already installed on a system.

- "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.

- New "Logging level" option gives enhanced logging capabilities, including 
read and write access logging to individual elog entries.

- The elog utility can now edit existing messages, and correctly quotes 
messages with "> " on replies.

A few small bugs have been fixed, refer to the ChangeLog for more details.

Can you give a syntax example of the Logging Level option ?



> Version 2.3.9 of elog has been released today. Enhancements are:
> 
> - Added options "Use Lock", "Title image"
> 
> - New "Email format" specifies what is sent exactly in an email 
> notification. This may now include also attachments
> 
> - "Format <attribute>" lets you assign separate style sheet classes to each 
> attribute, making the web display more powerful (see this forum, 
> the "subject" uses a separate formatting). Note that this feature requires 
> an update of the old "default.css" CSS file, if a elog version prior to 
> 2.3.9 is already installed on a system.
> 
> - "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.
> 
> - New "Logging level" option gives enhanced logging capabilities, including 
> read and write access logging to individual elog entries.
> 
> - The elog utility can now edit existing messages, and correctly quotes 
> messages with "> " on replies.
> 
> A few small bugs have been fixed, refer to the ChangeLog for more details.

> Can you give a syntax example of the Logging Level option ?

Please refer to the documentation (http://midas.psi.ch/elog/config.html), I just 
updated it. "Logging Level = 3" is the maximum level which includes writes and 
reads.

Cheers

It appears Im having problems getting this to work, my config is as follows, yet 
its not updating the log file since i installed the new RPM 2.3.9, is there a 
problem or am I doing something wrong ?

Thanks in advance.

[global]
port = 81
Logbook dir = /data
Logbook Tabs = 1
Main Tab = Home
Page title = LogBook System
SMTP host = support.localnet
Logfile = /var/log/elogd.log
Logging level = 3
Resource dir = /usr/local/elog
Welcome title = <img src="logo.gif"><p><font size=4 color=white>Customer Relational 
Management System</font>
Page title = Customer Relational Management System
Bottom text = bottom.html
URL = http://172.16.24.108:81/

> > Can you give a syntax example of the Logging Level option ?
> 
> Please refer to the documentation (http://midas.psi.ch/elog/config.html), I just 
> updated it. "Logging Level = 3" is the maximum level which includes writes and 
> reads.

> It appears Im having problems getting this to work, my config is as follows, yet 
> its not updating the log file since i installed the new RPM 2.3.9, is there a 
> problem or am I doing something wrong ?

Oops, there was a bug. I added the resource directory in front of the logfile name, 
which is not correct if the logfile name contains an absolute path. I fixed that in 
the current CVS version. As a temporary fix, remove the resource dir in your elogd.cfg 
or remove the full path in the logfile (the file will the be put into the resource dir 
of course...).

> 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.
>

> 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.

Sorry, I forgot to put it into the documentation. It's now available from 
http://midas.psi.ch/elog/config.html You basically use "Execute new = 
<command>", where <command> can have substitutions like $<attribute>, 
$remote_host, etc. You also have to start elogd with the "-x" flag to enable 
shell executions, since they can impose a security problem (see documentation).

I just upgraded from 2.3.5 to 2.3.9.

There are some errors in the generated HTML.  Most of the time
the browser renders everything correctly but sometimes not.  Please
check especially (http://validator.w3.org/):

- http://midas.psi.ch/elogdemo/Database/7
    There are too many <table> tags before the attribute list:
    'Type', 'Operating system',...  This should be just one table and
    not each row a separate table.  Also the first <table> tag lies
    outside a <td> tag of the enclosing table.

- http://midas.psi.ch/elogdemo/forum/

> There are some errors in the generated HTML.  Most of the time
> the browser renders everything correctly but sometimes not.  Please
> check especially (http://validator.w3.org/):

I did so and fixed several errors. Now the W3 validator doesn't complain any 
more. New version under CVS.

Hi,

I am trying to create an issues logbook where I have defined an attribute 
so I can track who this issue is assigned to. In order to get a drop-down 
list of users of the system to show up for that attribute (when creating a 
new issue), I have to type in the whole list of users in the config file. 
The problem is that whenever a user self-registers, I have to go into the 
config file and add that user to the list. Is there a way to write 
something like this:

Options Assigned To = $user_list

I am a new user, and am thoroughly enjoying working with ELog. Thanks for 
such a neat product. I have not been able to go through all the logs yet 
to figure out if this question has been asked/answered before.

> I am trying to create an issues logbook where I have defined an attribute 
> so I can track who this issue is assigned to. In order to get a drop-down 
> list of users of the system to show up for that attribute (when creating a 
> new issue), I have to type in the whole list of users in the config file. 
> The problem is that whenever a user self-registers, I have to go into the 
> config file and add that user to the list. Is there a way to write 
> something like this:
> 
> Options Assigned To = $user_list

This is not possible right now, but I will consider implementing it some time.

Boolean attributes were not displayed correctly in version 2.3.9.
Patch is attached.

> Boolean attributes were not displayed correctly in version 2.3.9.
> Patch is attached.

Yes, implemented, thank you.

The width of the textarea after pressing reply is too large. 
The problem is that the algorithm that searches for the longes line
looks for the next '\r' which it does not find and therefore takes the
number of characters in the text to be the width of the longest line.
To search for '\n' instead should solve the problem.  Please find the 
diff output below.


$ diff -c elogd.c elogd.c~
*** elogd.c     Mon Aug  4 13:57:35 2003
--- elogd.c~    Fri Aug  1 13:13:09 2003
***************
*** 6028,6035 ****
      p = text;
      do
        {
!       /*      pend = strchr(p, '\r'); */
!       pend = strchr(p, '\n');
        if (pend == NULL)
          pend = p+strlen(p);
  
--- 6028,6034 ----
      p = text;
      do
        {
!       pend = strchr(p, '\r');
        if (pend == NULL)
          pend = p+strlen(p);
  

> The width of the textarea after pressing reply is too large. 
> The problem is that the algorithm that searches for the longes line
> looks for the next '\r' which it does not find and therefore takes the
> number of characters in the text to be the width of the longest line.
> To search for '\n' instead should solve the problem.  Please find the 
> diff output below.

Ok, implemented, thanks.

Good day! I´m a german guy so my english is not the best sorry for this...  
I have my Elog completely configured now have I still another problem I 
would like with a new entry a E-Mail address to select to be able itself 
where the again provided entry am then hang-sent can me there someone 
help?  already the whole has after forum answers scanned.  Thanks David

> Good day! I´m a german guy so my english is not the best sorry for this...  
> I have my Elog completely configured now have I still another problem I 
> would like with a new entry a E-Mail address to select to be able itself 
> where the again provided entry am then hang-sent can me there someone 
> help?  already the whole has after forum answers scanned.  Thanks David

I'm German as well, but cannot understand your question. Can you write an 
email in German directly to me?

Ich kann Deine Frage leider nicht verstehen. Kannst Du sie mir direkt in 
Deutsch per Email schicken?

I know there's an item on the wishlist for password expiration, so how 
about account expiration..?? (after so many days of inactivity).

One complaint that comes from management is that when a user leaves the 
agency, the elog account seems to never get deleted.  There way of asking 
me, why I never keep up with the user account deletions.  Ha Ha, like I 
have time to constantly compare the user list from elog to the user list of 
other systems.

Another plea on my part, for Elog to allow for authentication via external 
database - such as LDAP, so we wouldn't have to maintain another user 
database.

Thanks,
Eric

> I know there's an item on the wishlist for password expiration, so how 
> about account expiration..?? (after so many days of inactivity).

Ok, added to the wishlist.

> Another plea on my part, for Elog to allow for authentication via external 
> database - such as LDAP, so we wouldn't have to maintain another user 
> database.

I had that request more than once. The problem with it is that I cannot 
implement it, since he have no LDAP server here at our institute to try it. So 
if someone teaches me how to do LDAP authorization correctly, I can put it in, 
but not before.