Re: Version 2.3.9 released today, posted by nickc1 on Wed Jul 16 21:42:54 2003
|
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. |
Re: Version 2.3.9 released today, posted by Stefan Ritt on Thu Jul 17 10:46:29 2003
|
> 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. |
|
Re: Version 2.3.9 released today, posted by nickc1 on Thu Jul 17 18:06:17 2003
|
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. |
|
Re: Version 2.3.9 released today, posted by Stefan Ritt on Fri Jul 18 08:57:21 2003
|
> 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...). |
Bottom text = <file> not displayed in every screen?, posted by R. Beekman on Tue Jul 22 16:21:51 2003
|
I tried to add a file with the "Bottom text = <file>" option.
Although one would suggest that the bottom text file is included in every
page, I only saw the file appear in the page that appears when you issue
the "cmd=Edit" command.
Resolving this would enhance the ability to create skin. |
|
Re: Bottom text = <file> not displayed in every screen?, posted by Stefan Ritt on Thu Jul 24 15:10:14 2003
|
> I tried to add a file with the "Bottom text = <file>" option.
>
> Although one would suggest that the bottom text file is included in every
> page, I only saw the file appear in the page that appears when you issue
> the "cmd=Edit" command.
That's really weired. The file is displayed at the bottom of single messages,
and the message list, but NOT at the form, which you reach with the "Edit"
command. So all I can suggest ist the following:
- Hit the reload button on your browser each time you change that file, to
make sure the browser does not display a page from its cache
- The HTML file is *included* in the normal page, so it should not contain
<HTML> or <BODY> tags. Start with a simple file containing something like
<center>Test</center>
and see what you get.
- Make sure the file is in the elog "resource" directory, which gets
displayed if you start elogd with the "-v" flag.
Let me know if any of this helped. |
|
elog.exe cmd line - seems to just hang, posted by eric wooten on Fri Jul 25 02:02:48 2003
|
elog -h 192.168.0.25 -p 80 -l Database -a Type=test1 -a OS=W2K -a Loc=room1
-a Status=operational
doing anything wrong here? |
|
Re: elog.exe cmd line - seems to just hang, posted by eric wooten on Fri Jul 25 02:03:37 2003
|
Note: When I hit ctrl-break, it exits to cmd prompt, and the entry appears
in the logbook.... ?
> elog -h 192.168.0.25 -p 80 -l Database -a Type=test1 -a OS=W2K -a Loc=room1
> -a Status=operational
>
> doing anything wrong here? |