Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 734 of 796  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSup ELOG Version Subject Text Attachments
  Draft   Sat Jul 9 10:44:45 2016 Reply Andreas Luedekeandreas.luedeke@psi.chInfoWindows3.1.1Re: Custom input forms implementationYou might try to specify
an absolute path to the password file in
the configuration.
  
  68355   Tue Jul 12 16:18:46 2016 Question Jason Stitancomp@hotmail.caQuestionWindowsV3.1.1-3f311c5Using Reply optionForgive me I'm not incredibly Elog
savy yet.

A little backround about this log
  
  68356   Tue Jul 12 19:39:04 2016 Reply Andreas Luedekeandreas.luedeke@psi.chQuestionWindowsV3.1.1-3f311c5Re: Using Reply optionPreset on reply Author = $long_name
Cheers, Andreas

  
  68357   Tue Jul 12 20:53:03 2016 Reply Jason Stitancomp@hotmail.caQuestionWindowsV3.1.1-3f311c5Re: Using Reply optionWorks Great. Thanks Andreas

  
  68364   Thu Jul 21 07:44:04 2016 Question Antonio Bulgheroniantonio.bulgheroni@gmail.comQuestionWindows2.9.2Different logbook files when running elogd as admin or normal userDear all, I have a problem with my window
elog installation (2.9.2) and I would like
to ask your help for solving it.
  
  68365   Thu Jul 21 08:08:07 2016 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.9.2Re: Different logbook files when running elogd as admin or normal userI don't know why elogd uses different
logbook directories depending on the user.
Maybe you start it in different directories,
  
  68366   Thu Jul 21 09:37:47 2016 Reply Antonio Bulgheroniantonio.bulgheroni@gmail.comQuestionWindows2.9.2Re: Different logbook files when running elogd as admin or normal userSo I found the my log files, but this issue
should probably be documented.

When running as admin my logbook
  
  68367   Thu Jul 21 13:08:44 2016 Question Antonio Bulgheroniantonio.bulgheroni@gmail.comQuestionWindows3.1.1Image source url missingDear all, sorry for asking you another
question, but today after I finally recovered
all my logbook entries, I updated to elog
  
ELOG V3.1.5-2eba886