Ah, I see another problem. The pre 3.1 version had all logbook files in one directory, and the 3.1 puts the files in one subdirectoy per year. On transition from 3.0 to 3.1, an automatic conversion is made, but only once. If you later add files into the root logbook directory, they will not be seen. So you have to move them manually into the right subdirectory.
| Mike Giles wrote: |
|
Thanks very much for your comments. I will take a look at the mirror server functionality.
I have only been running one elogd at a time, restarting elogd (on Windows 10) doesn't seem to pick up the changes made on Windows 8.1 PC (stopped elogd after changes made and log file updated)
Mike
| Stefan Ritt wrote: |
|
Besides the commen Andrea made I would like to add that you can convince elog to show all files if you simply restart it, then it will re-scan all files. But as Andreas said, if two elogd instances write to the same directory, you will get a mess with double IDs of entries.
Stefan
| Mike Giles wrote: |
|
Hi,
I'm having an issue with Elog 3.1.1 on windows 10 not displaying all log entries (after a certain date) in a logbook directory.
The logbook is saved in a Dropbox folder and the entries were created on a windows 8.1 PC with 3.1.1 also.
I created an entry in windows 10, this created a new log file (new day) with a duplicate ID, deleted the log file and then the windows 10 pc displayed all entries.
Is there any way to ensure Elogd picks up all log files ?
Thanks & Regards,
Mike
|
|
|
|