More than 100 attributes , posted by JD on Wed Jun 29 16:07:32 2016
|
I am modifying the elogd.cfg automatically with a script. The Script fetches a list of systems from a LDAP database and writes them into an "Options" line in the elog.cfg.
Everything worked fine, until we hit the critical number of 100 attributes. I saw this is also stated in the manual.
Is there any workaround? I downloaded the source code and hat a quit look, but couldn't find the section which is responsible for this behavior.
Is there a reason for this limit?
Thanks
Jonathan |
Re: More than 100 attributes , posted by Stefan Ritt on Wed Jun 29 16:58:15 2016
|
The limit is in the variable
#define MAX_N_ATTR 100
in elogd.c. If you increase it and recompile, it could work, but at some time you will get a stack overflow since arrays with that size are dynamically allocated on the stack, and depending on your compiler settings the stack size is only finite.
Stefan
JD wrote: |
I am modifying the elogd.cfg automatically with a script. The Script fetches a list of systems from a LDAP database and writes them into an "Options" line in the elog.cfg.
Everything worked fine, until we hit the critical number of 100 attributes. I saw this is also stated in the manual.
Is there any workaround? I downloaded the source code and hat a quit look, but couldn't find the section which is responsible for this behavior.
Is there a reason for this limit?
Thanks
Jonathan
|
|
Re: More than 100 attributes , posted by JD on Thu Jun 30 14:00:43 2016
|
Thank you Stefan, I think then I will leave it at the default value. I need a stable Systen
Stefan Ritt wrote: |
The limit is in the variable
#define MAX_N_ATTR 100
in elogd.c. If you increase it and recompile, it could work, but at some time you will get a stack overflow since arrays with that size are dynamically allocated on the stack, and depending on your compiler settings the stack size is only finite.
Stefan
JD wrote: |
I am modifying the elogd.cfg automatically with a script. The Script fetches a list of systems from a LDAP database and writes them into an "Options" line in the elog.cfg.
Everything worked fine, until we hit the critical number of 100 attributes. I saw this is also stated in the manual.
Is there any workaround? I downloaded the source code and hat a quit look, but couldn't find the section which is responsible for this behavior.
Is there a reason for this limit?
Thanks
Jonathan
|
|
|
Unable to set a custom logbook dir on Debian 8 from the repository package, posted by S. Caiazza on Tue May 31 20:03:53 2016
|
Dear all
I installed elog from the current stable repository on Debian 8 (jessie)
The installation went on smoothly, I modified the configuration files of the Apache server as described in the manual to use the elog in parallel with an existing webserver and then I tested. The demo logbook loads fine and I see that elog created a folder for the logbook in /var/lib/elog/logbooks, which is the directory specified by default in the /etc/init.d/elog file.
Then I modified the /etc/elog.conf file, added the following lines in the global section (custompath is a local path)
Resource dir = /<custompath>/elog/res
Logbook dir = /<custompath>/elog/logbooks
And I created a new logbook.
After restarting the elog service the second database is correctly created but both of them are still stored in /var/lib/elog/logbooks so it seems the global configurations in the config file are overwritten.
How can I specify the custom folder so that the new logbooks are written there? |
Re: Unable to set a custom logbook dir on Debian 8 from the repository package, posted by Stefan Ritt on Mon Jun 27 16:06:55 2016
|
The debian version of elog is pretty old with quite a number of bugs fixed in meantime. Unfortunatlely the debig packase has not bee updated by the maintainers. So better download the current version from bitbucket and compile elogd yourself.
S. Caiazza wrote: |
Dear all
I installed elog from the current stable repository on Debian 8 (jessie)
The installation went on smoothly, I modified the configuration files of the Apache server as described in the manual to use the elog in parallel with an existing webserver and then I tested. The demo logbook loads fine and I see that elog created a folder for the logbook in /var/lib/elog/logbooks, which is the directory specified by default in the /etc/init.d/elog file.
Then I modified the /etc/elog.conf file, added the following lines in the global section (custompath is a local path)
Resource dir = /<custompath>/elog/res
Logbook dir = /<custompath>/elog/logbooks
And I created a new logbook.
After restarting the elog service the second database is correctly created but both of them are still stored in /var/lib/elog/logbooks so it seems the global configurations in the config file are overwritten.
How can I specify the custom folder so that the new logbooks are written there?
|
|
Hide blank fields when displaying logbook entry, posted by Rudy Taraschi on Thu Jun 23 15:57:34 2016
|
Hi, I have a logbook with attributes Tool1, Tool2, and Tool3. When viewing a completed entry, what I want to do is see Tool2 or Tool3 only if they are non-zero, and don't want to see them if blank. Basically, a "Hide if blank" option. I couldn't find it - if it doesn't exist, are there any tricks to simulate it? |
pdf thumbnails in latest Imagemagick, posted by John Haggerty on Mon Jun 6 05:51:44 2016
|
I think with the latest Imagemagick from brew (6.9.4-7) that pdf thumnails no longer get made; the attachment is there but the message "Cannot create thumbnail, please check ImageMagick installation" apears instead of the thumbnails. I couldn't make out from elogd -v 3 why they failed, but I couldn't make out the exact convert command that was failing. This is on MacOS 10.11.5 and I think the updated version ofImagemagick was the last thing that changed before it failed. |
Re: pdf thumbnails in latest Imagemagick, posted by Stefan Ritt on Tue Jun 21 16:33:56 2016
|
Hi John,
I use ImageMagick 6.9.3-10 on my Mac OSX 10.11.5 and it works fine. So apparently the parameters of the ImageMagick program have been changed. If you set the logging level to 2 or higher, you should see the "convert" and "identify" commands in the logging file. If you try these commands manually from the command line, you will see if they succeed or give an error. Please post this error here so I can have a look.
Cheers,
Stefan
John Haggerty wrote: |
I think with the latest Imagemagick from brew (6.9.4-7) that pdf thumnails no longer get made; the attachment is there but the message "Cannot create thumbnail, please check ImageMagick installation" apears instead of the thumbnails. I couldn't make out from elogd -v 3 why they failed, but I couldn't make out the exact convert command that was failing. This is on MacOS 10.11.5 and I think the updated version ofImagemagick was the last thing that changed before it failed.
|
|
Re: pdf thumbnails in latest Imagemagick, posted by John Haggerty on Tue Jun 21 16:44:05 2016
|
Stefan Ritt wrote: |
Hi John,
I use ImageMagick 6.9.3-10 on my Mac OSX 10.11.5 and it works fine. So apparently the parameters of the ImageMagick program have been changed. If you set the logging level to 2 or higher, you should see the "convert" and "identify" commands in the logging file. If you try these commands manually from the command line, you will see if they succeed or give an error. Please post this error here so I can have a look.
Cheers,
Stefan
John Haggerty wrote: |
I think with the latest Imagemagick from brew (6.9.4-7) that pdf thumnails no longer get made; the attachment is there but the message "Cannot create thumbnail, please check ImageMagick installation" apears instead of the thumbnails. I couldn't make out from elogd -v 3 why they failed, but I couldn't make out the exact convert command that was failing. This is on MacOS 10.11.5 and I think the updated version ofImagemagick was the last thing that changed before it failed.
|
|
Since I posted that, there have been multiple versions of Imagemagick released through brew for the Mac in the last few weeks, and I'm now using 6.9.4-9, which seems to work fine with thumbnails again, indeed, I noticed that as soon as 6.9.4-8 was released, I was back to normal, but thanks for the debugging pointer. |
cannot use "use email heading", posted by utomoadji wisnubroto on Tue Jun 14 07:51:37 2016
|
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: 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: cannot use "use email heading", posted by utomoadji wisnubroto on Wed Jun 15 02:42:53 2016
|
Hi Stefan,
Thanks for your reply, i got it now.
Thank you
Stefan Ritt wrote: |
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
|
|
|
Guest menu commands not working as advertisted, posted by Greg Christian on Tue Jun 14 16:50:41 2016
|
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 |
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
|
|
Re: Guest menu commands not working as advertisted, posted by Greg Christian on Tue Jun 14 18:32:03 2016
|
Got it. Thanks!
Stefan Ritt wrote: |
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
|
|
|
Self register = 0 not working , , posted by rudy on Wed Jun 8 15:00:47 2016
|
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 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
|
|
|
|
|
pdf thumbnails in latest Imagemagick, posted by John Haggerty on Mon Jun 6 05:45:57 2016
|
I think with the latest Imagemagick from brew (6.9.4-7) that pdf thumnails no longer get made; the attachment is there but the message "Cannot create thumbnail, please check ImageMagick installation" apears instead of the thumbnails. I couldn't make out from elogd -v 3 why they failed, but I couldn't make out the exact convert command that was failing. This is on MacOS 10.11.5 and I think the updated version ofImagemagick was the last thing that changed before it failed. |
|