|
Demo
Discussion
|
Forum
Config Examples
Contributions
Vulnerabilities
|
Discussion forum about ELOG |
Not logged in |
|
|
|
Message ID: 1517
Entry time: Fri Nov 18 21:03:03 2005
In reply to: 1512
Reply to this: 1522
|
|
Category: |
Question |
OS: |
Windows |
ELOG Version: |
2.6.0beta5 |
|
Subject: |
Re: Automatic creation of new entry in another logbook |
|
|
Carlos Mateo wrote: | I am trying to create an entry in logbook2 when I submit a new entry in logbook1. The automatically created entry in logbook2 will have a reference to the entry that created it. |
Please tell me for what purpose you need two identical logbooks. Maybe what you want can be achieved in a simpler way.
Carlos Mateo wrote: | 1.- Using the "Execute new" I call elog to create the second entry. As the server is single-process, it locks: elog is waiting for elogd to be ready and elogd is waiting for elog to finish to accept new requests. As my server is on a Windows machine I canīt execute elog on background. |
Have you tried to start your elog with the start command under Widnows, like start elog .... This is the equivalent of starting a process in the background under linux.
Carlos Mateo wrote: | 2.- I tried to run 2 servers on different ports using the same elogd.cfd file, calling the second server from elog. This "almost" works: the logbook files are updated, but the original server must be restarted to "see" the changes. |
This is because you use the same data directory for both servers. If one server writes a new entry to a file, the other server does not realize this. Only when you restart it, it rescans the whole data directory and gets aware of the new entry. Try using separate data directories for the two servers.
Carlos Mateo wrote: | 3.- Using the "Menu text" option, I create a link to create the new entry. The problem is that attributes are not parsed: a link like this <a href="/logbook2/?cmd=New&pAttr=Value $ID">Test</a> wonīt substitute $ID |
Parsing attributes is not implemented and therefore will not work. |