Re: elogd complains about unknown cookies, posted by Konstantin Olchanski on Sat May 23 02:49:22 2015
|
> > elogd is spewing these messages about unknown cookies:
> >
> > Received unknown cookie "is_returning"
|
|
Re: elogd moves elog entries, posted by Konstantin Olchanski on Sat May 23 02:53:31 2015
|
>
> "News for each version can be seen in the changelog (->http://midas.psi.ch/elog/download/ChangeLog)"
>
|
Cannot download large attachments, posted by Konstantin Olchanski on Tue Jul 14 19:29:17 2015
|
Older versions of elogd have a problem with sending long attachements - the send() syscall is not protected against interrupt by SIGALARM. This seems to
be fixed in non-SSL builds of current elog (version 3+),
but for SSL builds, the error handling for the SSL_write() function looks incorrect. In addition, from OpenSSL documentation it is not clear if SSL_write() |
make all messages on ubuntu LTS 20.04.03, posted by Konstantin Olchanski on Tue Feb 8 00:52:47 2022
|
For the record, compiler messages from elog tip of branch elog/master.
Most of the stuff is the usual same-old that we mostly fixed in midas:
|
|
Re: make all messages on ubuntu LTS 20.04.03, posted by Konstantin Olchanski on Tue Feb 15 20:55:02 2022
|
> Well, I bit the bullet and fixed all of these warnings. Took me like two days of work, but now should be fine.
> You might want to test it again.
|
|
Re: make all messages on ubuntu LTS 20.04.03, posted by Konstantin Olchanski on Wed Feb 16 20:01:17 2022
|
> I fixed these as well, please have a look again. BTW, midas had a few of these as well.
confirmed. elog commit d828aa58305ee8ce2ae882c0ff3c34cfa66650e5
|
|
Invalid activation code, posted by Konstantin Olchanski on Wed Mar 2 18:29:08 2022
|
Something is not right with the elog account activation, I get the email
for "Registration request for ELOG logbook "haicu"", but when I follow the given URL,
I get "Invalid activation code". Account activation requests go to two people,
|
|
login cookie confusion, posted by Konstantin Olchanski on Wed Mar 2 18:35:48 2022
|
we had an elog with only one logbook and one password file,
we added a second logbook with a second password file and everything broke.
|