Re: elog submit without user and password, posted by H. Scheit on Tue Jul 9 15:28:33 2002
|
> > With elog it is possible to submit messages to a password protected
> > logbook without specifying the -u option. I.e. NO PASSWORD is
> > necessary to submit a message. I assume it is related to the problem
|
|
Re: elog submit without user and password, posted by Stefan Ritt on Wed Jul 10 08:53:21 2002
|
> I guess it cannot and doesn't have to be 100% save. Maybe if the web
> interface is used for a new message a long random number (let's call
> it newID) can be included, which elog remembers for some time (say 1
|
|
Re: elog submit problem, posted by Stefan Ritt on Mon Jul 8 10:44:08 2002
|
> If a message is submitted via the elog command then the reply string '> '
is only inserted in the first line if a reply is made.
> This message was submitted with the following commandline:
|
|
Re: elog sprintf() buffer overflows on ubuntu-22, posted by Stefan Ritt on Wed Sep 25 13:19:29 2024
|
> I get the following compiler warnings about sprintf() buffer overflows. I suggest sprintf() should be replaced by std::string msprintf() from
> midas. K.O.
|
|
Re: elog slowness, posted by Stefan Ritt on Thu Jan 14 14:05:19 2021
|
Have you tried to restart the elogd server? The CLOSE_WAIT could be dangling network connections, which were not properly closed by the browser.
Giuseppe
Cucinotta wrote:
We run elog on a server to provide a logbook for our laboratory. |
|
Re: elog service crashes frequently, posted by Andreas Luedeke on Sun May 22 11:56:21 2016
|
We do run ELOG on a Linux server and see about weekly crashes, too. It seems to be connected to the authentication process (Kerberos, File), but we could
not nail it down yet.
But we have set up a supervision process that checks every minute if the "elogd" process is still running. If not, it simply restarts |
|
Re: elog server go to high CPU and hangs, posted by David Pilgram on Thu Feb 18 12:05:52 2021
|
Dear Stefano,
Try the entry I wrote some time ago elog:68655
|
|
Re: elog server go to high CPU and hangs, posted by Stefan Ritt on Thu Feb 18 12:06:12 2021
|
Usually a restart of the elogd server helps. If the problem persists, one of the logbooks might be corrupt. Try to disable one logbook at a time to figure
out which one it is. Then
remove that one and set it up freshly.
|