I am getting the following errors when trying to install elog-2.3.9 on
my FreeBSD box. I am running FreeBSD 4.5-RELEASE.

Many thanks!

"Makefile", line 21: Missing dependency operator
"Makefile", line 27: Need an operator
"Makefile", line 29: Missing dependency operator
"Makefile", line 31: Need an operator
make: fatal errors encountered -- cannot continue


You4eea

Unfortunately I don't have access to a FreeBSD box so I cannot try. But I 
thought the GNU make is the same on Linux and FreeBSD??? 

Has anybody successful compiled under FreeBSD?

- Stefan

I got elog 2.3.9 running on FreeBSD 5.1 successfully,
I compiled elog on a redhat box and then just copied over all the files to 
the FreeBSD box and ELOG just ran with no issues.
It's been running under heavy use for at least a month now.

PS: you might need the linux compatibility package installed on BSD though...


> I am getting the following errors when trying to install elog-2.3.9 on
> my FreeBSD box. I am running FreeBSD 4.5-RELEASE.
> 
> Many thanks!
> 
> "Makefile", line 21: Missing dependency operator
> "Makefile", line 27: Need an operator
> "Makefile", line 29: Missing dependency operator
> "Makefile", line 31: Need an operator
> make: fatal errors encountered -- cannot continue
> 
> 
> You4eea

> I got elog 2.3.9 running on FreeBSD 5.1 successfully,
> I compiled elog on a redhat box and then just copied over all the files to 
> the FreeBSD box and ELOG just ran with no issues.
> It's been running under heavy use for at least a month now.

FYI- the default "make" on FreeBSD is BSD, not GNU.

The easiest way to build elog on FreeBSD is to install "gmake" (via the port or
package) and type "gmake".  That's all it took for me to build a freshly
downloaded copy on 5.1 not 5 minutes ago.

Thanks for that mate, compiled elog on FreeBSD 5.1 myself no problems just like 
you said, great!

> 
> FYI- the default "make" on FreeBSD is BSD, not GNU.
> 
> The easiest way to build elog on FreeBSD is to install "gmake" (via the port or
> package) and type "gmake".  That's all it took for me to build a freshly
> downloaded copy on 5.1 not 5 minutes ago.

I would very much like to list groups instead of the individual logs on the
firs page you see after login.

Is there a way to do this? 

> I would very much like to list groups instead of the individual logs on the
> firs page you see after login.
> 
> Is there a way to do this? 

What would you like to see exactly?

a) Only groups. When you click on a group, you are taken to the first logbook 
in that group

b) Only groups. When you click on a group, a secondary page shows up showing 
a logbook selection page from that group

c) Two colums: First column group, second colum logbook, a bit like a 
directory structure like:

  Demo
    Linux
    Database
  Discussion
    Forum
    Archive
    Config Examples
    Contributions

Other uses might also vote...

- Stefan

I think I would like: Only groups. When you click on a group, a secondary page
shows up showing logs in that group. 

I would also have the option to list all logs so you could see logs that are not
in a group or locate a log where you didn't know what group it was in. I would
also like to have the option to sort logs and groups.

I am using Elog to keep track of application servers. The log names are the server
names and they are grouped by application. The list on the first page is getting
very long.

> I think I would like: Only groups. When you click on a group, a secondary page
> shows up showing logs in that group. 
> 
> I would also have the option to list all logs so you could see logs that are not
> in a group or locate a log where you didn't know what group it was in. I would
> also like to have the option to sort logs and groups.
> 
> I am using Elog to keep track of application servers. The log names are the server
> names and they are grouped by application. The list on the first page is getting
> very long.

Before I go and implement additional features, I would like to check if your problem 
cound not be solved easier. Whey don't you define your server as an attribute inside 
a logbook instead of having separate logbooks for each server? You know that you can 
sort by attributes (just by cliking on the column header for that attribute), so that 
would satisfy your need for sorting.

OK, I'm willing to give a shot but I don't know how to do it. I'll look in the docs and
see if I can figure it out.  Thanks.
 
> Before I go and implement additional features, I would like to check if your problem 
> cound not be solved easier. Whey don't you define your server as an attribute inside 
> a logbook instead of having separate logbooks for each server? You know that you can 
> sort by attributes (just by cliking on the column header for that attribute), so that 
> would satisfy your need for sorting.

I don't see anyway to define a log as an attribute. May be I just don't understand
something. I have more than 50 logs anyway.

Sorting is not something I have to have but it would make the servers names a little easier
to find. However, I can get them into any order I want buy rearranging them in the config
file. I've already done that for some of them. 

Groups on the front page would make navigation easier but it really isn't necessary.

I was hoping their was a way to do this that I had overlooked.


> OK, I'm willing to give a shot but I don't know how to do it. I'll look in the docs and
> see if I can figure it out.  Thanks.
>  
> > Before I go and implement additional features, I would like to check if your problem 
> > cound not be solved easier. Whey don't you define your server as an attribute inside 
> > a logbook instead of having separate logbooks for each server? You know that you can 
> > sort by attributes (just by cliking on the column header for that attribute), so that 
> > would satisfy your need for sorting.

> I don't see anyway to define a log as an attribute. May be I just don't understand
> something. I have more than 50 logs anyway.

What I meant was having only one logbook, and having the server as an attribute like

Attributes = Server, Type, ....
Options Server = Server1, Server2 (just the names of your current logbooks)
...

If you have already 50 logbooks this would require quite some work of course, but it might 
something for the future. I don't know if this fits into your requirements. If not, please 
let me know your complete scheme (current attributes and logbooks), then I can think about.

i work on Windows2000

part of my elog.cfg:

    Passwort file = c:\elog\passwd.txt
    Self register = 1
    Guest user commands = config, admin, logout

file system:

    - i created an emty file with name passwd.txt

problem:

    - if i use the link "Register as new user" on login, it does not work.
    - if i login as guest user and choose the menu config, it only 
    display  the attributes Login_name, Full_name and Email.    
    So i kann not create user.

what should i do ?
what are my mistakes ?

Can you attache as sample password file ?

in Unix:
i fixed the problem by defining a password file entry like 'user1::::'. 
then i defined 'admin user = user1' in elogd.cfg.
then i connected with login name 'user1' and created new user (as admin).

in Windows2000:
if i do this steps and i save the new user, it fails. the server service 
crash down.



> i work on Windows2000
> 
> part of my elog.cfg:
> 
>     Passwort file = c:\elog\passwd.txt
>     Self register = 1
>     Guest user commands = config, admin, logout
> 
> file system:
> 
>     - i created an emty file with name passwd.txt
> 
> problem:
> 
>     - if i use the link "Register as new user" on login, it does not work.
>     - if i login as guest user and choose the menu config, it only 
>     display  the attributes Login_name, Full_name and Email.    
>     So i kann not create user.
> 
> what should i do ?
> what are my mistakes ?
> 
> Can you attache as sample password file ?

> i work on Windows2000
> 
> part of my elog.cfg:
> 
>     Passwort file = c:\elog\passwd.txt
>     Self register = 1
>     Guest user commands = config, admin, logout
> 
> file system:
> 
>     - i created an emty file with name passwd.txt
> 
> problem:
> 
>     - if i use the link "Register as new user" on login, it does not work.
>     - if i login as guest user and choose the menu config, it only 
>     display  the attributes Login_name, Full_name and Email.    
>     So i kann not create user.
> 
> what should i do ?
> what are my mistakes ?
> 
> Can you attache as sample password file ?

Dear Friend!,

Only mistake in your file .cfg is   spell mistake "Passwort" in "Passwort 
file = c:\elog\passwd.txt" line. It should "Password file" t=d. 

try some thing like below,

[Log]
Theme = default
Comment = Financial Accounting Bug posting 
Attributes = Resource, Project Name, Task Desc, SDT, EEDT, ACDT, Percent WC, 
Status 
Options Type = Masters, Transactions, Reports
Options Category = Bug, New Feature, Client Requirement, Change
Required Attributes = Author, Type, Bug
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
Password file =D:\Program Files\ELOG\logpwd.txt
;Self register = 0
Self register = 1

Admin user =sridhar
Menu commands = Back, Login, New, Edit, config, Delete, Reply, Find, Help, 
Logout
Guest user commands = config, admin, Login, logout

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.