ELOG Config Examples

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Configuration examples for ELOG, Page 2 of 2

Not logged in

Find | Login | Help

Full | Summary | Threaded | Hide attachments

20 Entries

Goto page Previous 1, 2 All

Mon Jul 10 21:48:23 2006

Arno Teunisse

arno.teunisse@hetnet.nl

Personal Logbook

webmouse

trying to write a time keeping system with elog. At work this is done with an Excel Sheet. Was just trying to see if it could be done with elog. And Yes it can be done. There is only one disadvantage : it's very slow in stating up. Has this to do with the large listings I've included into the configutation file , or is there something wrong in my config file.???

Is there somebody with an advice for this one ??

Attachment 1: webmouse.cfg

[global]
/* Logbook Tabs = 0
Time Format =   %d-%b-%y %H:%M
CSS = tiny.css
Password file = passwd
Admin user = Arnot
Self register = 1
Allow password change = 1


[webmouse]

Attributes = Naam,EmpNum,Week,Dag,Soort,Klantnaam,SO,Uren,Werkzaamheden,Afdeling,Urensoort,Urencode,ULS,Controle
Link display = Naam,EmpNum
Preset Naam=$short_name
Hidden Attributes = Date
Required Attributes = Naam,EmpNum,Week,Dag,Afdeling,Uren,Urensoort,Urencode,ULS
subst Naam = $short_name
Roptions Dag = Mon,Tue,Wed,Thu,Fri,Sat,Sun
Options Week = 1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,
options Soort = SLA{1},Service Order{2},PROJ{3},NEW{4}
{1}options Klantnaam  = SLA_Arag beheer Q3 2006{1_1},SLA_ASML BlackBerry Beheer Q3 2006{1_2},SLA_BAT Beheer Q3 2006{1_3},SLA_Beter Horen Acoudire WAN Beheer Q3 2006{1_4},SLA_Beter Horen Acoudire Server Beheer Q3 2006{1_5},SLA_Bodemsanering NS  Beheer Q3 2006{1_6},SLA_Breman  beheer Q3 2006{1_7},SLA_Compliance Beheer Q3 2006{1_8},SLA_DocData beheer Q3 2006{1_9},SLA_Edutel Beheer Q3 2006{1_10},SLA_Efteling Beheer Q3 2006{1_11},SLA_EMI Beheer Q3 2006{1_12},SLA_EPZ Borssele Beheer AS/400 Q3 2006{1_13},SLA_Combo/Essent  Beheer 2006{1_14},SLA_Combo/Essent Helpdesk 2006{1_15},SLA_Etam Retail Service beheer Q3 2006{1_16},SLA_Essent AS-400 Beheer Q3 2006{1_17},SLA_Expo Beheer Q3 2006{1_18},SLA_FM Beheerwerkz.CCx-operator-NOS  Q3 2006{1_19},SLA_FM Beheerwerkz.CCV-operator-LWT  Q3 2006{1_20},SLA_FM Change Office Q3 2006{1_21},SLA_FM Infrastructuur Q3 2006{1_22},SLA_FM Telecity geheel 2006{1_23},SLA_Fontys hogescholen Q3 2006{1_24},SLA_Frieslandbank LAN Q3 2006{1_25},SLA_Frieslandbank WAN Q3 2006{1_26},SLA_Frieslandbank  Citrix  Q3 2006{1_27},SLA_Frieslandbank Unix Q3 2006{1_28},SLA_The Greenery Q3 2006{1_29},SLA_Harcourt Q3 2006{1_30},SLA_Hema Beheer Ethernet Switch Q3 2006{1_31},SLA_Hymec Beheer Q3 2006{1_32},SLA_Hypotheker Helpdesk Q3 2006{1_33},SLA_Hypotheker DSL Beheer Q3 2006{1_34},SLA_Hypotheker Centrale Omgeving Q3 2006{1_35},SLA_Hypotheker Werkplek/Deskforce Q3 2006{1_36},SLA_Hypotheekshop Beheer Q3 2006{1_37},SLA_Interaccess NoLimit Beheer Q3 2006{1_38},SLA_Jamin Beheer Q3 2006{1_39},SLA_Kiwa beheer Q3 2006 Rijswijk{1_40},SLA_Kiwa beheer Q3 2006 Nieuwegein{1_41},SLA_Kiwa Wateropleidingen  Q3 2006{1_42},SLA_Kiwa Apeldoorn Q3 2006{1_43},SLA_Laurus Winkelnetwerk Q3 2006{1_44},SLA_Laurus Werkplekbeheer Q3 2006{1_45},SLA_Laurus Winkeltaken Q3 2006{1_46},SLA_Laurus Helpdesk Q3 2006{1_47},SLA_Laurus Incident Solving Winkels Q3 2006{1_48},SLA_Malmberg Beheer Q3 2006{1_49},SLA_Helpdesk Malmberg Q3 2006{1_50},SLA_MCB werkplekbeheer obv inspanning Q3 2006{1_51},SLA_MRG Beheer Q3 2006{1_52},SLA_MRG Belcompany Q3 2006{1_53},SLA_MRG Kwantum Beheer Q3 2006{1_54},SLA_MRG Piet klerkx Q3 2006{1_55},SLA_Neways Beheer Q3 2006{1_56},SLA_Gemeente Nijmegen  Q3 2006{1_57},SLA_NRE Beheer Q3 2006{1_58},SLA_Philips Beheer Q3 2006{1_59},SLA_Philips SC AS wkzh. Q3 2006{1_60},SLA_Pon beheer Q3 2006{1_61},SLA_PON Midrange Beheer Q3 2006{1_62},SLA_PON Datawarehouse beheer Q3 2006{1_63},SLA_Probiblio Beheer Q3 2006{1_64},SLA_RIBW Nijmegen Rivierenland  Beheer Q3 2006{1_65},SLA_RIBW Den Haag Beheer Q3 2006{1_66},SLA_Schoonenberg Beheer Q3 2006{1_67},SLA_Simac Broadcast Beheer Q3 2006{1_68},SLA_Simac ICT IT Shop Q3 2006{1_69},SLA_Simac ICT Telefonie Q3 2006{1_70},SLA_Simac ICT ERP Q3 2006{1_71},SLA_Simac: ICT KA Q3 2006{1_72},SLA_Simac Triangle Q3 2006{1_73},SLA_SNV Beheer Q3 2006{1_74},SLA_Twice Beheer Q3 2006{1_75},SLA_V&D Winkelwerkplek Beheer Q3 2006{1_76},SLA_Vendex KBB VKRN Vast Beheer Q3 2006{1_77},SLA_Vendex KBB - ADSL Beheer Q3 2006{1_78},SLA_VVAA Semic Beheer Q3 2006{1_79},SLA_VVAA LAN Beheer Q3 2006{1_80},SLA_VVAA Bureau Hufen Beheer Q3 2006{1_81},SLA_VVAA Reisbureau Beheer Q3 2006{1_82},SLA_VVAA Congres en Evenementen Q3 2006{1_83},SLA_VVAA Praktijk Adviseurs Q3 2006{1_84},SLA_Wagner & Partners Beheer Q3 2006{1_85},SLA_Watermark Beheer Q3 2006{1_86},SLA_Zeeman Beheer Q3 2006{1_87}
/* SLA_Arag beheer Q3 2006{1_1},SLA_ASML BlackBerry Beheer Q3 2006{1_2},SLA_BAT Beheer Q3 2006{1_3},SLA_Beter Horen Acoudire WAN Beheer Q3 2006{1_4},SLA_Beter Horen Acoudire Server Beheer Q3 2006{1_5},SLA_Bodemsanering NS  Beheer Q3 2006{1_6},SLA_Breman  beheer Q3 2006{1_7},SLA_Compliance Beheer Q3 2006{1_8},SLA_DocData beheer Q3 2006{1_9},SLA_Edutel Beheer Q3 2006{1_10},SLA_Efteling Beheer Q3 2006{1_11},SLA_EMI Beheer Q3 2006{1_12},SLA_EPZ Borssele Beheer AS/400 Q3 2006{1_13},SLA_Combo/Essent  Beheer 2006{1_14},SLA_Combo/Essent Helpdesk 2006{1_15},SLA_Etam Retail Service beheer Q3 2006{1_16},SLA_Essent AS-400 Beheer Q3 2006{1_17},SLA_Expo Beheer Q3 2006{1_18},SLA_FM Beheerwerkz.CCx-operator-NOS  Q3 2006{1_19},SLA_FM Beheerwerkz.CCV-operator-LWT  Q3 2006{1_20},SLA_FM Change Office Q3 2006{1_21},SLA_FM Infrastructuur Q3 2006{1_22},SLA_FM Telecity geheel 2006{1_23},SLA_Fontys hogescholen Q3 2006{1_24},SLA_Frieslandbank LAN Q3 2006{1_25},SLA_Frieslandbank WAN Q3 2006{1_26},SLA_Frieslandbank  Citrix  Q3 2006{1_27},SLA_Frieslandbank Unix Q3 2006{1_28},SLA_The Greenery Q3 2006{1_29},SLA_Harcourt Q3 2006{1_30},SLA_Hema Beheer Ethernet Switch Q3 2006{1_31},SLA_Hymec Beheer Q3 2006{1_32},SLA_Hypotheker Helpdesk Q3 2006{1_33},SLA_Hypotheker DSL Beheer Q3 2006{1_34},SLA_Hypotheker Centrale Omgeving Q3 2006{1_35},SLA_Hypotheker Werkplek/Deskforce Q3 2006{1_36},SLA_Hypotheekshop Beheer Q3 2006{1_37},SLA_Interaccess NoLimit Beheer Q3 2006{1_38},SLA_Jamin Beheer Q3 2006{1_39},SLA_Kiwa beheer Q3 2006 Rijswijk{1_40},SLA_Kiwa beheer Q3 2006 Nieuwegein{1_41},SLA_Kiwa Wateropleidingen  Q3 2006{1_42},SLA_Kiwa Apeldoorn Q3 2006{1_43},SLA_Laurus Winkelnetwerk Q3 2006{1_44},SLA_Laurus Werkplekbeheer Q3 2006{1_45},SLA_Laurus Winkeltaken Q3 2006{1_46},SLA_Laurus Helpdesk Q3 2006{1_47},SLA_Laurus Incident Solving Winkels Q3 2006{1_48},SLA_Malmberg Beheer Q3 2006{1_49},SLA_Helpdesk Malmberg Q3 2006{1_50},SLA_MCB werkplekbeheer obv inspanning Q3 2006{1_51},SLA_MRG Beheer Q3 2006{1_52},SLA_MRG Belcompany Q3 2006{1_53},SLA_MRG Kwantum Beheer Q3 2006{1_54},SLA_MRG Piet klerkx Q3 2006{1_55},SLA_Neways Beheer Q3 2006{1_56},SLA_Gemeente Nijmegen  Q3 2006{1_57},SLA_NRE Beheer Q3 2006{1_58},SLA_Philips Beheer Q3 2006{1_59},SLA_Philips SC AS wkzh. Q3 2006{1_60},SLA_Pon beheer Q3 2006{1_61},SLA_PON Midrange Beheer Q3 2006{1_62},SLA_PON Datawarehouse beheer Q3 2006{1_63},SLA_Probiblio Beheer Q3 2006{1_64},SLA_RIBW Nijmegen Rivierenland  Beheer Q3 2006{1_65},SLA_RIBW Den Haag Beheer Q3 2006{1_66},SLA_Schoonenberg Beheer Q3 2006{1_67},SLA_Simac Broadcast Beheer Q3 2006{1_68},SLA_Simac ICT IT Shop Q3 2006{1_69},SLA_Simac ICT Telefonie Q3 2006{1_70},SLA_Simac ICT ERP Q3 2006{1_71},SLA_Simac: ICT KA Q3 2006{1_72},SLA_Simac Triangle Q3 2006{1_73},SLA_SNV Beheer Q3 2006{1_74},SLA_Twice Beheer Q3 2006{1_75},SLA_V&D Winkelwerkplek Beheer Q3 2006{1_76},SLA_Vendex KBB VKRN Vast Beheer Q3 2006{1_77},SLA_Vendex KBB - ADSL Beheer Q3 2006{1_78},SLA_VVAA Semic Beheer Q3 2006{1_79},SLA_VVAA LAN Beheer Q3 2006{1_80},SLA_VVAA Bureau Hufen Beheer Q3 2006{1_81},SLA_VVAA Reisbureau Beheer Q3 2006{1_82},SLA_VVAA Congres en Evenementen Q3 2006{1_83},SLA_VVAA Praktijk Adviseurs Q3 2006{1_84},SLA_Wagner & Partners Beheer Q3 2006{1_85},SLA_Watermark Beheer Q3 2006{1_86},SLA_Zeeman Beheer Q3 2006{1_87}
{2}options Klantnaam  = SO_EPZ Borssele jaarorder Erwin de Kam 711447{2_1},SO_EPZ AS400 TAB /Chg./Inc.  Frans Mallens 711446{2_2},SO_Frieslandbank LAN  Changes 712276{2_3},SO_Frieslandbank Citrix Changes 712277{2_4},SO_Frieslandbank WAN Changes  712278{2_5},SO_Frieslandbank Unix Changes  712279{2_6},SO_Harcourt transformatie  711106{2_7},SO_Kiwa Apeldoorn laptop uitrol en niet-werkpl. Beheer 710424{2_8},SO_Laurus Transformatie 712608{2_9},SO_Philips Non standaard changes 712164{2_10},SO_Philip Morris Improvement werk Urenpotje 711602{2_11},SO_Philips Morris Extra werkzaamheden 711603{2_12},SO_Vendex VKRN Vast consultancy  709276{2_13}
{3}options Klantnaam  = PRJ_Laurus Pilot Retailix   900190{3_1}
{4}options Klantnaam  = SO_TMP{4_1}

{1_1}Roptions SO = 712702
{1_2}Roptions SO = 712703
{1_3}Roptions SO = 712706
{1_4}Roptions SO = 712704
{1_5}Roptions SO = 712705
{1_6}Roptions SO = 712707
{1_7}Roptions SO = 712708
{1_8}Roptions SO = 712709
{1_9}Roptions SO = 712710
{1_10}Roptions SO = 712711
{1_11}Roptions SO = 712712
{1_12}Roptions SO = 712713
{1_13}Roptions SO = 712714
{1_14}Roptions SO = 711437
{1_15}Roptions SO = 711442
{1_16}Roptions SO = 712715
{1_17}Roptions SO = 712716
{1_18}Roptions SO = 712312
{1_19}Roptions SO = 712717
{1_20}Roptions SO = 712718
{1_21}Roptions SO = 712311
{1_22}Roptions SO = 712719
{1_23}Roptions SO = 710530
{1_24}Roptions SO = 712720
{1_25}Roptions SO = 712722
{1_26}Roptions SO = 712721
{1_27}Roptions SO = 712724
{1_28}Roptions SO = 712723
{1_29}Roptions SO = 712773
{1_30}Roptions SO = 712778
{1_31}Roptions SO = 712725
{1_32}Roptions SO = 712726
{1_33}Roptions SO = 712728
{1_34}Roptions SO = 712729
{1_35}Roptions SO = 712730
{1_36}Roptions SO = 712727
{1_37}Roptions SO = 712731
{1_38}Roptions SO = 712732
{1_39}Roptions SO = 712733
{1_40}Roptions SO = 712734
{1_41}Roptions SO = 712736
{1_42}Roptions SO = 712737
{1_43}Roptions SO = 712735
{1_44}Roptions SO = 712738
{1_45}Roptions SO = 712609
{1_46}Roptions SO = 712610
{1_47}Roptions SO = 712611
{1_48}Roptions SO = 712612
{1_49}Roptions SO = 712739
{1_50}Roptions SO = 712740
{1_51}Roptions SO = 712826
{1_52}Roptions SO = 712742
{1_53}Roptions SO = 712741
{1_54}Roptions SO = 712743
{1_55}Roptions SO = 712744
{1_56}Roptions SO = 712745
{1_57}Roptions SO = 712746
{1_58}Roptions SO = 712747
{1_59}Roptions SO = 712748
{1_60}Roptions SO = 712749
{1_61}Roptions SO = 712771
{1_62}Roptions SO = 712845
{1_63}Roptions SO = 712846
{1_64}Roptions SO = 712750
{1_65}Roptions SO = 712751
{1_66}Roptions SO = 712752
{1_67}Roptions SO = 712753
{1_68}Roptions SO = 712754
{1_69}Roptions SO = 712758
{1_70}Roptions SO = 712755
{1_71}Roptions SO = 712756
{1_72}Roptions SO = 712757
{1_73}Roptions SO = 712776
{1_74}Roptions SO = 712759
{1_75}Roptions SO = 712777
{1_76}Roptions SO = 712760
{1_77}Roptions SO = 712761
{1_78}Roptions SO = 712762
{1_79}Roptions SO = 712764
{1_80}Roptions SO = 712765
{1_81}Roptions SO = 712766
{1_82}Roptions SO = 712768
{1_83}Roptions SO = 712763
{1_84}Roptions SO = 712767
{1_85}Roptions SO = 712769
{1_86}Roptions SO = 712770
{1_87}Roptions SO = 712772

{2_1}Roptions SO = 711447
{2_2}Roptions SO = 711446
{2_3}Roptions SO = 712276
{2_4}Roptions SO = 712277
{2_5}Roptions SO = 712278
{2_6}Roptions SO = 712279
{2_7}Roptions SO = 711106
{2_8}Roptions SO = 710424
{2_9}Roptions SO = 712608
{2_10}Roptions SO = 712164
{2_11}Roptions SO = 711602
{2_12}Roptions SO = 711603
{2_13}Roptions SO = 709276
{2_14}Roptions SO = 917443
{2_15}Roptions SO = 917446
{2_16}Roptions SO = 917445
{2_17}Roptions SO = 917453
{2_18}Roptions SO = 917461

{3_1}Roptions SO = 900190
O_T
{4_1} Preset SO = Enter SO here


; Urensoort is afhankelijk van CCV,CCE,Serv.Man.


options Afdeling = CCE{1a},ServiceManager{1c}


{1a}options Urensoort = Studie/Training{a_1},Parts Control{a_2},Verlof{a_3},Interne activiteiten{a_4},Ziek/bezoek arts{a_5},SM Activiteiten kleine klanten{a_6},SM Sales Ondersteuning{a_7},Engineer Sales Ondersteuning{a_8},Innovatie{a_9},Preventieve standby vrijgeroosterd{a_10},OR Werkzaamheden{a_11},Project HP ServiceDesk{a_12},&nbsp; ,SLA CCx Server Management{a_13},SLA CCx Network Management{a_14},SLA CCx Desktop Management{a_15},SLA CCx Telecom Management{a_16},SLA CCx Technisch Applicatie Beheer{a_17},SLA CCx Rapportage/overleg{a_18},SLA Reisuren{a_19},&nbsp; ,SLA SM Accountteam{a_20},SLA SM SLR Maken{a_21},SLA SM Pro/Chg/Inc coordinatie{a_22},SLA SM Proces verbetering{a_23},SLA SM Administratie/Facturatie{a_24},SLA SM Overleg{a_25},&nbsp; ,SO CCx Remote Support{a_26},SO CCx On-site Support{a_27},SO CCx Repair Intern{a_28},SO CCx Wvb (storing/change) planning{a_29},SO CCx Uitvoer non-standard change{a_30},SO CCx Reisuren{a_31},&nbsp; ,SO SM Voorbereiding{a_32},SO SM Concultancy{a_33},SO SM Nazorg/Overdracht{a_34},SO SM Reisuren{a_35},&nbsp; ,PRJ CCx Wvb Project{a_36},PRJ CCx Uitvoer Project{a_37},PRJ CCx Reisuren Project{a_38},&nbsp; ,PRJ SM Voorbereiding{a_39},PRJ SM Consultancy{a_40},PRJ SM Nazorg/overdracht{a_41},PRJ SM Reisuren{a_42},
{1c}options Urensoort = Studie/Training{c_1},Parts Control{c_2},Verlof{c_3},Interne activiteiten{c_4},Ziek/bezoek arts{c_5},SM Activiteiten kleine klanten{c_6},SM Sales Ondersteuning{c_7},Engineer Sales Ondersteuning{c_8},Innovatie{c_9},Preventieve standby vrijgeroosterd{c_10},OR Werkzaamheden{c_11},Project HP ServiceDesk{c_12},&nbsp; ,SLA CCx Server Management{c_13},SLA CCx Network Management{c_14},SLA CCx Desktop Management{c_15},SLA CCx Telecom Management{c_16},SLA CCx Technisch Applicatie Beheer{c_17},SLA CCx Rapportage/overleg{c_18},SLA Reisuren{c_19},&nbsp; ,SLA SM Accountteam{c_20},SLA SM SLR Maken{c_21},SLA SM Pro/Chg/Inc coordinatie{c_22},SLA SM Proces verbetering{c_23},SLA SM Administratie/Facturatie{c_24},SLA SM Overleg{c_25},&nbsp; ,SO CCx Remote Support{c_26},SO CCx On-site Support{c_27},SO CCx Repair Intern{c_28},SO CCx Wvb (storing/change) planning{c_29},SO CCx Uitvoer non-standard change{c_30},SO CCx Reisuren{c_31},&nbsp; ,SO SM Voorbereiding{c_32},SO SM Concultancy{c_33},SO SM Nazorg/Overdracht{c_34},SO SM Reisuren{c_35},&nbsp; ,PRJ CCx Wvb Project{c_36},PRJ CCx Uitvoer Project{c_37},PRJ CCx Reisuren Project{c_38},&nbsp; ,PRJ SM Voorbereiding{c_39},PRJ SM Consultancy{c_40},PRJ SM Nazorg/overdracht{c_41},PRJ SM Reisuren{c_42},


/* Please notice : below will link the activity to the SO number */
{a_1}Roptions Urencode = 8762
{a_2}Roptions Urencode = 8778
{a_3}Roptions Urencode = 8780
{a_4}Roptions Urencode = 8782
{a_5}Roptions Urencode = 8788
{a_6}Roptions Urencode = n.a.
{a_7}Roptions Urencode = n.a.
{a_8}Roptions Urencode = 8763
{a_9}Roptions Urencode = 8767
{a_10}Roptions Urencode = 8740
{a_11}Roptions Urencode = 8786
{a_12}Roptions Urencode = 8766
{a_13}Roptions Urencode = 8735
{a_14}Roptions Urencode = 8736
{a_15}Roptions Urencode = 8737
{a_16}Roptions Urencode = 8738
{a_17}Roptions Urencode = 8739
{a_18}Roptions Urencode = 8742
{a_19}Roptions Urencode = 8783
{a_20}Roptions Urencode = n.a.
{a_21}Roptions Urencode = n.a.
{a_22}Roptions Urencode = n.a.
{a_23}Roptions Urencode = n.a.
{a_24}Roptions Urencode = n.a.
{a_25}Roptions Urencode = n.a.
{a_26}Roptions Urencode = 8720
{a_27}Roptions Urencode = 8722
{a_28}Roptions Urencode = 8723
{a_29}Roptions Urencode = 8726
{a_30}Roptions Urencode = 8731
{a_31}Roptions Urencode = 8734
{a_32}Roptions Urencode = n.a.
{a_33}Roptions Urencode = n.a.
{a_34}Roptions Urencode = n.a.
{a_35}Roptions Urencode = n.a.
{a_36}Roptions Urencode = 8710
{a_37}Roptions Urencode = 8711
{a_38}Roptions Urencode = 8716
{a_39}Roptions Urencode = n.a.
{a_40}Roptions Urencode = n.a.
{a_41}Roptions Urencode = n.a.
{a_42}Roptions Urencode = n.a.


{c_1}Roptions Urencode = 8462
{c_2}Roptions Urencode = n.a.
{c_3}Roptions Urencode = 8480
{c_4}Roptions Urencode = 8464
{c_5}Roptions Urencode = 8488
{c_6}Roptions Urencode = 8465
{c_7}Roptions Urencode = 8463
{c_8}Roptions Urencode = n.a.
{c_9}Roptions Urencode = n.a.
{c_10}Roptions Urencode = n.a.
{c_11}Roptions Urencode = 8486
{c_12}Roptions Urencode = 8466
{c_13}Roptions Urencode = n.a.
{c_14}Roptions Urencode = n.a.
{c_15}Roptions Urencode = n.a.
{c_16}Roptions Urencode = n.a.
{c_17}Roptions Urencode = n.a.
{c_18}Roptions Urencode = n.a.
{c_19}Roptions Urencode = 8410
{c_20}Roptions Urencode = 8411
{c_21}Roptions Urencode = 8412
{c_22}Roptions Urencode = 8413
{c_23}Roptions Urencode = 8414
{c_24}Roptions Urencode = 8415
{c_25}Roptions Urencode = 8439
{c_26}Roptions Urencode = n.a.
{c_27}Roptions Urencode = n.a.
{c_28}Roptions Urencode = n.a.
{c_29}Roptions Urencode = n.a.
{c_30}Roptions Urencode = n.a.
{c_31}Roptions Urencode = n.a.
{c_32}Roptions Urencode = 8401
{c_33}Roptions Urencode = 8403
{c_34}Roptions Urencode = 8404
{c_35}Roptions Urencode = 8405
{c_36}Roptions Urencode = n.a.
{c_37}Roptions Urencode = n.a.
{c_38}Roptions Urencode = n.a.
{c_39}Roptions Urencode = 8441
{c_40}Roptions Urencode = 8443
{c_41}Roptions Urencode = 8444
{c_42}Roptions Urencode = 8445

Roptions ULS=100,150,200

Tue Jul 11 09:10:44 2006

Arno Teunisse wrote:

There is only one disadvantage: it's very slow in stating up. Has this to do with the large listings I've included into the configutation file , or is there something wrong in my config file.?

This has to do with the extensive use of conditional attributes. It has been reported by someone else recently and there is a fix: Just upgrade to Version 2.6.1-7 (SVN revision 1696). Also read the note about List conditions in the documentation.

Tue Jul 11 10:24:40 2006

Arno Teunisse

arno.teunisse@hetnet.nl

Personal Logbook

webmouse

Stefan Ritt wrote:

Arno Teunisse wrote:

There is only one disadvantage: it's very slow in stating up. Has this to do with the large listings I've included into the configutation file , or is there something wrong in my config file.?

Thanks for you're quick answer. I'm running version SVN 1695 ( which is the latest ) on windows. SVN 1696 is not available for this Operating System.

Tue Jul 11 10:38:44 2006

Arno Teunisse wrote:

I'm running version SVN 1695 ( which is the latest ) on windows. SVN 1696 is not available for this Operating System.

It is. Just use Version 2.6.2 which I released just now.

Tue Jul 11 22:27:25 2006

Arno Teunisse

arno.teunisse@hetnet.nl

Personal Logbook

webmouse

Stefan Ritt wrote:

Arno Teunisse wrote:

I'm running version SVN 1695 ( which is the latest ) on windows. SVN 1696 is not available for this Operating System.

It is. Just use Version 2.6.2 which I released just now.

Hello Stefan

Have some problem with elog. just upgraded to version 2.6.2. revision 1699 for windows

Below is the example from the "man-page"

[New_test]
List conditions = 1 /* for version 2.6.2 revision 1699 */

Attributes = PC Name, Operating System, Version, Location, Floor
Options Operating System = Linux{1}, Windows{2}
Options Location = Main Building{a}, New Building{b}, Old Building{c}
{1} Options Version = 2.2, 2.4, 2.6
{2} Options Version = ME, 2k, NT, XP
{a} Options Floor = Ground, First, Second
{b,c} Options Floor = Ground, First

If I use the above on version :
elogd 2.6.1 built Jul 5 2006, 12:49:34 revision 1695
Indexing logbooks ... done
Server listening on port 80 ...

All is working fine . But using verion 2.6.2 revision 1699 , No matter the option : List conditions = 1
The Floor options will not be displayed.

Maybe I'm missing something about the "list display" .

Can you show me a correct example. ??

Thu Jul 13 15:13:04 2006

Arno Teunisse wrote:

Have some problem with elog. But using verion 2.6.2 revision 1699 , No matter the option : List conditions = 1
The Floor options will not be displayed.

This does not have anything to do with List conditions but with a bug I introduced in 1696. I fixed it now in 1702. I will soon make a 2.6.2-2 containing that fix.

Draft

Sat Oct 7 16:22:15 2023

Ram Krishan Sharma

rks544@york.ac.uk

Personal Logbook

Wed Feb 26 09:24:42 2003

Stefan Ritt

stefan.ritt@psi.ch

Public Logbook

Config Examples (this logbook!)

Thu Jun 2 08:49:24 2005 by Stefan Ritt

This is the configuration from this logbook. There are a few special things:

it uses the same password file as the 'forum' logbook
it has a guest menu so that people without an account can read it
the author and email are automatically taken from the password file
a 'last revision' gets updated on each edit
entries can only changed by the origial author ('restrict edit = 1')
no email notification is sent

Please find the elogd.cfg attached.

Attachment 1: elogd.cfg

[Config Examples]
Comment = Configuration examples for ELOG

; same password as forum
Password file = /usr/local/elogdemo/logbooks/Forum/passwd
Login expiration = 1000
Admin user = stefan
Allow delete = stefan

; look and feel
CSS = examples.css
Display mode = summary
Guest menu commands = Back, Find, Login, Help
Guest find menu commands = Find, Login, Help
Date format = %B %d, %Y

; attributes
Attributes = Author, Author Email, Category, Configuration Name, Last Revision
Options Category = Personal Logbook, Public Logbook, Database like, Other
Required Attributes = Author, Author Email, Category, Configuration Name
Thread display = $Configuration Name, posted by $author on $Entry time
Quick filter = Date, Category

; preset author and email
Preset Author = $long_name
Preset Author Email = $user_email

; these attributes cannot be changed
Locked Attributes = Author, Last Revision

; add last revision on each edit
Subst on Edit Last Revision = $date by $long_name

; some comments showing up in the "new" page
Message comment = Please enter a description of your <b>elogd.cfg</b> here:
Attachment comment = Plese upload your <b>elogd.cfg</b> here:

; a few flags
Filtered browsing = 0
Entries per page = 10
Restrict edit = 1
Summary lines = 0

; options for reply
Subst on reply subject = Re: $Configuration Name
Remove on reply = Author, Author Email

; No Email notification
Suppress Email to users = 1

Wed Feb 26 09:45:23 2003

Wed Jul 14 21:49:36 2004 by Stefan Ritt

This is the configuration of the discussion forum on this server. Special 
things are:

- a guest menu so people without an account can read it
- an entry can only be edited by the original author ('restrict edit = 1')
- the author and email attributes are taken from the password file and
  cannot be changed by the author, thus to make sure who wrote a specific
  entry
- the email notification is sent to all people who registered for it, but
  their email address is not contained in the "To:" field 
  (Omit Email to = 1) so that they don't see each other's email address
  (for security reasons). For the 'from' field in the email, my address
  is used to that people can hit 'reply' on automatic notifications and
  they will reach me.
- The option "Format <attribute>" is used for a compact page display

Attachment 1: elogd.txt

[Forum]

; general options
Password file = forum.pwd
CSS = forum.css
Login expiration = 1000
Allow delete = stefan
Self register = 2
Comment = Discussion forum about ELOG
Display mode = threaded
Guest menu commands = Back, Find, Login, Help
Guest find menu commands = Find, Login, Help
Number Attachments = 1
Message comment = <img src=icons/icon6.gif> Please enter only serious messages here, for testing use the <b>Linux</b> Logbook:
Filtered browsing = 0
Entries per page = 8
Reverse sort = 1
Restrict edit = 1

; Attributes
Attributes = Icon, Author, Author Email, Category, OS, ELOG Version, Subject
Options Category = Info, Bug report, Bug fix, Question, Request, Comment, Other
IOptions Icon = icon1.gif, icon2.gif, icon3.gif, icon4.gif, icon5.gif, icon6.gif, icon7.gif, icon8.gif, icon12.gif, icon13.gif, icon14.gif
MOptions OS = Linux, Windows, Mac OSX, All, Other
Icon comment icon1.gif = Entry
Icon comment icon2.gif = Reply
Icon comment icon3.gif = Idea
Icon comment icon4.gif = Warning
Icon comment icon5.gif = Question
Icon comment icon6.gif = Cool
Icon comment icon7.gif = Smile
Icon comment icon8.gif = Angy
Icon comment icon12.gif = Blink
Icon comment icon13.gif = Disagree
Icon comment icon14.gif = Agree
Required Attributes = Author, Author Email, Subject, Icon
Subst on reply subject = Re: $subject
Thread display = $subject, posted by $author on $Entry time
Thread icon = Icon
Remove on reply = Author, Author Email
Date format = %B %d, %Y
Preset Author = $long_name
Preset Author Email = $user_email
Locked Attributes = Author
Quick filter = Date, Category

; Combine attributes into singles lines
Format Author = 1
Format Author email = 1
Format Category = 1
Format OS = 1
Format ELOG Version = 1
Format Subject = 0, subjname, subjvalue

; Email notification
Email message body = 1
Display Email recipients = 0
Omit Email to = 1
Use Email from = stefan.ritt@psi.ch
Use Email subject = ELOG Forum: "$Subject" posted by $Author

Wed May 19 00:03:48 2004

Stefan Ritt

stefan.ritt@psi.ch

Public Logbook

Example for accelerator logbook

This is a typical shift logbook, in this case for an accelerator. It
contains following features:

- public read access
- write access only for registered users
- typical attributes for shift logbook
- author and author email get automatically filled in
- no email notification

Attachment 1: elogd.cfg

[global]

; port under which server is listening
Port = 8080


[Accelerator]
Comment = Accelerator Logbook

; use user level password access
Password file = passwd
Login expiration = 1000
Admin user = ritt
Self register = 1

; look and feel
Guest menu commands = Back, Find, Login, Help
Guest find menu commands = Find, Login, Help
Date format = %B %d, %Y

; attributes
Attributes = Author, Author Email, Category, Subject
Options Category = Routine entry, Shift summary, Problem, Fix, Question, Info, Other
Extendable attributes = Category
Required Attributes = Category, Subject
Thread display = $Subject, entered by $author on $Entry date
Quick filter = Date, Category

; title as shown in the browser
Page Title = Accelerator Logbook - $subject

; preset author and email
Preset Author = $long_name
Preset Author Email = $user_email

; these attributes cannot be changed
Locked Attributes = Author, Author Email

; only author can change its own entry
Restrict edit = 1

; options for reply
Subst on reply subject = Re: $Configuration Name
Remove on reply = Author, Author Email

; No Email notification
Suppress Email to users = 1

Goto page Previous 1, 2 All

ELOG V3.1.5-fe60aaf