Is there a limit on the number of conditions that can be simultaneously active in a log?  When I activate more than 10 conditions I start to see side effects with other conditions being deactivated.  I think this is due to the hard-coded array size of 10 for clist in the match_param function in elogd.c.  If so, could this limit be increased?  

Are there other limits on the number of conditions, or the length of condition names?  If I've understood the code right, the _condition string holds a comma-separated list of the active conditions, so the 256 byte length of this will also put some limit on the number of conditions that can be active.

Ups. I never imagined that someone would use more than 10 conditions. I'm not 100% sure if the problem is the clist array, but can you try to set it to 20 and see if it gets better? You can also send me your config file and I can try it myself. 

I'll try increasing the list size(s), and will also prepare a simplified config file for you to look at.  Maybe there is a another way to implement what I am trying to achieve?  

In general terms I am trying to give an e-log a "memory" of what has been recorded previously in order to constrain what is permissible to record next.  I do this by starting a log with an initial entry, then alter the config so that users can add records only by duplicating the last record.  The log records the current state of some variables, and allows users to record changes to the state of any of these variables. Conditions are used to constrain the permitted state changes, depending on the current state; conditions are also used, with subst options, to update the current state variables when changes are made.

Specifically, we have "Mate-Demate" logs for connectors to record when connectors are mated and demated.  Previously we just had an attribute for each connector in an assembly with options "Mate", "Demate" and "-" to indicate that either a mate or demate was carried out or that the connector was not touched on this occasion (although others were).  My cunning plan was to ensure that a "Demate" (or no-op) was possible only if the connector is currently mated, and conversely that a "Mate" (or no-op) was possible only if the connector is currently demated.  For each connector (e.g. ConnectorA), there are now two attributes

• "ConnectorA state", to record the current state, and
• "ConnectorA" to record any change.

A new record can be created only by duplicating the last record, thus copying the current state of the connectors, and for each connector the relevant config file entries are like this:

Show Attributes = ConnectorA
Show Attributes Edit = ConnectorA state, ConnectorA
Locked Attributes = ConnectorA state
Preset on duplicate ConnectorA = -
Options ConnectorA state = Mate{1}, Demate{2}
{2} Options ConnectorA = -, Mate{3}
{1} Options ConnectorA = -, Demate{3}
{3} Subst ConnectorA state = $ConnectorA

Hello,

we used Admin and write passwords. Now this is no longer supported in ELOG 2.9.0 and I tried to change to File or Kerberos Autentication. But nothing worked. I tried the following lines in elog.cfg

[Serverlogbuch]
Authentication = File
Password file = C:\Program Files\ELOG\logbooks\Serverlogbuch\pwd.txt
Self Authentication = 1

So the self Autentication site opens and I can put in all informations. But if I click on save he tries to save the information in the password file and after a time he stops and Internet Explorer says that the page cannot be reached.

The file is not saved. If I remove the 3 lines the logbook opens without any problems.

I tried also kerberos but it didn't work. But there I think some entries in the krb5.ini are wrong.

Would you please help solving the File password problem?

Best Regards

Michael

Just two hints:

• The file mentioned as "Password file" should be writeable for the "elogd" process. It is needed for both, Kerberos and File authentication. Better not specify the full path, it should assume the file in the logbook directory.
• The command "Self Authentication = 1" does not exist. Maybe you mean "Self register = 1"?

Thank you for the answer, but it didn't solve the problem.

• I used Self Register instead of Self Authentication. I deleted the complete path and only used the Filename.

• The Account which is used to start the Elogd process is local system. System has full right at the logbook directory

 Should I use an Admin Account for the elogd process? The error message is always the same (page not reachable) The File is also not created in the logbook dir.

I once had problems with the local system account, so I used my own account to start the service and that worked. For trial, you can also start the elogd.exe program manually (not as a service) in a DOS box and see if it can create the password file. 

 That worked for me. Used an Account instead of local system and everything is OK. Thanks for your help.

Hi,

I have logbook A and logbook B.  Is it possible to move one type of entries in logbook A to logbook B?  If yes, may I know how you do it?  Thank you.

Ze

•  You can add the "Move to = B" command in logbook A.
• Then you add "select" in "List Menu commands = ..., select, ...".
• Now you "Find" all entries of the type you want (for convenience choose "Display 9999 entries per page").
• You press "toggle all" and then "Move to B"

Hi All,

I am interested to have ELOG installed in my QNAP x86 based NAS (239 Pro II)
Have someone done this already or is there a write-up of a normal compile-procedure which I can have as a base when I attempt to compile?

Regards,

Per

I solved it.
I don't really know if I really needed to compile it but I complied this on the NAS itself so now it is 100% compatible (I believe)

Per

 I managed to package Elog v2.92 build 2462 into and QNAP installer QPKG package.

This is for x86 based QNAP NAS only.

Note: You must have adduser package installed prior to installation.
Login to the NAS with SSH and type:
apt-get update
apt-get install adduser

BR,

Per

If I have a couple of attachments in a log book entry, I can link to that entry "http://example.edu/elog/Sandbox/7", I get the appropriate log in page, and after logging it, it takes me to the entry.

However, if I link directly an attachment, "http://example.edu/elog/Sandbox/7/1", I receive a plain log in page that doesn't have the stylesheet applied, and logging in, I am directed to " http://example.edu/elog/Sandbox/7/" which throws an invalid error. If I am already logged in the browser, it links correctly. 

I assume the problem must stem from messed up relative URL somewhere, hence the lack of stylesheet, or from the redirect incorrectly handling the /. (Looking at the source for the two login pages, the only difference is "<input type=hidden name=redir value="7">" versus "<input type=hidden name=redir value="7/1">". ) But that reaches the end of my ability...

This breaks the attachment links in emails.

Any help would be much appreciated!

Hi,

I was wondering what is the correct way so that the author field when a reply is made shows the author of the
person making the reply.
In version 2.6, the field was filled correctly but since upgrading to ELOG V2.9.1-2435 due to the ssh problem
the field just keeps the author of the original post.

I have a tried a number of subst on reply Author = $long_name with no luck.

Any ideas?

Cheers,
Aldo

Hi,

I installed ELOG on other machine for making automatic backups. I copied the .cfg file to the slave and edited the .cfg file on the original machine (mirror server entries).
(automatic configuration with -C didn't work somehow - maybe a firewall problem)

Then I tried to synchronize manually, which works great.
I set the mirror cron = 0 7-18 * * 1-5, as written as example in the documents, but nothing happens at full hours.

There's something else strange: I can't access "https://lx0.mydomain.org/" or "http://lx1.mydomain.org:8082/" directly. The browser just keeps loading - showing an empty page (and an error message after a long while). I have to add the name of the logbook to the link. Why is that?
If I set different paths in the [global HBAR] and [global SMI] areas (like URL = https://lx0.mydomain.org/hbar/), I can access the links above (giving me the overview page as expected), but I can't access the logbooks itself anymore.

However, that's not a big problem (I can access the logbooks via direct link and see all the others in the same group and switch to them), but the backup thing is.

So, main machine is lx0.mydomain.org and the backup machine is lx1...

Attached are my config files.
I deleted many of the logbook specific entries, since they aren't important and just look like the first one.

Hope anyone can help,
Roland.

The synchronize feature is totally worthless to me.

First of all the automatic backup doesn't work - and nobody seems to know why - and pressing the synchronize button by hand from time to time also doesn't work if the entry is too big:

Error sending local entry: Error transmitting message

So, copying the files manually helps, but for this I don't need a "fancy" synchronize feature.

In the elogd.c file nearly at the very top is the following line:

char svn_revision[] = "$Id: elogd.c 2411 2011-04-01 14:39:35Z ritt $";

How does this information get into the source file?  Is it a script used when the svn changes are committed, or perhaps when they are checked out?  Any details or pointers to info on the web would be greatly appreciated.

Thanks.

This gets handled automatically by SVN. All you have to do is to put an "$Id$" in your text somewhere and enable the keyword ID. See for example

http://svnbook.red-bean.com/en/1.4/svn.advanced.props.special.keywords.html