Re: Elog stability with multiple users, posted by Stefan Ritt on Mon Mar 2 08:06:38 2015
|
Being not able to kill a server running in an endless loop seems strange to me. If you put any program artificially into an endless loop, you can kill it
via "kill -9 <pid>". Have you tried that? The only exception I
can imagine is if there is a problem in the file system, like your elog logbooks are mounted via NFS or some other remote filesystem, and you have a problem |
|
Re: Is it possible to only send an email based on the value of multiple attributes?, posted by Stefan Ritt on Mon Mar 9 17:24:42 2015
|
[quote="Darren Hollinrake"]My current setup notifies users if downtime = yes.
[CODE]Email Downtime Yes = user1@xyz.com, user2@xyz.com[/CODE]
|
|
Re: Is it possible to only send an email based on the value of multiple attributes?, posted by Andreas Luedeke on Thu Mar 12 09:53:57 2015
|
[quote="Darren Hollinrake"]My current setup notifies users if downtime = yes.
[CODE]Email Downtime Yes = user1@xyz.com, user2@xyz.com[/CODE]
|
|
Re: Configure default time range in 'Find', posted by David Pilgram on Sun Mar 15 16:41:49 2015
|
Hi Stefan,
There's one pre-set value you forgot to include in this, which is the genuinely required "Show last all time". I archive
many logbooks by years, and so for the year 2005 (say), searching by anything other than all time will always bring up zero results. And it gets |
|
Re: Configure default time range in 'Find', posted by David Pilgram on Sun Mar 15 17:53:44 2015
|
Law of unintended consequences came into play. If you use 0, then on the results page it says "Restricted search to last 0 Days".
So that also needs tweeking, and that's really put my c coding (or lack of it) to the test. But I've changed that phrase to "Unrestricted
search" followed by blank for when the parameter "last" is 0. |
|
Re: Configure default time range in 'Find', posted by David Pilgram on Mon Mar 16 13:51:11 2015
|
Hi Andreas,
Yes, the empty string does exactly that, in the drop down menu, but before my changes, I could not set it to be the default setting in the configuration
file. In an archived logbook, it's perfectly possible for "all time" to be the only sensible value. I tried "Show last default |
|
Re: Configure default time range in 'Find', posted by Andreas Luedeke on Tue Mar 17 07:04:44 2015
|
Hi David,
I was confused because one normally does not need to include a line in the configuration to set a default value. A default
is exactly what you get if you don't specify anything in the configuration
But I think I've figured it out: you were overriding the default in the global section for all logbooks and |
|
Re: How to change configuration already set properly, posted by Andreas Luedeke on Wed Mar 18 09:34:46 2015
|
ELOG does not provide you with a simple mechanism to rename attributes in existing entries.
If you rename an attribute in the configuration,
then you need to adapt all existing entries by replacing the name in all *a.log files on the server.
Or you could set-up a second logbook
with the renamed attributes, export all entries from the first logbook (use "Find") and import these entries in the second logbook.
|