New docs?, posted by PJ Meyer on Thu Dec 22 01:17:12 2005
|
Just looked at change log for 2.6
was wondering where the documentation for the new additions/changes is/are. |
Re: Compile on Windows?, posted by Stefan Ritt on Thu Dec 22 08:53:43 2005
|
Mike wrote: | What version of Visual Studio do you use for compile Elog on windows.
I have downloaded the Tar from svn and am having some errors, but then I've go VS.Net 2003. I wondering if this was done with 6.0? |
Right now I'm using VS.Net 2003, but you should be able to compile it with 6.0, except that you have to redo the project file, which might not be backwards compatible. An alternative is to use gcc under cygwin, which is a free alternative for windows. |
Re: New docs?, posted by Stefan Ritt on Thu Dec 22 08:58:25 2005
|
PJ Meyer wrote: | Just looked at change log for 2.6
was wondering where the documentation for the new additions/changes is/are. |
I usually keep http://midas.psi.ch/elog/config.html up-to-date, but I agree that it's a bit hard to find the additions there, that's why there is the change log
The ELCode is described on a separate page, which can also be accessed by clicking on the ELCode link below the text box of the logbook entry page. |
Maximum number of LogBooks? Bug?, posted by Mike on Thu Dec 22 14:32:00 2005
|
Is there a Maximum number logbooks?
I have run into a problem but I'm not sure if to call it a Bug or not. We have started using Elog to keep a work log for each of our production servers. After a short trial I put generated a config file using groups for all of our servers which is 294 logbooks. Almost every thing works except the config screen. You get a list of all the logbooks with the checkboxes for the email notifications. If you click save (Doesn't make a difference if you make changes or not) you get the following.
Error: Too many parameters (> 120). Cannot perform operation.
I was able to recompile using cygwin under windows after changing MAX_PARAM from 120 to 400. That fixes the problem, but eventually you get a stack overflow.
Any suggestions? I have considered separate instances running 100 logbooks each but I would like to have a global search.
Thanks for a Great tool. I've been using it as a personal log for sometime and was finally able to convince my team we sould use it. |
Re: Maximum number of LogBooks? Bug?, posted by Stefan Ritt on Thu Dec 22 15:14:39 2005
|
Mike wrote: | Is there a Maximum number logbooks?
I have run into a problem but I'm not sure if to call it a Bug or not. We have started using Elog to keep a work log for each of our production servers. After a short trial I put generated a config file using groups for all of our servers which is 294 logbooks. Almost every thing works except the config screen. You get a list of all the logbooks with the checkboxes for the email notifications. If you click save (Doesn't make a difference if you make changes or not) you get the following.
Error: Too many parameters (> 120). Cannot perform operation.
I was able to recompile using cygwin under windows after changing MAX_PARAM from 120 to 400. That fixes the problem, but eventually you get a stack overflow.
Any suggestions? I have considered separate instances running 100 logbooks each but I would like to have a global search.
Thanks for a Great tool. I've been using it as a personal log for sometime and was finally able to convince my team we sould use it. |
You're really pushing to the limit 
The maximum number of logbooks is indeed 120. If you have too many logbooks, they are also hard to handle (too many check boxes in the config page etc.). What if you make not one logbook per server, but have a single logbook and use the server as an attribute, like
Attributes = ..., Server, ...
Options Server = Server1, Server2, ...
Now you can ask: How many options are possible for an attribute, and the answer is 100, which is even less than the number of logbooks. But you can make three logbooks, each covering 100 servers, and that covers your 294 servers. |
Re: Maximum number of LogBooks? Bug?, posted by Mike on Thu Dec 22 15:39:23 2005
|
Stefan Ritt wrote: |
You're really pushing to the limit 
The maximum number of logbooks is indeed 120. If you have too many logbooks, they are also hard to handle (too many check boxes in the config page etc.). What if you make not one logbook per server, but have a single logbook and use the server as an attribute, like
Attributes = ..., Server, ...
Options Server = Server1, Server2, ...
Now you can ask: How many options are possible for an attribute, and the answer is 100, which is even less than the number of logbooks. But you can make three logbooks, each covering 100 servers, and that covers your 294 servers. |
Thanks for the quick reply and suggestion. I will give that a try.
You might want to consider adding a check that there aren't over 120 logbooks. I manually created the elog.cfg with 294 logbooks. Everything works, except for running into this problem.
Thanks again |
MS Fonts only in ELCode options?, posted by T. Ribbrock on Wed Jan 4 12:05:21 2006
|
I'm just after installing 2.6.0 and marvelling at all the changes, especially ELCode (I was using 2.5.8 previously). However, I noticed that the "FONT" menu for ELCodes only offers Microsoft fonts - something I usually avoid like hell when publishing web content, as I cannot rely on those being installed on the clients. As far as I can see there is no easy way to change this, short of patching the source - or is there?
I'd want to add at least options like "serif" and "sans-serif" and maybe some standard (Unix\?) fonts like "Helvetica". |
HelpELCode needs to be present in "Menu commands"?, posted by T. Ribbrock on Wed Jan 4 12:26:31 2006
|
Another little issue I came across was this: I'm using "Menu commands" and "Guest Menu commands" in my configuration. When I logged in and started to create a new entry, clicking on the URL that is behind "ELCode" at the bottom of the screen (and accesses the help for the ELCodes) resulted in a "command denied". The only way to get around this was to add "HelpELCode" to "Menu commands" - but now it also shows up in the menus, which is not what I want. Is there any way around this? |