FreeBSD Install, posted by Jason on Sun Sep 21 09:33:46 2003
|
I am getting the following errors when trying to install elog-2.3.9 on
my FreeBSD box. I am running FreeBSD 4.5-RELEASE.
Many thanks!
"Makefile", line 21: Missing dependency operator
"Makefile", line 27: Need an operator
"Makefile", line 29: Missing dependency operator
"Makefile", line 31: Need an operator
make: fatal errors encountered -- cannot continue
You4eea |
|
Adding New User Failed During Email Send, posted by Jason Moore on Wed Jan 17 18:11:49 2018
|
The following error occured during the addition of new user, first time this occured:
"Cannot send email notification to "xxx@xxx.com" Sender address rejected: Domain not found
Please use your browser's back button to go back
We are using version 2.7.1-2002. Could this be a version issue? When we loaded the new version, the browser GUI was scrambled and illegible using Microsoft Edge/Explorer and Firefox. |
Crash on attachment upload, posted by jaro mrazek on Thu Sep 12 10:42:08 2024
|
I am on ubuntu 24.04.1, I needed to git clone, make and make install,
HEAD is 3fb85fa6 - (HEAD -> master, origin/master, origin/HEAD) Fixed compiler warning (3 weeks ago)
It crashes on every attachment: thank you. Jaro
root@vaio:~# systemctl status elogd
× elogd.service - The ELOG Server
Loaded: loaded (/usr/lib/systemd/system/elogd.service; enabled; preset: ena>
Active: failed (Result: core-dump) since Thu 2024-09-12 10:39:23 CEST; 3s a>
Duration: 5.402s
Docs: man:elogd(8)
man:elog(8)
Process: 724285 ExecStart=/usr/local/sbin/elogd -D -c /usr/local/elog/elogd.>
Main PID: 724286 (code=dumped, signal=ABRT)
CPU: 32ms
Sep 12 10:39:18 vaio systemd[1]: Starting elogd.service - The ELOG Server...
Sep 12 10:39:18 vaio elogd[724286]: elogd 3.1.5 built Sep 11 2024, 17:02:36
Sep 12 10:39:18 vaio elogd[724286]: revision 3fb85fa6
Sep 12 10:39:18 vaio elogd[724286]: File "/var/run/elogd.pid" exists, overwritin>
Sep 12 10:39:18 vaio systemd[1]: Started elogd.service - The ELOG Server.
Sep 12 10:39:18 vaio elogd[724286]: CKeditor detected
Sep 12 10:39:18 vaio elogd[724286]: ImageMagick detected
Sep 12 10:39:18 vaio elogd[724286]: Server listening on port 9000 ...
Sep 12 10:39:23 vaio systemd[1]: elogd.service: Main process exited, code=dumped>
Sep 12 10:39:23 vaio systemd[1]: elogd.service: Failed with result 'core-dump'.
root@vaio:~# systemctl restart elogd
|
number of entries in Login user list, posted by Janusz Szuba on Wed Jun 13 18:08:06 2018
|
Hi,
could it be possible to increase the limit of entries in Login user list from 100 to somewhat reasonably higher? Like twice or 3 times as much. Similar limit exist also on Admin user list, which is afair 10, could this also be increased?
best
Janusz |
Re: number of entries in Login user list, posted by Janusz Szuba on Thu Jun 14 13:07:32 2018
|
Thanks, good point, I was not sure that in case of other lists which will be changed as well, there will not be any problems, like overflow, etc.
Regarding admin list, now I remember, that was the limit to send email notification in case of registration requests. But actually it is not important right now.
best
Janusz
| Andreas Luedeke wrote: |
|
Hi Janusz,
You can change the following line in elogd.h and recompile:
#define MAX_N_LIST 100
That'll change the login user list limit. But it'll change other list length as well - which should not do harm unless you are very short of memory.
I don't see the Admin user list limit of 10 - aparently that is hard coded somewhere deep within (or I've just missed it).
Cheers, Andreas
| Janusz Szuba wrote: |
|
Hi,
could it be possible to increase the limit of entries in Login user list from 100 to somewhat reasonably higher? Like twice or 3 times as much. Similar limit exist also on Admin user list, which is afair 10, could this also be increased?
best
Janusz
|
|
|
|
bug in elog.spec, posted by Janusz Szuba on Mon Jul 6 19:09:48 2020
|
Hi,
in commit 1812e7c, specifying CFLAGS to make command in elog.spec, renders all other settings in Makefile void. That is, if I want to include any of KRB5, LDAP, PAM support, and change makefile accordingly, then when producing rpm they are not taken into account. Anyway, CFLAGS in Makefile are already set to the same defaults, so why it is redefined in spec file?
best
Janusz |
|
Re: bug in elog.spec, posted by Janusz Szuba on Tue Jul 7 11:22:45 2020
|
Thanks for the answer, I will try with your specfile
best
Janusz
| Laurent Jean-Rigaud wrote: |
|
Hi,
You rights, CFLAGS should not be in specfile to take care of distrib env.
Btw, I sent in the past an update for build process of Stefan delivery to generate src.rpm file copatible to tarball version. I think Stefan did not have time yet to test and to check.
With the enclosed SPEC file, you can build ELOG with options at rpmbulld command w/o modifying sources. For exemple,
rpm -i elog-.....src.rpm
rpmbuild -bb --with ssl --with pam --with ldap --with krb5 ~/rpmbuild/SPECS/elog.spec
I enclosed also the SRPMS i used for my projects. Be careful, It's maybe not uptodate of last GIT version or PSI releases... but you can test it on your RPM distrib. It should be nice to hare your feedback.
Bye,
Laurent
| Janusz Szuba wrote: |
|
Hi,
in commit 1812e7c, specifying CFLAGS to make command in elog.spec, renders all other settings in Makefile void. That is, if I want to include any of KRB5, LDAP, PAM support, and change makefile accordingly, then when producing rpm they are not taken into account. Anyway, CFLAGS in Makefile are already set to the same defaults, so why it is redefined in spec file?
best
Janusz
|
|
|
|
Deny option and Guest commands, posted by Janusz Szuba on Mon Jul 19 18:41:29 2021
|
Hi,
I have a logbook with guest access and guest can also enter a new entry (in config: Guest List Menu commands = New, Find, Select, Login). For other reason in a global section, I put
Deny New = account1, account2
This somehow invalidates Guest List Menu commands, since as guest I don't see New button anymore. Is this behaviour desired? Otherwise, I would need to move Deny option to plenty of individual logbook configs. Just to explain the reason, those accounts are set up to only read entries and not to create new ones. Or maybe you can suggest a different solution?
Best |
|