Re: Merge duplicate types, posted by Andreas Luedeke on Fri May 6 22:30:56 2016
|
I'm not sure I understand your question correctly.
If you want to remove options from an extendable option attribute, then you can just edit the logbook configuration file.
| John Mund wrote: |
|
Hello,
We have accumulated some duplicate 'types' in one of our logbooks. Is it possible to merge them?
Thanks,
John
|
|
|
Re: elog service crashes frequently, posted by Andreas Luedeke on Sun May 22 11:56:21 2016
|
We do run ELOG on a Linux server and see about weekly crashes, too. It seems to be connected to the authentication process (Kerberos, File), but we could not nail it down yet.
But we have set up a supervision process that checks every minute if the "elogd" process is still running. If not, it simply restarts it.
If ELOG is down for two minutes a week, this is fine for our users.
| Stan Turner wrote: |
|
We have always had issues with eLOG crashing intermittently... I upgraded from Server 2003 to Server 2008 about a year ago to try to reduce the issues... which really didn't help.
The service now seems to crash every week... (getting worse)... Is anyone seeing these issues in Windows servers? Any suggestions??
|
|
|
Re: Self register = 0 not working , , posted by Andreas Luedeke on Wed Jun 8 16:01:11 2016
|
It would be new to me if elog would support independent [global] sections for each logbook.
I thought you can only have one [global] section. Whatever is defined in that section will be valid for all logbooks.
If you need to have different user files, you'll need to run different elogd services with independent config files (and Password files).
Andreas
| rudy wrote: |
|
I have Split Elog to Two Top Group [Check the Config Below].
Problem =
After Staff01 login successfully to http://127.0.0.1/Staff and if he/she fill the url http://127.0.0.1/Administrator and choose any elog topic, it will direct registration form.
[global]
port = 8080
Self register = 0
Show top groups = 1
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 1
Top group Staff = Website, Notes
Top group Administrator = Website Update, Admin Notes, Ticketing
[global Staff]
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config
Password file = staff.pwd
Admin user = sylpid
Login user = staff01
[global Administrator]
Password file = admin.pwd
Admin user = sylpid
Login user = admin01
|
|
|
Re: Self register = 0 not working , , posted by rudy on Wed Jun 8 17:08:56 2016
|
Hi Andreas
I'm following the instruction from https://midas.psi.ch/elog/config.html#groups , please scroll to the Top Groups
Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = 98, ME, NT, XP, CE
Group CE = 1.0, 2.UL
Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
[global engineering]
Password file = engineers.pwd
Admin user = stefan
[global administration]
Password file = admin.pwd
Admin user = bill
| Andreas Luedeke wrote: |
|
It would be new to me if elog would support independent [global] sections for each logbook.
I thought you can only have one [global] section. Whatever is defined in that section will be valid for all logbooks.
If you need to have different user files, you'll need to run different elogd services with independent config files (and Password files).
Andreas
| rudy wrote: |
|
I have Split Elog to Two Top Group [Check the Config Below].
Problem =
After Staff01 login successfully to http://127.0.0.1/Staff and if he/she fill the url http://127.0.0.1/Administrator and choose any elog topic, it will direct registration form.
[global]
port = 8080
Self register = 0
Show top groups = 1
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 1
Top group Staff = Website, Notes
Top group Administrator = Website Update, Admin Notes, Ticketing
[global Staff]
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config
Password file = staff.pwd
Admin user = sylpid
Login user = staff01
[global Administrator]
Password file = admin.pwd
Admin user = sylpid
Login user = admin01
|
|
|
|
Re: Self register = 0 not working , , posted by Andreas Luedeke on Wed Jun 8 18:49:28 2016
|
Aparently I've missed that one :-)
In order to test your problem it would be useful to have a minimal config file to reproduce the problem. Yours does not include any actual logbook, only [global *] sections.
Andreas
| rudy wrote: |
|
Hi Andreas
I'm following the instruction from https://midas.psi.ch/elog/config.html#groups , please scroll to the Top Groups
Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = 98, ME, NT, XP, CE
Group CE = 1.0, 2.UL
Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
[global engineering]
Password file = engineers.pwd
Admin user = stefan
[global administration]
Password file = admin.pwd
Admin user = bill
| Andreas Luedeke wrote: |
|
It would be new to me if elog would support independent [global] sections for each logbook.
I thought you can only have one [global] section. Whatever is defined in that section will be valid for all logbooks.
If you need to have different user files, you'll need to run different elogd services with independent config files (and Password files).
Andreas
| rudy wrote: |
|
I have Split Elog to Two Top Group [Check the Config Below].
Problem =
After Staff01 login successfully to http://127.0.0.1/Staff and if he/she fill the url http://127.0.0.1/Administrator and choose any elog topic, it will direct registration form.
[global]
port = 8080
Self register = 0
Show top groups = 1
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 1
Top group Staff = Website, Notes
Top group Administrator = Website Update, Admin Notes, Ticketing
[global Staff]
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config
Password file = staff.pwd
Admin user = sylpid
Login user = staff01
[global Administrator]
Password file = admin.pwd
Admin user = sylpid
Login user = admin01
|
|
|
|
|
Re: Self register = 0 not working , , posted by rudy on Thu Jun 9 04:29:14 2016
|
Hi Andreas,
Thanks for your help. I will try to do that and if I found how to fix this problems, I will post it at here again.
| Andreas Luedeke wrote: |
|
Aparently I've missed that one :-)
In order to test your problem it would be useful to have a minimal config file to reproduce the problem. Yours does not include any actual logbook, only [global *] sections.
Andreas
| rudy wrote: |
|
Hi Andreas
I'm following the instruction from https://midas.psi.ch/elog/config.html#groups , please scroll to the Top Groups
Group Linux PCs = Red Hat, Debian, Mandrake
Group Windows PCs = 98, ME, NT, XP, CE
Group CE = 1.0, 2.UL
Top group engineering = Linux PCs, Windows PCs
Top group administration = Employees, Purchases
[global engineering]
Password file = engineers.pwd
Admin user = stefan
[global administration]
Password file = admin.pwd
Admin user = bill
| Andreas Luedeke wrote: |
|
It would be new to me if elog would support independent [global] sections for each logbook.
I thought you can only have one [global] section. Whatever is defined in that section will be valid for all logbooks.
If you need to have different user files, you'll need to run different elogd services with independent config files (and Password files).
Andreas
| rudy wrote: |
|
I have Split Elog to Two Top Group [Check the Config Below].
Problem =
After Staff01 login successfully to http://127.0.0.1/Staff and if he/she fill the url http://127.0.0.1/Administrator and choose any elog topic, it will direct registration form.
[global]
port = 8080
Self register = 0
Show top groups = 1
Preset Author = $long_name
Locked Attributes = Author
Restrict edit = 1
Top group Staff = Website, Notes
Top group Administrator = Website Update, Admin Notes, Ticketing
[global Staff]
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config
Password file = staff.pwd
Admin user = sylpid
Login user = staff01
[global Administrator]
Password file = admin.pwd
Admin user = sylpid
Login user = admin01
|
|
|
|
|
|
Re: cannot use "use email heading", posted by Stefan Ritt on Tue Jun 14 14:33:40 2016
|
The setting
Use Email Heading
is only used for plain text encoding of email messages. The default is HTML encoding, which has its own heading which cannot be changed. If you want the different heading, use
Email encoding = 1
and you get it.
/Stefan
| utomoadji wisnubroto wrote: |
|
Hello,
i have config file elogd.cfg like below:
[Tom Yaht]
Theme = default
;Comment and Tittle
Comment = LogBook
Page title = Tom LogBook
List page title = Tom LogBook
;admin and user settings
admin user = tom
login user = tom, soc
login expiration = 2
Restrict edit time = 8
Attributes = Controllers, Event Date/Time, Site, Engineers, Type, Category, Subsystems, Subject, Distribution-Mail, EMail to
Moptions Distribution-Mail = Controllers, Engineers, Consultant Team, Manager
;Email settings
Email Distribution-Mail "Controllers" = ble@xxx.com, cor@xxx.com, nor@xxx.com
Email Distribution-Mail "Engineers" = blo@xxx.com, sur@xxx.com, ars@xxx.com
Email Distribution-Mail "Consultant Team" = bli@xxx.com, zam@xxx.com
Email Distribution-Mail "Manager" = bos@xxx.com
Email all = $EMail to
Use Email Subject = Tom Logbook - $Subject
Use Email Heading = New Tom Logbook entry
Use Email Heading edit = Tom Logbook has been updated
The Subject successfully displayed as i expected , but the email heading still use default heading "A new ELOG entry has been submitted" , while i want to changeit to be "New Tom Logbook entry" as i mention in Use Email Heading above.
Could anybody help me.
Thank you
|
|
|
Re: Guest menu commands not working as advertisted, posted by Stefan Ritt on Tue Jun 14 17:01:04 2016
|
There are two menus, one for the list display, and one for the individual entry display. To change the first, you need
List menu commands = ...
Guest list menu commands = ...
| Greg Christian wrote: |
|
Hello,
I am trying to set up my elog to have read-only guest access and require registration/password for users to be able to post to the elog. I've tried following the instructions here: https://midas.psi.ch/elog/faq.html#6, i.e. putting the following lines under the [global] section of my elogd.cfg file:
Menu commands = List, New, Edit, Reply, Duplicate, Find, Config, Logout, Help
Guest menu commands = List, Find, Login, Help
When I do this, I do get guest acccess, however the menu items are
New | Find | Select | Import | Config | Logout | Last day | Help
rather than the List, Find, Login, Help I would expect. Also, if I click on Logout, it simply does nothing, which means there's now no way to log in as a registered user.
Any thoughts on what might be wrong?
Thanks,
Greg
|
|
|