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.

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

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

Hi,

  We have been using Elog successfully as a shiftlog book for over a month 
now, but I recently ran into an annoying bug, I think.
  We had a thread that was created and was being replied to over several 
days.  We first replied to the original thread and then each subsequent 
reply was a reply of the previous reply.  When the thread reached above 13 
of these, the elogd.exe would crash everytime a user attempted to select 
the logbook that contained the enormous thread.  
  I found the only workaround was to manually delete the offending entry 
from the log file and to instruct my users to not reply to replies unless 
absolutely necessary.  I have been able to replicate this error across the 
rest of my logbooks as well.  If there is any more information you may 
need, please feel free to contact me.

Thanks,
Chris Jones

> 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