> For some reason if I define a "login user" that is allowed the configure
> option he is also allowed to change the configuration file. According to the
> documentation it seems like this should NOT be the case. Any ideas as to
> what the problem might be? 

Unfortunately I cannot reproduce your problem. This leaves few possibilites:

- any login user CAN change his/her full name, email address etc. but only admin
users can change ALL OTHERS as well. Admin users should see a "change elogd.cfg"
button on the config page, whil normal users will not

- are you sure you logged out as admin user and loggin in again as non-admin
user? Under some circumstances, the browser keeps old cookies which can confuse
things. Best is if you delete all browser cookies and try again (Tools/Internet
Options/Delete Cookies in IE).

- Stefan

Hello,

For some reason if I define a "login user" that is allowed the configure
option he is also allowed to change the configuration file. According to the
documentation it seems like this should NOT be the case. Any ideas as to
what the problem might be? 

Thanks in advance for any help/advice.

Ralph 

I'm trying capture any edit/modified entry with the following, Using the
real date format instead of text string so that I could do a quick filter on it.

Type modified = date
Subst on Edit modified = $date

Problem: It seem that the Subst on Edit always default to 1 Jan 1970 instead
of current date on edit screen. 

Could it be $date is a string and not compatible with tape date? or is there
a variable or function to convert $date to date format?
 
Thanks,
nait

> > The snapshot version you sent me seems to be locked onto port 80 and does not honor 
> > the port directive in elog.cfg....
> 
> Thank you, I fixed that and updated the file.

Tested and working, thx.

> The snapshot version you sent me seems to be locked onto port 80 and does not honor 
> the port directive in elog.cfg....

Thank you, I fixed that and updated the file.

> > Is it possible to have a conditionnal attribute depend on an extendanble one ?
> 
> In principle yes, but I never tried it...

The snapshot version you sent me seems to be locked onto port 80 and does not honor 
the port directive in elog.cfg....

> Is it possible to have a conditionnal attribute depend on an extendanble one ?

In principle yes, but I never tried it...

Hi Stefan,

Many thanks, it works. I'm impressed by your reactivity ! thanks again.

Is it possible to have a conditionnal attribute depend on an extendanble one ?


> > the use of extendable options in the global section seem to "crash" elogd 
> > when creating a new entry.
> > My elogd.cfg is included
> > the problem attribute is "Client"
> > Should it be possible to have it extendable only in one specific logbook ?
> 
> Actually it was never foreseen to have extendable options in the [global]
> section. I added now this functionality. The new windows version can be obtained
> under
> 
> http://midas.psi.ch/elog/download/windows/elogd-snapshot.exe