Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 735 of 796  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OS ELOG Version Subject
  541   Tue May 11 19:35:11 2004 Reply Marc Neigerm.neiger@synergie-inf.comBug reportWindows2.5.2Re: Extendable options
> > 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.
  540   Tue May 11 11:18:24 2004 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.5.2Re: Extendable options
> 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.
  539   Tue May 11 11:08:33 2004 Reply Marc Neigerm.neiger@synergie-inf.comBug reportWindows2.5.2Re: Extendable options
> > 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....
  538   Tue May 11 10:44:55 2004 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.5.2Re: Extendable options
> Is it possible to have a conditionnal attribute depend on an extendanble one ?

In principle yes, but I never tried it...
  537   Tue May 11 10:42:44 2004 Reply Marc Neigerm.neiger@synergie-inf.comBug reportWindows2.5.2Re: Extendable options
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
  536   Mon May 10 21:57:49 2004 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.5.2Re: Extendable options
> 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
  535   Mon May 10 00:00:06 2004 Warning Marc Neigerm.neiger@synergie-inf.comBug reportWindows2.5.2Extendable options
Hi,

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 ?

Are extendable and conditionnal "compatible" on the same set of attributes ?

Cheers,
Marc
Attachment 1: elogd.cfg
[global]
logbook tabs = 1
port = 8081
; on reste en anglais car les textes francais sont trop longs
;Language = french
Date format = %d/%m/%y %H:%M
Password file = passwords.txt
Login expiration = 24
Self register = 0

SMTP host = archie.gsi.synergie-inf.com
Suppress Email to users = 1

; attributs communs
Options Client = CE Astrium, Cofogar, Deco Ouest, GA, Mairie StO, RTS, Subra, Swap-Data
Extendable options = Client

[Routeurs]
Theme = default
Comment = Gestion des routeurs
Attributes = Author, Client, Equipment, Category, Summary
Preset Author = $short_name
Options Category = Modification, Update, Correction, Installation, Autre
Required Attributes = Client, Equipment, Category
Locked Attributes = Author
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Client, Equipment, Category

[Liste Routeurs]
Theme = default
Comment = Liste des routeurs
Attributes = Client, Equipment, EqType, HostName
Required Attributes = Client, Equipment, EqType
Options EqType = FWL1, FWL2, VPN1, VPN2
Page Title = Equipement - $Equipment
Quick filter = Client, EqType
Menu commands = Back, New, Edit, Delete, Find, Help
Summary lines = 6

[Problems]
Theme = default
Comment = Problemes et Knowledgebase
Attributes = Author, PbType, PbStatus, Priority, Client, Equipment, Description
Options PbType = Event, System, Applic, Other
Options PbStatus = Reported, Confirmed, Investigating, Testing, Solved, Suspended
Options Priority = 1 Critical, 2 Urgent, 3 Normal, 4 Background, 5 Low
Required Attributes = Author, PbType, PbStatus, Priority, Description
Quick Filter = Author, PbStatus, PbType
Locked Attributes = Author
Fixed Attributes Reply = PbType
Preset Author = $short_name
Display mode = threaded
Reverse Sort = 1
Quote On Reply = 0

[ProblemsA]
Theme = default
Comment = Problemes et Knowledgebase, single entry
Attributes = Author, PbType, PbStatus, Revisions, Priority, Client, Equipment, Description
Options PbType = Event, System, Applic, Other
Options PbStatus = Reported, Confirmed, Investigating, Testing, Solved, Suspended
Options Priority = 1 Critical, 2 Urgent, 3 Normal, 4 Background, 5 Low
Required Attributes = Author, PbType, PbStatus, Priority, Description
Quick Filter = Author, PbStatus, PbType
Locked Attributes = Author, Revisions
Fixed Attributes Reply = PbType
Preset Author = $short_name
Menu commands = Back, New, Edit, Delete, Find, Help
Reverse Sort = 1
Subst on Edit Revisions = $Revisions
$date par $short_name
  534   Wed May 5 17:38:12 2004 Reply Stefan Rittstefan.ritt@psi.ch Linux2.5.2Re: safari browser issue
> we've experienced a problem when using the safari browser to do a search in
> our elog. whenever you do a search, the logbook returns an error and the
> elog deamon crashes. when we first experienced this problem we were running
> version 2.3.9. however, an upgrade to version 2.5.2 doesn't seem to fix the
> problem. searches with other browsers (mozilla, internet explorer, ...) go
> off without a hitch.
> has anyone else observed a similar problem or have any ideas on how to
> resolve this issue.
> thanks for the help.

I finally found some time to address this problem. It was related to the way I
do the page redirection. The "Location:" in the HTTP header used a relative
path, although the standard requires an absolute (full) path, which I just
discovered. Although most browsers accept a relative path, the safari browser
obviously does not. 

I changed the redirection to absolute paths, the new version can be obtained
via CVS.
ELOG V3.1.5-2eba886