In a configuration with elog running (8080) under Apache (80) [as explained in admin guide], what is the syntax for tunnelling in with ssh, of both the ssh command and the browser locator?

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

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

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 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. 

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.

•  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"

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"?