ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 552 of 808

Not logged in

Find | Login | Help

New entries since:

Thu Jan 1 01:00:00 1970

Full | Summary | Threaded | Hide attachments

6457 Entries

Goto page Previous 1, 2, 3 ... 551, 552, 553 ... 806, 807, 808 Next

Wed Nov 29 22:44:15 2006

Stefan Ritt wrote:

Grant Jeffcote wrote:

Stefan Ritt wrote:

Grant Jeffcote wrote:

What will the configuration line be?

If you have

MOptions item = value_1, value_2

you can do a

Tooltip value_1 = text

Thanks Stefan,

When implemented there seems to be a finite number of characters that are visible under a tool tip, is this an OS defined limit or something that can be changed?

ELOG itself has a limit of 256 characters, but that can be changed easily. I found that Mozilla Firefox only showed 70 characters and then three dots ("..."), while Internet Explorer showed all 256 characters, wrapping words if necessary. So it strongly depends on the browser.

Thanks, we use Internet Explorer in service but I tested using Mozilla (hence above).
I'd really like to be able change the limit to more than 256 characters, is this simply a configuration parameter or a code change?

2101

Wed Nov 29 13:42:14 2006

Grant Jeffcote wrote:

Stefan Ritt wrote:

Grant Jeffcote wrote:

What will the configuration line be?

If you have

MOptions item = value_1, value_2

you can do a

Tooltip value_1 = text

Thanks Stefan,

When implemented there seems to be a finite number of characters that are visible under a tool tip, is this an OS defined limit or something that can be changed?

2100

Tue Nov 28 22:12:13 2006

Stefan Ritt wrote:

Grant Jeffcote wrote:

What will the configuration line be?

If you have

MOptions item = value_1, value_2

you can do a

Tooltip value_1 = text

Thanks Stefan,

When implemented there seems to be a finite number of characters that are visible under a tool tip, is this an OS defined limit or something that can be changed?

2099

Tue Nov 28 12:50:19 2006

Re: Resubmit-as-new-entry behaviour when synchronizing/mirroring

Andreas Warburton wrote:

Thanks for any comments or insights.

This problem was introduced a couple of months ago. It is now fixed in the new version 2.6.3.

2098

Tue Nov 28 12:48:47 2006

Version 2.6.3 released today

Dear ELOG users,

ELOG version 2.6.3 has been released today. It contains all the bug fixes, security fixes and a few new features collected since the last release which was actually almost half a year ago. The changelog contains all the details.

Due to the security fixes it is recommended to upgrade from any version prior to 2.6.3. Please note that the location of all password and log files has been moved from the main elog directory to the logbook directory. This means that after upgrading you have to move your password file manually, otherwise you cannot log in any more. This modification was requested because some ELOG installations (especially ones with top groups) can now have a read-only main directory.

Stefan Ritt

2097

Tue Nov 28 10:34:54 2006

Re: elog (2.6.1+r1642 ubuntu/debian) regularly becomes non-responsive (w/o crashing)

Peter Kovac wrote:

First, the problem. Fairly regularly (at least once a week, perhaps more), our elog daemon seems to quietly die. The process is still running but anyone attempting to access the server gets "connection refused." The elog log doesn't show anything and the apache logs just show "proxy: Error reading from remote server returned by [path]". Calling a daemon restart doesn't seem to kill the daemon -- I get a "could not bind to port" error. Using kill and then starting the daemon again fixes the problem for a few days and then we start over.

The particulars:
We are running elog on an Ubuntu (6.06 Dapper Drake LTS) web server.
It's currently version 2.6.1+r1642 pulled via apt-get from the Debian repositories.
elog is hiding behind an apache2+SSL proxy.

Any thoughts? Has anyone else seen this behavior? My next step is probably to compile 2.6.2 and remove the packaged flavor but I wanted to see if this was a known bug...

There are three reasons why an elog server can go into an infinite loop:

A bug which has been fixed in meantime. If you can give a try to 2.6.2-1750 or so that could help. I'm not sure if this version is already in the Debian distribution since I'm not the maintainer there.
A corrupted log file. If one of the YYMMDDa.log file get some garbage (maybe due to hard disk problems etc.) the elogd server can run into an infinite loop. In that case examine all log files to see if there is anything wrong. If so, edit it manually and restart elogd.
Some not yet found bug. One never can exclude this of course, but at this forum I have elogd running under similar conditions like you, and it runs for months without problems.

2096

Tue Nov 28 10:26:33 2006

Grant Jeffcote wrote:

What will the configuration line be?

If you have

MOptions item = value_1, value_2

you can do a

Tooltip value_1 = text

2095

Tue Nov 28 10:25:08 2006

Stefan Ritt wrote:

Grant Jeffcote wrote:

Hi Stefan,

Is there a way to add a 'Tool Tips' to individual 'Options' similar to that currently available for Attributes? I have several checkboxes under an attribute for predefined email groups and would like to see if I can make the recipient list viewable via a mouse hover using the 'Tool tip' feature.
If not possible can it be added to the wishlist?

Ok, I implemented this. It is in revision 1760 and will be contained in the next release.

That's really great, thank you so much.
What will the configuration line be?

Goto page Previous 1, 2, 3 ... 551, 552, 553 ... 806, 807, 808 Next

ELOG V3.1.5-3fb85fa6