Have set up 3 top level groups, each with their own password file.
Ever since users have to 'login' twice to get to the appropriate elog.
You click on top level group, get to log book and click on the one you want 
and get login/password dialog box, click ok and and you get it again and 
then you finally get into the elog book.

Anything I can check on this behavior?

Hi all,

We currently have Elog postings mirrored on to a majordomo email list. 
Invariably, people on this list reply to the listserv and not to the Elog. 
Has anyone tried getting emails to a listserv to autoformat and register as
proper elog entries.  Didn't see any mention of this in the docs or forums.

Thx 

hello, 

i need to use a perl script with LWP to automatically update our elog
entries. we use ELOG internally.

however, I am not sure what elog checks for when doing the post through
form. and the auto-submit script always failed and returns "200 EOF". i can
get to the login part and grab form entry. its only the submittion failed.

let me know if you need more info to help me solve the problem.

thanks.


QiAng

I have a computer that has a different idea of its name from the DNS 
server. When I run ELOG and someone clicks "Search" I get a page not found.
I tried starting with "-n <hostname>", but elog still uses gethostname.
The example is that DNS says my machine is "abc.company.com" and netstat -
a says elog is listening on 8080 abc.personaldomain.com

Here is the code from elogd.c:

   /* get host name for mail notification */
   gethostname(host_name, sizeof(host_name));
   phe = gethostbyname(host_name);
   if (phe != NULL)
      phe = gethostbyaddr(phe->h_addr, sizeof(int), AF_INET);
   /* if domain name is not in host name, hope to get it from phe */
   if (strchr(host_name, '.') == NULL && phe != NULL)
      strcpy(host_name, phe->h_name);

I think you should be using tcp_hostname instead of gethostname if it is 
specified.

Hi,

right now I'm testing Elog to use it as a task/todo-log for our small 
workgroup. What I saw so far looks very nice and I like it very much. 
Thanks for the good work.

Playing with all the configuration possibilities I have one issue:
I like to use the "Extendable options" but I can't combine them with 
the "Conditional attributes".

-- snip

Options Area = Area_1{1}, Area_2{2}, Area_51{3}
{1} Options Ressort = Res01, Res whatever, end so on
{2} Options Ressort = somthing else, fill in
{3} Options Ressort = Alien observation, Budget planning
Extendable options = Ressort

-- snip

The "Conditinal Attributes" do have the "Add Ressort" button and the elog-
entry is written with this new attribute. But the new attribute is not 
inserted into the config file.

Long time ago I last read C syntax but mabye the function 
add_attribute_option should take care of the prefix {n} in extendable 
options?

Or do I miss something in the configuration syntax? 

  Regards,

  David

I just submitted a reply to elog:847 (the reply is elog:853).
Normally the thead containing the reply should now be listed as
the top thread.  Instead only the original message of the thread
(elog:820) is listed but the remaining messages in the thread are not 
listed.  It seems the problem is that for elog:820 the 'reply to this'
header is missing.  And elog:820 and elog:824 are the same messages
except that for elog:824 the subject is missing.  Actually ALL attributes
for elog:824 are missing.

I guess you could fix things up if you:
- add 'reply to this: 823' to elog:820
- remove entry elog:824

Could you implemet and option 'admin menu' which gets displayed
when an 'admin' is logged in.  This menu could e.g. also include 'Delete'
while the normal menu would not.

know that illness...  :-(  but was the last of the family of 4 people

i'd like to ask for an other usefull change togehter with this and how url's are 
handled by elog:

since there may be spaces in the name of a logbook (ex. "1stWordOfLogbook 
2ndWordOfLogbook") it is very userfriendly to name logbooks. also it's easy th 
make a reference for a other entry by copy and paste:

Display ThisURL = http://localhost:8080/$logbook/$message id

however, using spaces in the logbook name may give a wrong result, because the 
url would be http://localhost:8080/1stWordOfLogbook

and the space as well as the 2ndWordOfLogbook//$message id is only normal text.

may it be possible stefan, to replace the space in an url (starting 
with "http://") with a "+" or "%20"? this would allow to automate some things. 
actual the logbook name has to be hardcoded.


> > I think you should be using tcp_hostname instead of gethostname if it is 
> > specified.
> 
> Sorry my late reply, I was ill for some time. I implemented your suggestion in
> revision 1.522 which is available from CVS.
> 
> Note that there is also the "URL = xxx" option in the configuration file which
> lets you specify the whole URL including the host name.