Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 112 of 806  Not logged in ELOG logo
IDdown Date Icon Author Author Email Category OS ELOG Version Subject Text Attachments
  68939   Wed Apr 24 11:03:26 2019 Reply Heinz Junkesjunkes@fhi-berlin.mpg.deBug reportAllelogd 3.1.4Re: elog program does not respect "Allow edit" listSorry, 

I meant "read only" by
using "Restrict edit time" settings.
  
  68938   Wed Apr 24 10:29:00 2019 Reply Stefan Rittstefan.ritt@psi.chBug reportAllelogd 3.1.4Re: elog program does not respect "Allow edit" listThere is no "read only" flag.
Please describe what you exactly did. Probably
you want "Restrict edit time" for
  
  68937   Wed Apr 24 10:21:58 2019 Reply Heinz Junkesjunkes@fhi-berlin.mpg.deBug reportAllelogd 3.1.4Re: elog program does not respect "Allow edit" listThanks for the answer. The real problem
is that you can overwrite existing entries
even if you have set an entry to "read
  
  68936   Wed Apr 24 10:15:23 2019 Reply Stefan Rittstefan.ritt@psi.chBug reportAllelogd 3.1.4Re: elog program does not respect "Allow edit" listThere are two ways:

1) Use different password files
for different logbooks. Each password file
  
  68935   Wed Apr 24 09:43:02 2019 Reply Heinz Junkesjunkes@fhi-berlin.mpg.deBug reportAllelogd 3.1.4Re: elog program does not respect "Allow edit" listSince there's no answer to that.
I am the only one with the problem? Did
I just configure something wrong?
  
  68934   Wed Apr 24 09:15:26 2019 Question Nikolas Patronisnpatronis@uoi.grQuestionLinux3.1.3exclude access to a number of users in one logbookHow can I exclude the access of a number
of users in one (out of two) logbooks running
in the same server and URL?
  
  68933   Tue Apr 23 14:26:51 2019 Reply Stefan Rittstefan.ritt@psi.chBug reportMac OSX3.1.4Re: elogd Service exited with abnormal code: 1This kind of behavior we typically see
if some elog entry is corrupt. After a few
hours you might access this corrupt entry
  
  68932   Tue Apr 23 14:06:36 2019 Warning Alessio Sartialessio.sarti@uniroma1.itBug reportMac OSX3.1.4elogd Service exited with abnormal code: 1Dear all.

I am running elog 

elogd
  
ELOG V3.1.5-3fb85fa6