Unable to set a custom logbook dir on Debian 8 from the repository package, posted by S. Caiazza on Tue May 31 19:53:59 2016
|
Dear all
I installed elog from the current stable repository on Debian 8 (jessie)
The installation went on smoothly, I modified the configuration files of the Apache server as described in the manual to use the elog in parallel |
Unable to set a custom logbook dir on Debian 8 from the repository package, posted by S. Caiazza on Tue May 31 20:03:53 2016
|
Dear all
I installed elog from the current stable repository on Debian 8 (jessie)
The installation went on smoothly, I modified the configuration files of the Apache server as described in the manual to use the elog in parallel |
Re: Unable to set a custom logbook dir on Debian 8 from the repository package, posted by Stefan Ritt on Mon Jun 27 16:06:55 2016
|
The debian version of elog is pretty old with quite a number of bugs fixed in meantime. Unfortunatlely the debig packase has not bee updated by the maintainers.
So better download the current version from bitbucket and compile elogd yourself.
S. |
|
Different logbook files when running elogd as admin or normal user, posted by Antonio Bulgheroni on Thu Jul 21 07:44:04 2016
|
Dear all, I have a problem with my window elog installation (2.9.2) and I would like to ask your help for solving it.
I'm using elog on my lab computer for a single user installation, so something very simple. It was running smoothly for many months using
the automatic window service (i.e. elogd was started automatically at boot). I need to add that the service is started as the local administrator, while |
|
Re: Different logbook files when running elogd as admin or normal user, posted by Stefan Ritt on Thu Jul 21 08:08:07 2016
|
I don't know why elogd uses different logbook directories depending on the user. Maybe you start it in different directories, or one user cannot
read the config file and falls back to some default. Anyhow, you can start elogd interactively wit the -v flag which tells you which logbook files are
parsed. There are no cache files or similar, everything is stored in Yymmdda.log files, you just have to search for them. |
|
Re: Different logbook files when running elogd as admin or normal user, posted by Antonio Bulgheroni on Thu Jul 21 09:37:47 2016
|
So I found the my log files, but this issue should probably be documented.
When running as admin my logbook files are where they should (C:\Program Files (x86)\ELOG\logbooks)
When running as local user (with no admin rights), elogd has no writing access to the logbooks directory. So it falls back to use C:\Users\[MyUserName]\AppData\Local\VirtualStore\Program |
|
Full anonymous access, posted by K on Thu Apr 20 12:45:11 2017
|
How can i configure eLog to be used completely anonymous without the need to log in?
I tried menu and guest menu settings without luck. I do not use password files. With earlier versions this was easy to set up...
|
|
Re: Full anonymous access, posted by Stefan Ritt on Thu Apr 20 12:59:24 2017
|
Sure. Just remove "Password file = ..." and any guest menu.
Stefan
K |