| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
255
|
Thu Mar 20 21:07:09 2003 |
 | djek | djek@nospam.invalid | Bug report | | | Re: Elog 2.3.3, problems of 2.3.2 solved |
> > After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
> > as stylesheets, images or passwordfiles.
> >
> > Cannot open file /usr/local/elogdata/logbooks/djeks/password!
>
> If you installed from the RPM, elogd runs under the user "elog". If you have
> installed a previous version under a different user, it might be that elogd
> does not have read or write access to it. A
>
> "chown -R elog.elog /usr/local/elogdata"
>
> might help.
>
It did, a lot, guess I missed that one in the changelog.
Had some trouble with subdir too:
changed it to its full path
restarted elogd
worked
As a test I changed subdir to it's relative path
restarted
It kept working
mmmm, I wonder where that twighlight tune comes from ... |
|
254
|
Thu Mar 20 21:07:09 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | | | Re: Elog 2.3.3, problems of 2.3.2 only partly solved |
> After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
> as stylesheets, images or passwordfiles.
>
> Cannot open file /usr/local/elogdata/logbooks/djeks/password!
If you installed from the RPM, elogd runs under the user "elog". If you have
installed a previous version under a different user, it might be that elogd
does not have read or write access to it. A
"chown -R elog.elog /usr/local/elogdata"
might help.
- Stefan |
|
253
|
Thu Mar 20 21:07:09 2003 |
 | djek | djek@nospam.invalid | Bug report | | | Elog 2.3.3, problems of 2.3.2 only partly solved |
After upgrading from 2.3.1 to 2.3.3, elog is not able to load any resources
as stylesheets, images or passwordfiles.
Cannot open file /usr/local/elogdata/logbooks/djeks/password!
oops? |
|
249
|
Sun Mar 16 19:15:16 2003 |
 | Recai Oktas | roktas@omu.edu.tr | Info | | | Elog and SSL |
> Basically im running elog on a redhat 8 box with stunnel already installed
> as part of OpenSSL, on the server i ran the command specified in the
> instructions
>
> stunnel -d 443 -r 172.16.24.108:81
I haven't tried `stunnel` with elog, but as far as I read from various
sources, stunnel requires you to create an SSL certificate. In attachment,
you'll find a sample case for stunnel and smtp (port 25) + pop3 (port 110).
Hope this helps.
Reference: http://www.tldp.org/linuxfocus/common/sart/index.html |
|
248
|
Fri Mar 14 10:30:25 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | | | Re: Problems with 2.3.2 |
> > Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to
> > port bindings, basically im running elog bound to port 81 and when i
> > install the new RPM it refuses to bind to this port, i tried port 8080
and
> > that worked fine
The bug has been fixed in V 2.3.3 which has been released today. |
|
247
|
Thu Mar 13 17:33:58 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | | | Re: Problems with 2.3.2 |
> Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to
> port bindings, basically im running elog bound to port 81 and when i
> install the new RPM it refuses to bind to this port, i tried port 8080 and
> that worked fine
>
> Any ideas ?
This is a bug I discovered myself just today, so we are working on it. I
expect this to be fixed by tomorrow or somewhen during this weekend.
- Stefan |
|
246
|
Thu Mar 13 17:30:16 2003 |
| nick | nick@nick.com | Bug report | | | Problems with 2.3.2 |
Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to
port bindings, basically im running elog bound to port 81 and when i
install the new RPM it refuses to bind to this port, i tried port 8080 and
that worked fine
Any ideas ? |
|
245
|
Tue Mar 11 18:40:39 2003 |
 | Aamir Khan | aamir@aamir.uk.com | Question | | | Compile on AIX 5L |
Dear Friends,
Anyone managed to compile elog on AIX 5.2 or 5.1 ... is there a binary
anywhere?
new to "C"
kind regards Aamir |