> small problem :
> ****************
> Logbook Tabs = 0 in the guest logbook will close the group header
> may be create a parameter to solve ?
> GroupGuest Extranet = ....
What I would recommend in that case is to run two copies of elogd in
parallel, one for the public and one for the private section. They can even
run on differnt ports so the firewall can block the private section. If the
private logbooks are not defined in the public elogd, they don't show up in
the logbook tabs, so only the publick logbook tabs are seen. Please note
that two elogd daemons should not have concurrent write access to the same
logbook, since there is not locking and the logbook could get messed up that
way. So only one elogd should have write access to any logbook.
- Stefan |