> > > Title says all :)
> > >
> > > Is it possible to preload Options or Moptions from a text file or CSV instead of being load from the elogd.conf ?
> > >
>
> So basically, I have a list of 5-10 workers. I'll have to choose one for each entry I make into the logbook. But these workers will change from time to time
> (students) and I don't want the staff to manipulate the config file manually..("Extendable options" is not an option as I will get to many "Darth Vader" entry for
> sure..)
>
> I asked if I could populate that option box from another logbook attribute and Andreas told me only possible via external scripts.
> https://midas.psi.ch/elogs/Forum/67877
Hi Francois.
if those worker lists do change rather infrequently, then I would have an idea how to do it:
You could have an application that updates the Options or MOptions lists in the elogd.cfg file at midnight,
and in case they actually did change the application restarts the elogd process afterwards.
I use such a mechanism to update my user list from our companies LDAP service every second Monday of a month at midnight.
This avoids misspelled user names or wrong email addresses and takes care that all employees (~2000) can log-in to our ELOG.
The passwords are handled anyway by kerberos authentication.
But I admit that it would be a cool feature to have "includes" in the configuration file for dynamic data sources.
Shell scripts of course are useless for "Option" definitions: they would only be executed at start-up anyway,
and that can be accomplished as well by the above mentioned automatic changes to the config file.
Kind Regards
Andreas |