| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68319
|
Wed May 18 16:19:07 2016 |
 | Devin Bougie | devin.bougie@cornell.edu | Request | Linux | 3.1.1 | support "authentication = webserver, kerberos" |
The elog client binary does not work with webserver authentication. One fix would be to support both webserver and kerberos authentication (authentication = webserver, kerberos), similar to how you currently support
"authentication = kerberos, file".
A more general discussion of the elog client binary with webserver authentication can be found at https://midas.psi.ch/elogs/Forum/68318 .
Many thanks,
Devin |
|
1701
|
Tue Feb 21 19:25:28 2006 |
 | Steve Jones | steve.jones@freescale.com | Question | All | 2.6.1 | svn revision number in the source |
There is a variable $Id$ in source that looks like it is supposed to reflect the svn revision number of the compiled code. How is this supposed to be set, manually just before compiling?
Thanks! |
|
66401
|
Wed Jun 17 09:05:27 2009 |
 | lance | lance1.hayward@yahoo.com | Question | Windows | 2.7.2 | synchronization |
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 |
|
350
|
Wed May 21 10:15:17 2003 |
| Etienne Van Caillie | etienne.vancaillie@mba.be | Other | | | syntax highligting for elog.cfg with ULTRAEDIT |
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 |
|
68995
|
Wed Aug 7 02:57:55 2019 |
| Lech | subs@lwp.email | Question | Linux | 3.1.3 | tags |
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. |
|
67837
|
Wed Mar 25 10:36:15 2015 |
 | Tim Schel | tim.schelfhout@fixbrussel.be | Info | Linux | Windows | 3.00 | test |
zezerze |
|
2322
|
Sat Oct 6 15:39:12 2007 |
 | Arno Teunisse | A.Teeling3@chello.nl | Question | Windows | 2.6.5-1890 | testing for the limit of the elog database |
Hello
To test elog i created a very large databasefile ( 071006a.log = 39MB ) via an import.
Nothing special. At the import I already got a message to increase "Max content length" to 22420822 in the global section. Below is the what i've done. There are no attachments involved, as you can see.
[global]
port = 80;
Max content length = 22420822
[DAP]
Theme = default
Attributes=Klant,Doc
Quick filter = Klant
So there are only 2 user defined fields in the database.
Everything works ......... but terrible slow : is there a rule of thumb for the size of the database ? |
|
69180
|
Thu Jul 30 17:03:12 2020 |
| Jose Caballero | jcaballero.hep@gmail.com | Question | Linux | 3.1.4 | testing the client: unclear it worked |
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 |