| bob wrote: |
|
| Stefan Ritt wrote: |
|
| bob wrote: |
|
hello,
At home, when I change the config *. cfg, the modifications are not taken in consideration
Have you got a idea ?
Thanks a lot ! 
Bob
|
Not really, you are the first one reporting this issue. Just some thoughts:
- Can you see the changes if you look at elogd.cfg with a text editor such as notepad?
- Some write protection of elogd.cfg
- Do you have more than one server running at the same time and changing the wrong one's config?
- Stefan
|
>- Can you see the changes if you look at elogd.cfg with a text editor such as notepad?
I change the configuration directly on elogd.cfg, (after i save and update my web page, and i not modification immediately)
>- Some write protection of elogd.cfg
no
- Do you have more than one server running at the same time and changing the wrong one's config?
i have one server with elog
|
Let me report when I see this behaviour.
If I use a text editor on elog.cfg directly, while elog is running, then when I save the file, the new elog.cfg is in place,
but the running elog is still running with the old configuration. You have to restart elog for it to read the new config file and
use the new settings.
This does not apply if you edit elog.cfg via the "config" option in the menu command, where elog will read the new elog.cfg
just after it has been saved.
The reason I sometimes edit the file directly is if I want to create a new logbook, but with all the configuration of another logbook,
and it's quickest to cut-and-paste, change the heading, create a new directory and restart elog.
This may be completely off what is being reported. |