Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon3.gif   "User" and "Group" statements changed from Version 2.2.5, posted by Stefan Ritt on Tue Jan 7 17:49:40 2003 
    icon5.gif   Re: 'group' option in conflict with 'guest logic' and 'LogBook Tabs' option , posted by Etienne Van Caillie on Sat Jan 11 19:26:24 2003 
       icon2.gif   Re: 'group' option in conflict with 'guest logic' and 'LogBook Tabs' option , posted by Stefan Ritt on Mon Jan 13 11:43:37 2003 
Message ID: 196     Entry time: Mon Jan 13 11:43:37 2003     In reply to: 194
Icon: Reply  Author: Stefan Ritt  Author Email: stefan.ritt@psi.ch 
Category: Bug report  OS:   ELOG Version:  
Subject: Re: 'group' option in conflict with 'guest logic' and 'LogBook Tabs' option  
> 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
ELOG V3.1.5-fe60aaf