elogd.cfg for this demo site, posted by Stefan Ritt on Wed Aug 14 00:04:44 2002
|
Just since some people asked for: Here is the elogd.cfg for this demo
logbooks:
|
elogd.cfg cannot be saved, posted by Mo on Thu Jul 25 19:17:13 2002
|
Hello,
In the newest version of eLog, I was having trouble saving the
configurations once I change them through the web interface. I can change
|
elogd.cfg, posted by Aamir Khan on Tue Feb 25 22:35:44 2003
|
Stefan and friends,
without breaching your own security, could it be possible to see what the
|
elogd under Apache, login screen always reappears, posted by Michael Doerner on Sat Apr 5 00:33:36 2003
|
Hi,
I am new to elog so please bear with me if this sounds like a stupid
|
elogd service crashes after windows update, posted by Tom Roberts on Fri May 18 00:57:33 2018
|
We have been using elog on Windows 10 for a long time. Today, after a Windows update, the elogd service started crashing (error 1067, unexpected termination).
It ran fine just before the Windows update (which took > 1 hour, so it was a major one). Uninstalling and re-installing did not help, including replacing
my elogd.cfg with the default. Installing on another PC (that also has this update) fails in the same way. I have a good backup of my logbook. |
elogd runs by a user but not by root, posted by Dongwook Jang on Tue Apr 28 21:25:31 2009
|
Hi,
I really don't understand why elogd cannot run by root but it runs by a user.
I've put elog deamon in /etc/init.d. So it didn't bring up, but it runs if I run it by user interactively. |
elogd moves elog entries, posted by Konstantin Olchanski on Wed May 20 01:59:17 2015
|
elogd 3.1.0 moves all elog entries into year-named subdirectories. this feature makes it incompatible with older elogs and so should be clearly mentioned
in the documentation,
in the release announcement and in the release and migration notes. K.O. |
elogd lost entry database without restart during file system trouble, posted by Andreas Luedeke on Thu Apr 30 09:54:17 2015
|
I'm running ELOG since several years with rather heavy usage.
Last week I've upgrades from 3.0.0 to 3.1.0 and this week I had twice the same problem:
elogd lost the index for old entries and showed empty logbooks, without having restarted.
|