ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
1438
|
Mon Oct 10 10:52:02 2005 |
| Exaos Lee | Exaos.Lee@gmail.com | Bug report | Linux | Mac OSX | 2.6.0beta5 | Re: "Error: Cannot find hostname" |
Yes, the "URL" works. Thanks! |
1444
|
Mon Oct 10 19:22:51 2005 |
| Exaos Lee | Exaos.Lee@gmail.com | Bug report | Mac OSX | 2.6.0-beta | Install error on MacOS X |
Executing "make" on MacOS X is OK, but "make install" failed due to the following error:
/usr/bin/install -m 0755 -d /usr/local/bin /usr/local/sbin /usr/local/man/man1/ /usr/local/man/man8/
/usr/bin/install -m 0755 -o bin -g bin elog elconv /usr/local/bin
install: bin: Invalid argument
make: *** [install] Error 67
The reason is that the account "bin" and group "bin" are missing on MacOS X. I also found that the following lines in "Makefile" doesn't work:
ifeq ($(OSTYPE),darwin)
CC = cc
endif
I have fixed this problem. The diff of Makefile as following:
diff Makefile.darwin Makefile.origin
====================================
24,25d23
< BINOWNER = bin
< BINGROUP = bin
30,31d27
< OSTYPE = $(shell uname)
<
40,43d35
< ifeq ($(OSTYPE),Darwin)
< OSTYPE=darwin
< endif
<
46,47d37
< BINOWNER = root
< BINGROUP = admin
89,90c79,80
< $(INSTALL) -m 0755 -o ${BINOWNER} -g ${BINGROUP} elog elconv $(DESTDIR)
< $(INSTALL) -m 0755 -o ${BINOWNER} -g ${BINGROUP} elogd $(SDESTDIR)
---
> $(INSTALL) -m 0755 -o bin -g bin elog elconv $(DESTDIR)
> $(INSTALL) -m 0755 -o bin -g bin elogd $(SDESTDIR)
The modified Makefiles have been attached. |
1445
|
Mon Oct 10 19:26:35 2005 |
| Exaos Lee | Exaos.Lee@gmail.com | Request | All | 2.6.0beta5 | Re: Some spell mistakes |
Quote: | Ok, fixed in the current subversion repository. Better write such things by personal mail to me, since it might not interest the elog community very much. |
Sorry. I will mail you first next time. |
1446
|
Mon Oct 10 19:33:05 2005 |
| Exaos Lee | Exaos.Lee@gmail.com | Bug report | Linux | Mac OSX | 2.6.0beta5 | Re: Cannot submit admin password while logbook is named in Chinese |
Stefan Ritt wrote: |
Exaos Lee wrote: | As the title. |
There is no possibility to change an admin password. You probably mean that you logged in as admin and cannot change your own password, is that right? Do you use user level access via "password file = ..."? What is your elogd.cfg? I tried to switch language to German and I can change my own password via the config page. |
Sorry for my poor English. The case is like this: When I set an admin password for my logbook which is named in Chinese, I cannot open the config page while the password is correct. It seems that the logbook named in Chinese cannot recieve the password submitted. If the logbook is named other than Chinese, everything is OK. I will repeat the problem and describe it more exactly. |
2108
|
Wed Jan 10 22:54:56 2007 |
| Exaos Lee | Exaos.Lee@gmail.com | Info | All | SVN1780 | Chinese language files updated |
As the attachment.
Sorry for no update long time. |
2110
|
Sat Jan 13 17:35:45 2007 |
| Exaos Lee | Exaos.Lee@gmail.com | Question | | | How many topgroups can be defined? |
I defined 6 top groups in my cfg file as the attachment.
But ... It doesn't work as I wanted.
The 4th and 5th groups need login. But when I clicked the 4th or 5th group, the login isn't needed.
And the 4th and 5th password files are not generated automatically. |
2111
|
Sat Jan 13 17:47:45 2007 |
| Exaos Lee | Exaos.Lee@gmail.com | Request | All | | Group definition under top group |
Hi, I think, if we can put the "Group xxx = xxx" under some "global xxxx" sections, the configure file will be more clean. Don't you think so? In fact, if the "Group XXX" sections are put under "global XXX" section, the "Top Group XXX" can be ignored. I also found that some options (e.g. "Logbook dir =") under "global" don't work under "global XXX".
Maybe the configure file can be defined more flexible, such as this way:
[global]
Port = 8080
Top configuration = yes
[global Group1]
Group config = group1.cfg
[global Group2]
Group config = group2.cfg
The "group1.cfg" looks like this:
[global]
Top configuration = no
Password file = group1.pwd
Group Linux PCs = Red Hat, Debian, Gentoo
Group Windows PCs = 98, ME, XP, Vista
Group Vista = Home, Pro, Media Center
[Red Hat]
...
|
69472
|
Thu Feb 10 19:03:56 2022 |
| Ezio Zanghellini | zanghell@chalmers.se | Info | Windows | 314-2 | ELOG problems with certificates |
Recently I have had problems with ELOG not accepting the certificates (in this case from https://letsencrypt.org/) probably due to the old version of the SSL library of the binary distribution for Windows.
I have tried to follow the instructions to set up ELOG to work with Apache but they are probably old.
I have a simple solution for the Apache installation of XAMPP, the example is for two separate logbooks using each its own ELOG service on the same server:
1. I have set up the two ELOG to run as http://my.server.example.com:8080/ and as http://my.server.example.com:8081/
2. in c:\xampp\apache\conf\httpd.conf I have enabled the following (I am not sure if all the modules are really needed but this works for me):
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule headers_module modules/mod_headers.so
LoadModule proxy_html_module modules/mod_proxy_html.so
LoadModule xml2enc_module modules/mod_xml2enc.so
3. still in c:\xampp\apache\conf\httpd.conf, at the very end of the file I added the following:
ProxyRequests off
Redirect permanent /app1 https://my.server.example.com/app1/
ProxyPass /app1/ http://my.server.example.com:8080/
ProxyHTMLURLMap http://my.server.example.com:8080 /app1
Redirect permanent /app2 https://my.server.example.com/app2/
ProxyPass /app2/ http://my.server.example.com:8081/
ProxyHTMLURLMap http://my.server.example.com:8081 /app2
This way I can now connect to the two ELOG using https://my.server.example.com/app1/ and https://my.server.example.com/app2/ without troubles and no additional setting to either the configuration files of ELOG nor any need for virtual hosts, ...
I hope this might be of use.
|