Re: Can't subscribe email to logbooks in different top groups, posted by Stefan Ritt on Fri Apr 12 15:43:42 2019
|
Top groups should use separate password files, otherwise things can mess up.
Stefan
Ben |
|
Re: Pinned entry, posted by Stefan Ritt on Tue Apr 23 10:00:48 2019
|
This is not directly possible, but you can configure it with a trick. Create an attribute "pinned", make it of type "boolean", and
set the start page such that it sorts using the "pinned" attribute:
Atributes = ..., Pinned |
|
Re: elogd Service exited with abnormal code: 1, posted by Stefan Ritt on Tue Apr 23 14:26:51 2019
|
This kind of behavior we typically see if some elog entry is corrupt. After a few hours you might access this corrupt entry by accident, and then the
server stops. If you see however this behavior on a fresh logbook with no corrupt entries, then the problem must lie somewhere else.
Do you see the same problem running under linux? |
|
Re: elog program does not respect "Allow edit" list, posted by Stefan Ritt on Wed Apr 24 10:15:23 2019
|
There are two ways:
1) Use different password files for different logbooks. Each password file contains only those users which have access to that logbook.
2) Use "Login user = <usr list>" to restrict access to certain users in that list. |
|
Re: elog program does not respect "Allow edit" list, posted by Stefan Ritt on Wed Apr 24 10:29:00 2019
|
There is no "read only" flag. Please describe what you exactly did. Probably you want "Restrict edit time" for that.
Stefan
Heinz |
|
Re: elog program does not respect "Allow edit" list, posted by Stefan Ritt on Wed Apr 24 11:30:37 2019
|
So you are telling me that "Restrict edit time" is not working correctly? In order to fix any problem, I have to reproduce it. Can you post
a minimel elogd.cfg file with which I can reproduce the problem?
Stefan |
|
Re: elogd Service exited with abnormal code: 1, posted by Stefan Ritt on Thu Apr 25 11:27:21 2019
|
What you recommend is enough. Just make sure to compile elogd with the flags mentioned before, and when you get the segment violation, do a stack trace
inside the debugger to learn where the fault happend. Maybe also print the contents of some variables at the current location.
Stefan |
|
Re: elog program does not respect "Allow edit" list, posted by Stefan Ritt on Fri Apr 26 17:22:46 2019
|
Ok, I found the issue. The "Restrict edit time" is only checked when one clicks on "Edit" in the browser. The elog command line tool
does not really an edit, but just submits an entry with an (old) ID. I added a check also for that case so now it should work. The commit is in git.
Stefan |