Error message: "Attachment #6 of entry #0 not found", posted by Christian Schult on Sun Oct 16 10:33:23 2005
|
Hi all, I get messages like this
Attachment #16 of entry #0 not found |
Re: Error message: "Attachment #6 of entry #0 not found", posted by Christian Schult on Tue Oct 18 08:02:44 2005
|
> > Hi all, I get messages like this
> > Attachment #16 of entry #0 not found
> > Please use your browser's back button to go back
|
|
when using webserver authentication, how can I restrict the users that can edit any given elog?, posted by Christian Ospelkaus on Sat Jun 19 18:38:21 2021
|
Dear elog users & developers,
the subject line says it all: when using webserver authentication, how is it possible to restict access of users to any given elog? Only using
the apche rules? Admin user and Login user do not seem to be doing anything for me. I am using elog as packaged by debian for buster, using an apache ssl |
|
Re: when using webserver authentication, how can I restrict the users that can edit any given elog?, posted by Christian Ospelkaus on Sun Jun 20 14:38:06 2021
|
Dear all,
I figured it out. Current global config is (using kerberos instead)
[global] |
|
elogd dies upon search, posted by Christian Ludwig on Fri Jun 3 08:16:31 2016
|
Hi all,
ELOG V3.0.0-21dc563
Our elogd dies alwways when searching for full text: |
solved: elogd dies upon search, posted by Christian Ludwig on Fri Jun 3 08:59:49 2016
|
I would like to share my findings about the solution of our problem:
One of my collegues used elog in a way it was not intended for, he put an endry with 8021 lines of text.
So I grabbed the corresponding 160517a.log file from logdir, renamed it to a text file and created a new entry with the large textfile as attachment. |
|
Compiling elog 2.0.4 on Solaris, posted by Christian Korschan on Mon Jul 8 21:01:00 2002
|
Comiling elogd 2.0.4 under Solaris obviously fails with
gcc -o elog elog.c -lsocket -lnsl
|
|
elog-2.0.5 core dumps under Solaris, posted by Christian Korschan on Wed Jul 24 16:44:44 2002
|
Just compiled elog-2.0.5 under Solaris 8 and 9 without any warnings/errors
but the elogd binary just core dumps:
|