Configure default time range in 'Find', posted by Eoin Butler on Fri Jan 16 13:41:18 2015
|
Hello,
We have a very large elog database, and executing a 'Find' on the whole range takes several minutes, locking other users out of the elog for that time. It would be very nice if there could be an option to set the default value of the 'search last ...' option on the find page. Thanks in advance! |
|
Is it possible to only send an email based on the value of multiple attributes?, posted by Darren Hollinrake on Mon Mar 9 17:03:38 2015
|
My current setup notifies users if downtime = yes. Email Downtime Yes = user1@xyz.com, user2@xyz.com
Is it possible to only send an email based on the value of multiple attributes?
For my use:
user1 only needs notifications if Platform = Workstation and Downtime = Yes
user2 only needs notifications if Platform = Network and Downtime = Yes |
|
test, posted by Tim Schel on Wed Mar 25 10:36:15 2015
|
zezerze |
Documentation of the webserver authentication, posted by Christof Hanke on Wed May 6 12:31:04 2015 
|
Hi Stefan,
here is a draft of how you could describe the webserver authentication in your docs.
T/Christof |
|
elogd complains about unknown cookies, posted by Konstantin Olchanski on Wed May 20 01:45:09 2015
|
elogd is spewing these messages about unknown cookies:
Received unknown cookie "is_returning"
Received unknown cookie "__utma"
Received unknown cookie "__utmz"
Received unknown cookie "SSESSee3cc9c70bedf9a840203765bf409d7b"
Received unknown cookie "SESSee3cc9c70bedf9a840203765bf409d7b"
Received unknown cookie "MidasWikiUserID"
Received unknown cookie "MidasWikiUserName"
Received unknown cookie "MidasWiki_session"
K.O. |
|
elconv deletes everything, posted by Konstantin Olchanski on Wed May 20 01:49:37 2015
|
Converting from elog 2.9.something to new elog 3.1.0 elogd refuses to start, instructs running elconv in one logbook.
When I do so, elconv converts a existing mhttpd-style elog entries to the new format (the corresponding new-format entries already exist)
and deletes everything else - this is very bad.
So there are 2 bugs:
- elogd should not tell us to run elconv when both old-style and corresponding new-style elog entries exist
- elconv should not delete all existing new-style elog entries.
I confirm that elconv *does* delete all new-style elog entries - with strace, I see it issue "unlink" on every elog entry.
What a disaster!
K.O. |
|
this elog errors sending email, posted by Konstantin Olchanski on Wed May 20 01:52:23 2015
|
this elog gives errors sending mail through PSI email server. (did not capture the error messages, sorry). K.O. |
|
edit somebody else's draft, posted by Konstantin Olchanski on Wed May 20 01:54:55 2015
|
this elog offers me to edit a draft message, then yells at me "only some other user can edit this draft!!!".
methinks I should only be offered to edit draft messages that I own or I can edit. K.O. |