Re: Custom input forms implementation, posted by Andreas Luedeke on Sat Jul 9 10:44:45 2016
|
You might try to specify an absolute path to the password file in the configuration.
I would need a complete minimal configuration that creates that problem.
|
Using Reply option, posted by Jason S on Tue Jul 12 16:18:46 2016
|
Forgive me I'm not incredibly Elog savy yet.
A little backround about this log book - I have our log set up as individual user names. The log book is designed for entrys to be
made when a process shutdown needs to be bypassed. The operator will create an entry and submit it. Then a supervisor will come in after |
|
Re: Using Reply option, posted by Andreas Luedeke on Tue Jul 12 19:39:04 2016
|
Preset on reply Author = $long_name
Cheers, Andreas
Jason |
|
Re: Using Reply option, posted by Jason S on Tue Jul 12 20:53:03 2016
|
Works Great. Thanks Andreas
Andreas Luedeke wrote:
Preset on reply Author |
|
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 |
|
Image source url missing, posted by Antonio Bulgheroni on Thu Jul 21 13:08:44 2016
|
Dear all, sorry for asking you another question, but today after I finally recovered all my logbook entries, I updated to elog 3.1.1 and now I have a
problem uploading images.
This is what I do: |