The exit status of elog is always 1.  It should be zero for
a successful submission.

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

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 :)

Couple Wish List Items for the Self Register:

-allow the user to pick which type of log entries (which categories, etc) 
they would like to subscribe to and receive notifications on.   

-Option to use an existing LDAP database to authenticate users instead of 
maintaining a password file.

Also having the ability to subscribe to notifications for one or more 
logbooks (if access is given - along with the ability to choose which 
categories, etc notifications are sent.


> Couple Wish List Items for the Self Register:
> 
> -allow the user to pick which type of log entries (which categories, etc) 
> they would like to subscribe to and receive notifications on.   
> 
> -Option to use an existing LDAP database to authenticate users instead of 
> maintaining a password file.

Is it possible to make the author and pwd check case in-sensitive??  I 
noticed that unless you type your userid and password in the same case each 
time, the system doesn't recognize your or thinks the info is invalid.

thanks,
eric

Some options for the password setting:
The ability that if admin creates a temporary password for the user, force 
the user to change the password once logged in.

User forgets password, system generates a random pwd and sends it to user 
via email, after they log in force pwd change. 

option to expire an account or expire a pwd after so many days??

just some ideas..

still loving the new features!!