is it possible to add ip information into the logging? that's something i was working on already but never finished...now that there's logging already added :)

Just since some people asked for: Here is the elogd.cfg for this demo 
logbooks:

========= cut here ===================

[global]
logbook tabs = 1
SMTP host = mailsend.psi.ch
URL = http://midas.psi.ch/elogdemo/
user = midas
group = midas

[Linux]
Theme = default
Comment = General linux Tips & Tricks
Data dir = /usr/local/elogdemo/logbooks/Linux
Attributes = Author, Type, Icon, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, 
Configuration, Tips & Tricks, Info, Other
IOptions Icon = icon1.gif, icon3.gif, icon4.gif, icon5.gif, icon6.gif, 
icon7.gif, icon8.gif, icon12.gif, icon13.gif, icon14.gif
Options Category = General, Hardware, Software, Network, Applications, 
Shell, Account, Packages, Daemons, Other
Required Attributes = Author
Subst Author = $author
Summary on default = 1
Summary lines = 0
Email all = stefan.ritt@psi.ch
Email message body = 1

[Database]
Theme = default
Comment = Demo of database-like elog
Data dir = /usr/local/elogdemo/logbooks/database
Attributes = Type, Operating system, Location, Status, Comment
Required Attributes = Type, Operating system, Location, Status
Options Type = PC, Router, Bridge
Options Operating system = Linux, Windows NT, Windows 2000, Windows XP, 
Windows ME, Embedded
Options Location = Building1, Building2, Building3
Options Status = working, defect, in repair
Show text = 0
Start page = ?cmd=Search&mode=summary
Display search = #, Type, Location, Status
Summary lines = 0
Find menu commands = New, Find, Last
Menu commands = Back, New, Edit, Delete, Find, Config, Help
Number Attachments = 0
Suppress default = 2
Entries per page = 10

[Forum]
; general options
Password file = /usr/local/elogdemo/logbooks/forum/passwd
Admin user = stefan
Self register = 2
Theme = default
Comment = Discussion forum about ELOG
Data dir = /usr/local/elogdemo/logbooks/forum
Display mode = threaded
Start page = ?cmd=Search&mode=threaded
Menu commands = Back, New, Edit, Reply, Find, Last day, Last 10, Admin, 
Config, Logout, Help
Find menu commands = New, Find, Last x, Admin, Config, Logout, Help
Guest menu commands = Back, Find, Login, Help
Guest find menu commands = Find, Login, Help
Number Attachments = 1
Message comment = <img src=icons/icon6.gif> Please enter only serious 
messages here, for testing use the <b>Linux</b> Logbook:
Filtered browsing = 0
Entries per page = 8
Reverse sort = 1
Restrict edit = 1

; Attributes
Attributes = Icon, Author, Author Email, Category, Subject
IOptions Icon = icon1.gif, icon2.gif, icon3.gif, icon4.gif, icon5.gif, 
Options Category = Info, Bug report, Bug fix, Question, Request, Comment, 
Other
icon6.gif, icon7.gif, icon8.gif, icon12.gif, icon13.gif, icon14.gif
Required Attributes = Author, Author Email, Subject, Icon
Subst on reply subject = Re: $subject
Thread display = $subject, posted by $author on $Entry date
Thread icon = Icon
Remove on reply = Author, Author Email
Date format = %B %d, %Y
Preset Author = $long_name
Preset Author Email = $user_email
Locked Attributes = Author

; Email notification
Email message body = 1
Display Email recipients = 0

Thank you very much!

> Just since some people asked for: Here is the elogd.cfg for this demo 
> logbooks:
> 
> ========= cut here ===================
> 
> [global]
> logbook tabs = 1
> tab cellpadding = 2
> SMTP host = mailsend.psi.ch
> URL = http://midas.psi.ch/elogdemo/
> user = midas
> group = midas
> 
> [Linux]
> Theme = default
> Comment = General linux Tips & Tricks
> Data dir = /usr/local/elogdemo/logbooks/Linux
> Attributes = Author, Type, Icon, Category, Subject
> Options Type = Routine, Software Installation, Problem Fixed, 
> Configuration, Tips & Tricks, Info, Other
> IOptions Icon = icon1.gif, icon3.gif, icon4.gif, icon5.gif, icon6.gif, 
> icon7.gif, icon8.gif, icon12.gif, icon13.gif, icon14.gif
> Options Category = General, Hardware, Software, Network, Applications, 
> Shell, Account, Packages, Daemons, Other
> Required Attributes = Author
> Subst Author = $author
> Summary on default = 1
> Summary lines = 0
> Email all = stefan.ritt@psi.ch
> Email message body = 1
> 
> [Database]
> Theme = default
> Comment = Demo of database-like elog
> Data dir = /usr/local/elogdemo/logbooks/database
> Attributes = Type, Operating system, Location, Status, Comment
> Required Attributes = Type, Operating system, Location, Status
> Options Type = PC, Router, Bridge
> Options Operating system = Linux, Windows NT, Windows 2000, Windows XP, 
> Windows ME, Embedded
> Options Location = Building1, Building2, Building3
> Options Status = working, defect, in repair
> Show text = 0
> Start page = ?cmd=Search&mode=summary
> Display search = #, Type, Location, Status
> Summary lines = 0
> Find menu commands = New, Find, Last
> Menu commands = Back, New, Edit, Delete, Find, Config, Help
> Number Attachments = 0
> Suppress default = 2
> Entries per page = 10
> 
> [Forum]
> ; general options
> Password file = /usr/local/elogdemo/logbooks/forum/passwd
> Admin user = stefan
> Self register = 2
> Theme = default
> Comment = Discussion forum about ELOG
> Data dir = /usr/local/elogdemo/logbooks/forum
> Display mode = threaded
> Start page = ?cmd=Search&mode=threaded
> Menu commands = Back, New, Edit, Reply, Find, Last day, Last 10, Admin, 
> Config, Logout, Help
> Find menu commands = New, Find, Last x, Admin, Config, Logout, Help
> Guest menu commands = Back, Find, Login, Help
> Guest find menu commands = Find, Login, Help
> Number Attachments = 1
> Message comment = <img src=icons/icon6.gif> Please enter only serious 
> messages here, for testing use the <b>Linux</b> Logbook:
> Filtered browsing = 0
> Entries per page = 8
> Reverse sort = 1
> Restrict edit = 1
> 
> ; Attributes
> Attributes = Icon, Author, Author Email, Category, Subject
> IOptions Icon = icon1.gif, icon2.gif, icon3.gif, icon4.gif, icon5.gif, 
> Options Category = Info, Bug report, Bug fix, Question, Request, Comment, 
> Other
> icon6.gif, icon7.gif, icon8.gif, icon12.gif, icon13.gif, icon14.gif
> Required Attributes = Author, Author Email, Subject, Icon
> Subst on reply subject = Re: $subject
> Thread display = $subject, posted by $author on $Entry date
> Thread icon = Icon
> Remove on reply = Author, Author Email
> Date format = %B %d, %Y
> Preset Author = $long_name
> Preset Author Email = $user_email
> Locked Attributes = Author
> 
> ; Email notification
> Email message body = 1
> Display Email recipients = 0

> Just since some people asked for: Here is the elogd.cfg for this demo 

quite a few things i wanted to do were in that config :)

the only feature i can think of now is a link on the subject in threaded display mode. 

i really crank up the resolution on my monitor, so i tend to miss clicking on the icon (or message number...

When logging in with a username and password; then trying to logout or 
change password one gets the following message:

Error: Parameter value too big. Please increase VALUE_SIZE and recompile 
elogd ; Please use your browser's back button to go back 

(up to now I have not yet tried to recompile - may be it works then)

Regards,

Stefan

> When logging in with a username and password; then trying to logout or 
> change password one gets the following message:
> 
> Error: Parameter value too big. Please increase VALUE_SIZE and recompile 
> elogd ; Please use your browser's back button to go back 
> 
> (up to now I have not yet tried to recompile - may be it works then)

That's strange. This error should only occur if someone uses a user name or 
password with more than 256 characters, which I hope is not the case. Have 
you tried changing your password etc. in this forum? It also runs 2.1.0 on 
Linux.

I made a version under 

http://midas/cgi-bin/cvsweb/~checkout~/elog/elogd.c?rev=2.67&content-
type=text/plain

which has improved error output for this problem, maybe this helps.

> > When logging in with a username and password; then trying to logout or 
> > change password one gets the following message:
> > 
> > Error: Parameter value too big. Please increase VALUE_SIZE and recompile 
> > elogd ; Please use your browser's back button to go back 
> > 
> > (up to now I have not yet tried to recompile - may be it works then)
> 
> That's strange. This error should only occur if someone uses a user name or 
> password with more than 256 characters, which I hope is not the case. Have 
> you tried changing your password etc. in this forum? It also runs 2.1.0 on 
> Linux.
> 
> I made a version under 
> 
> http://midas/cgi-bin/cvsweb/~checkout~/elog/elogd.c?rev=2.67&content-
> type=text/plain
> 
> which has improved error output for this problem, maybe this helps.

Hi, 

changed the VALUE_SIZE from 256 to 512. That seems to fix the problem.

Regards,

Stefan

i seem to be unable to find a clear explanation of how to enable self-registration in the docs.

just to be sure i grepped the doc directory, but the two references to it were in the changelog and the faq.

it could be just me but i'm not reading between the lines or connecting the various places in the docs to get it going :/

> i seem to be unable to find a clear explanation of how to enable self-
registration in the docs.
> 
> just to be sure i grepped the doc directory, but the two references to it 
were in the changelog and the faq.
> 
> it could be just me but i'm not reading between the lines or connecting the 
various places in the docs to get it going :/

Sorry, I haven't fully documented it yet, will do on Monday next week. For 
now, see the configuration file for this forum which is attached.

> Sorry, I haven't fully documented it yet, will do on Monday next week. For 
> now, see the configuration file for this forum which is attached.

that's ok. i just wanted to make sure that i hadn't missed something. i'm eventually switching over my entire dial up bbs, to my web page, with elog being the message system. self-registration was the last piece of the puzzle for me :)

Hello,

Is there a possibility to prevent elog to overwrite attribute values when 
editing an old message? The old values are overwriten with the preset 
options for that attribute. 
But sometimes you will preserve attribute text and /or options from the old 
message.

Thank you for your help. Regards,

Stefan

> Is there a possibility to prevent elog to overwrite attribute values when 
> editing an old message? The old values are overwriten with the preset 
> options for that attribute. 
> But sometimes you will preserve attribute text and /or options from the old 
> message.

The option "Fixed attributes = ..." will do the job.

> > Is there a possibility to prevent elog to overwrite attribute values when 
> > editing an old message? The old values are overwriten with the preset 
> > options for that attribute. 
> > But sometimes you will preserve attribute text and /or options from the 
old 
> > message.
> 
> The option "Fixed attributes = ..." will do the job.

Ok, but is there a possibility to preserve the fields of the old message, but 
still be able to edit it. This would be a nice feature in the case of an entry 
with lots of attributes (set to something different then the preset values). 
After submiting the message you realize : one option was wrong and now you 
want to edit it without changing the other options again.
Is this possible?

Thank you and best regards,

Stefan

> Ok, but is there a possibility to preserve the fields of the old message, 
but 
> still be able to edit it. This would be a nice feature in the case of an 
entry 
> with lots of attributes (set to something different then the preset 
values). 
> After submiting the message you realize : one option was wrong and now you 
> want to edit it without changing the other options again.
> Is this possible?

Actually this is a good idea. After thinking a while, I wonder if anybody at 
all would like not to preserve the preset values. So if nobody complains, I 
will set the behaviour such that elog always preserves the entries if one 
edits an existing message.

When an entry is submitted with an required attribute missing one gets to 
the resubmit page. When you the click your browsers back button all 
previously filled attribute field are blank.

Is there a workaround to get the old text back?

used versions:
Elog 2.0.5
Netscape 4.76

Best regards,

Stefan

> When an entry is submitted with an required attribute missing one gets to 
> the resubmit page. When you the click your browsers back button all 
> previously filled attribute field are blank.
> 
> Is there a workaround to get the old text back?
> 
> used versions:
> Elog 2.0.5
> Netscape 4.76
> 
> Best regards,
> 
> Stefan

This problem must be specific to NS 4.76, I don't have it on IE, NS 6, Mozilla
1, Opera etc. Maybe you should upgrade. Anybody else made this observation? 

Comiling elogd 2.0.4 under Solaris obviously fails with

gcc  -o elog elog.c -lsocket -lnsl
gcc  -o elogd elogd.c -lsocket -lnsl
elogd.c: In function `ss_file_find':
elogd.c:1372: `alphasort' undeclared (first use in this function)
elogd.c:1372: (Each undeclared identifier is reported only once
elogd.c:1372: for each function it appears in.)
make: *** [elogd] Error 1

because alphasort is an ucb'ism which does not exist under SYSV

... not very portable :-(

> Comiling elogd 2.0.4 under Solaris obviously fails with
> 
> gcc  -o elog elog.c -lsocket -lnsl
> gcc  -o elogd elogd.c -lsocket -lnsl
> elogd.c: In function `ss_file_find':
> elogd.c:1372: `alphasort' undeclared (first use in this function)
> elogd.c:1372: (Each undeclared identifier is reported only once
> elogd.c:1372: for each function it appears in.)
> make: *** [elogd] Error 1
> 
> because alphasort is an ucb'ism which does not exist under SYSV
> 
> ... not very portable :-(

I was not aware of this. Actually, I don't need 'alphasort' so I removed it 
from the source. The update is at

http://midas.psi.ch/cgi-bin/cvsweb/elog/elogd.c

Please give it a try.

> > Comiling elogd 2.0.4 under Solaris obviously fails with
> > 
> > gcc  -o elog elog.c -lsocket -lnsl
> > gcc  -o elogd elogd.c -lsocket -lnsl
> > elogd.c: In function `ss_file_find':
> > elogd.c:1372: `alphasort' undeclared (first use in this function)
> > elogd.c:1372: (Each undeclared identifier is reported only once
> > elogd.c:1372: for each function it appears in.)
> > make: *** [elogd] Error 1
> > 
> > because alphasort is an ucb'ism which does not exist under SYSV
> > 
> > ... not very portable :-(
> 
> I was not aware of this. Actually, I don't need 'alphasort' so I removed it 
> from the source. The update is at
> 
> http://midas.psi.ch/cgi-bin/cvsweb/elog/elogd.c
> 
> Please give it a try.

ok - i just continued with 2.0.5, but apparently it still has an UCB'ism
(scandir) that does not work under SYSV:

$ make
gcc -g -o elogd elogd.c -lsocket -lnsl
Undefined                       first referenced
 symbol                             in file
scandir                             /tmp/ccy0Z3iV.o
ld: fatal: Symbol referencing errors. No output written to elogd
collect2: ld returned 1 exit status
make: *** [elogd] Error 1
$ egrep scandir elogd.c
  n = scandir(path, &namelist, NULL, NULL);
$ 

> > > Comiling elogd 2.0.4 under Solaris obviously fails with
> > > 
> > > gcc  -o elog elog.c -lsocket -lnsl
> > > gcc  -o elogd elogd.c -lsocket -lnsl
> > > elogd.c: In function `ss_file_find':
> > > elogd.c:1372: `alphasort' undeclared (first use in this function)
> > > elogd.c:1372: (Each undeclared identifier is reported only once
> > > elogd.c:1372: for each function it appears in.)
> > > make: *** [elogd] Error 1
> > > 
> > > because alphasort is an ucb'ism which does not exist under SYSV
> > > 
> > > ... not very portable :-(
> > 
> > I was not aware of this. Actually, I don't need 'alphasort' so I removed 
it 
> > from the source. The update is at
> > 
> > http://midas.psi.ch/cgi-bin/cvsweb/elog/elogd.c
> > 
> > Please give it a try.
> 
> ok - i just continued with 2.0.5, but apparently it still has an UCB'ism
> (scandir) that does not work under SYSV:
> 
> $ make
> gcc -g -o elogd elogd.c -lsocket -lnsl
> Undefined                       first referenced
>  symbol                             in file
> scandir                             /tmp/ccy0Z3iV.o
> ld: fatal: Symbol referencing errors. No output written to elogd
> collect2: ld returned 1 exit status
> make: *** [elogd] Error 1
> $ egrep scandir elogd.c
>   n = scandir(path, &namelist, NULL, NULL);
> $ 
I am having the same experience with ELOG 2.0.5 and Solaris 8. Any work 
around woud be appreciated.

> > > > Comiling elogd 2.0.4 under Solaris obviously fails with
> > > > 
> > > > gcc  -o elog elog.c -lsocket -lnsl
> > > > gcc  -o elogd elogd.c -lsocket -lnsl
> > > > elogd.c: In function `ss_file_find':
> > > > elogd.c:1372: `alphasort' undeclared (first use in this function)
> > > > elogd.c:1372: (Each undeclared identifier is reported only once
> > > > elogd.c:1372: for each function it appears in.)
> > > > make: *** [elogd] Error 1
> > > > 
> > > > because alphasort is an ucb'ism which does not exist under SYSV
> > > > 
> > > > ... not very portable :-(
> > > 
> > > I was not aware of this. Actually, I don't need 'alphasort' so I 
removed 
> it 
> > > from the source. The update is at
> > > 
> > > http://midas.psi.ch/cgi-bin/cvsweb/elog/elogd.c
> > > 
> > > Please give it a try.
> > 
> > ok - i just continued with 2.0.5, but apparently it still has an UCB'ism
> > (scandir) that does not work under SYSV:
> > 
> > $ make
> > gcc -g -o elogd elogd.c -lsocket -lnsl
> > Undefined                       first referenced
> >  symbol                             in file
> > scandir                             /tmp/ccy0Z3iV.o
> > ld: fatal: Symbol referencing errors. No output written to elogd
> > collect2: ld returned 1 exit status
> > make: *** [elogd] Error 1
> > $ egrep scandir elogd.c
> >   n = scandir(path, &namelist, NULL, NULL);
> > $ 
> I am having the same experience with ELOG 2.0.5 and Solaris 8. Any work 
> around woud be appreciated.

I removed also scandir() in the current version (right now only in CVS). The 
official release of 2.1.0 is planned for next week.

Hi,

I added many features to ELOG recently, but before making a new release, I 
would like some beta testing. In addition to the current modes of 
operation, a logbook can be configured to require a user to be logged in to 
submit new messages. If not logged it, one can only read messages. To 
obtain a new account, one can do a self-registering. In this process, one 
can also enter the email address which is then filled in automatically on 
new logbook entries.

So please go to the forum logbook, create a new account for yourself and 
try things out. If there is any problem, please let me know.

Many thanks in advance, Stefan Ritt.