We are running elog across two sites and synchronizing every four hours on change only. There are about 100 entries per day of which most are just one line entries. However this is taking up to 9 mins and during the replication process the server gives us an "unavailable" error. We are using a T1 across the sites so bandwidth should not be an issue, I am confused as to why this takes so long.

The issue for us is not how long the sync takes, providing this was happening in the background, and doesnt lock out the server while the replication was taking place. We are operating under a 24 hour call center type environment so the server being available all the time is of paramount importance.

We use version 2.7.2 and I know there have been several changes made since this version. Would changing to the latest version have any impact on this?

Cheers,

Lance

UltraEdit Syntax coloring
=========================
add this file in ultraedit
UltraEdit --> ADVANCED --> CONFIGURATION --> SYNTAX HIGHLIGHTING
I hope this will help you...

it gives different color according to elog commands
some attributes are use internaly like

ShellOnSubmit
ShellParam

if somebody has other suggestion to improve the display ask me

Hello,

Is it possible to create tags for new entries in elog? I understand it would have to be some kind of mix between Extendable options and moptions. Currently, whatever is entered in extendable options forms one option, while usually for tags, words separated by # form different tags. As usual with tags, I would like to add multiple tags to my new entry and then be able to filter all entries by specific tag or group of tags.

zezerze

Hello,

I just gave it a quick try to the command line client, to see if I can use it to access our institution service. 

[root@host ~]# cd /tmp/
[root@host ~]# mkdir elog
[root@host ~]# cd elog
[root@host ~]# wget https://elog.psi.ch/elog/download/RPMS/elog-3.1.4-2.el7.x86_64.rpm
[root@host ~]# rpm2cpio elog-3.1.4-2.el7.x86_64.rpm | cpio -idmv
[root@host ~]# cd usr/local/bin/
[root@host ~]# ./elog --help
[root@host ~]# ./elog -h <hostname> -l <logbook> -u <myusername> <mypassword> -w last
"Message successfully transmitted, ID=-1"

Is that the expected output? I was expecting to see info about the latest message in the server.

Cheers,

Jose

Hi,

I wonder if it is possible to set a minimum default value for the height of the text box when submitting new entries. If I understood well, by default the text box height automatically resizes in order that all the elements of the page are visible. Actually for our needs having a minimum height of the text box fixed (for instance 500px)  is by far more useful of viewing the attachment box (we know it is down scrolling the page :) ). We know it is possible to resize the text box using the mouse but doing this every time one creates a new entry can be annoying. Setting a default minimum size would be more confortable. Is it possible to do this?

Thank you 

Beppe

I think the text display of ASCII files, which is new in version
2.5.4, is not a good idea.  E.g. I had a large ps file attached
to one entry and it took a long time display this entry (over DSL).
Then I saw that the ps-file is displayed as text, which is not really 
useful.  

Probably it is fine to display only files ending in '.txt' per default.
In addition a file that has more than say 1000 lines should probably 
also not be displayed (as default, optional OK).  

Cheers, Heiko