Re: elog 2.8.0 as daemon crashes when editing selected threaded list, posted by Mark Bergman on Thu Apr 21 21:06:20 2011
|
Mark Bergman wrote:
I recently upgraded elog from 2.7.8 to 2.8.0 (and moved servers, removed unused logbooks, etc.). I'm now having a problem |
error message "Command Config is not allowed" after registering, posted by Mark Bergman on Fri Oct 21 01:09:54 2011
|
After registering, elog displays a page with the message:
Error: Command "Config" is not allowed for user ""
However, the registration is successful. This causes confusion, and results in users registering multiple times. |
Re: error message "Command Config is not allowed" after registering, posted by Mark Bergman on Wed Feb 15 17:13:08 2012
|
Mark Bergman wrote:
After registering, elog displays a page with the message: |
|
elog entry in email footer?, posted by Mark Bergman on Wed Feb 15 17:17:27 2012
|
On our system, elog sends email to all people associated with an entry. Often, people will respond via email, not through elog. I'm in the process of
setting up a handler for the inbound email. However, I'd like to have the outbound mail from eLog include a 'footer' to each message the details where
to go to respond. |
|
obfuscate password in verbose logging, posted by Mark Bergman on Thu Apr 26 23:57:04 2012
|
I'm trying to debug an issue with elogd (2.9.1) and was reminded that using the "-v" option exposes
user passwords. This wasn't a huge problem for us in the past, but we're now using kerberos authentication,
meaning that the exposed username/password applies to lots of sensitive systems within our university.
|
|
Re: obfuscate password in verbose logging, posted by Mark Bergman on Fri Apr 27 00:29:56 2012
|
> I'd suggest that the "-v" option hide passwords. If they need to be revealed for debugging
|
|
any way to undelete entries?, posted by Mark Bergman on Thu Feb 21 23:23:19 2013
|
| Is there any way within eLog to undelete entries? |
|
elogd crashes with malloc() memory corruption, posted by Mark Bergman on Fri Mar 1 16:35:21 2013
|
I'm having an issue with ELog 2.9.2 revision 2455 where it crashes consistently with:
*** glibc detected *** /usr/local/sbin/elogd: malloc(): memory corruption: 0x0000000014977210 ***
(the address varies). The crash seems to be triggered by the attempt to email a log entry. The log entry itself is saved. If I open the existing |