Re: Request: can the comment for a log book be put in the status bar on hover, posted by Gary Clayson on Thu Jul 7 04:47:09 2005
|
| Tim Iskander wrote: | We have several logbooks running here with somewhat cryptic names. The comment field for the
logbook describes its intent well enough, so the thought was that the comment could show up in the
status bar (or tooltip) when you hover over the logbook name in the tabs at the top of the page.
___ yea 
___ nea 
/Tim |
I wonder if there is any way to use the javascript 'window.status' method to accomplish this. It would be a nice addition when there are many logbooks.
Gary ;-> |
Re: Request: can the comment for a log book be put in the status bar on hover, posted by Stefan Ritt on Thu Jul 7 21:48:31 2005
|
| Tim Iskander wrote: | We have several logbooks running here with somewhat cryptic names. The comment field for the
logbook describes its intent well enough, so the thought was that the comment could show up in the
status bar (or tooltip) when you hover over the logbook name in the tabs at the top of the page. |
_X_ yea
___ nea
I added a tooltip to the logbook showing the comment field. The status bar is a bit difficult since it requires Javascript and is not supported by all browsers. But I hope the tooltip is good enough. The modification is in CVS, you can try it at the forum.
- Stefan |
Re: Request: can the comment for a log book be put in the status bar on hover, posted by Tim Iskander on Fri Jul 8 13:32:56 2005
|
| Stefan Ritt wrote: |
| Tim Iskander wrote: | We have several logbooks running here with somewhat cryptic names. The comment field for the
logbook describes its intent well enough, so the thought was that the comment could show up in the
status bar (or tooltip) when you hover over the logbook name in the tabs at the top of the page. |
_X_ yea
___ nea
I added a tooltip to the logbook showing the comment field. The status bar is a bit difficult since it requires Javascript and is not supported by all browsers. But I hope the tooltip is good enough. The modification is in CVS, you can try it at the forum.
- Stefan |
I like it!
thanks...
/Tim |
|
Email notifications not working properly, posted by Stefan Ritt on Thu Mar 26 17:30:23 2009
|
I just found out that email notifications only worked for the first 50 users of this forum. So if you registered only recently, you might not have received any notification. This was a bug inside elogd which I hope to have fixed now (this entry notification will show...). If you get the first notification and do not want this, log in to the ELOG Forum, click on "Config" and remove the checkmarks from the logbooks you do not want to get notifications. |
Configuration problems, posted by Erich Beyrent on Mon Feb 14 17:10:00 2005
|
I am trying to run eLog under Apache 2 on my FreeBSD 5.3 server. I started
the daemon with "elogd -n <my hostname> -p 8080" and when I connect to my
server on that port, I get a 500 server configuration error. The Apache log
contains this:
malformed header from script. Bad header=Please specify hostname.: elog
I am running elogd 2.5.7-1 built Feb 14 2005, 09:55:19 revision 1.558
Any assistance would be greatly appreciated!
-Erich- |
|
Re: Configuration problems, posted by Stefan Ritt on Mon Feb 14 19:03:31 2005
|
> I am trying to run eLog under Apache 2 on my FreeBSD 5.3 server. I started
> the daemon with "elogd -n <my hostname> -p 8080" and when I connect to my
> server on that port, I get a 500 server configuration error. The Apache log
> contains this:
>
> malformed header from script. Bad header=Please specify hostname.: elog
- make sure your proxy definition in httpd.conf is correct and it uses port 8080
- start elogd with the "-v" flag to see the communication between Apache and elogd
- maybe you might need an "URL = http://<my hostname>/<elog dir>/" in the config
file |
|
Re: Configuration problems, posted by Erich Beyrent on Mon Feb 14 20:39:30 2005
|
> > I am trying to run eLog under Apache 2 on my FreeBSD 5.3 server. I started
> > the daemon with "elogd -n <my hostname> -p 8080" and when I connect to my
> > server on that port, I get a 500 server configuration error. The Apache log
> > contains this:
> >
> > malformed header from script. Bad header=Please specify hostname.: elog
>
> - make sure your proxy definition in httpd.conf is correct and it uses port 8080
> - start elogd with the "-v" flag to see the communication between Apache and elogd
> - maybe you might need an "URL = http://<my hostname>/<elog dir>/" in the config
> file
No luck. I have the proxy definition in my httpd.conf file. I have the URL parameter
in my elogd.cfg file.
Here is the command line I am using to start the daemon:
elogd -v -D -n <myhost> -p 8080 -l <myhost>/cgi-bin/elog/logbooks -c
/usr/local/server/apache/cgi-bin/elog/elogd.cfg
With the -v argument, here are the messages I get in /var/log/messages:
elogd 2.5.7-1 built Feb 14 2005, 09:55:19
Feb 14 14:38:28 onion elogd[34579]: revision 1.558
Feb 14 14:38:28 onion elogd[34579]: Config file :
/usr/local/server/apache/cgi-bin/elog/elogd.cfg
Feb 14 14:38:28 onion elogd[34579]: Resource dir : /usr/local/server/apache/cgi-bin/elog/
Feb 14 14:38:28 onion elogd[34579]: Logbook dir :
/usr/local/server/apache/cgi-bin/elog/logbooks/
Feb 14 14:38:28 onion elogd[34579]: Falling back to default group "elog"
Feb 14 14:38:28 onion elogd[34579]: Group "elog" not found
Feb 14 14:38:28 onion elogd[34579]: Falling back to default group "nogroup"
Feb 14 14:38:28 onion elogd[34579]: Falling back to default user "elog"
Feb 14 14:38:28 onion elogd[34579]: User "elog" not found
Feb 14 14:38:28 onion elogd[34579]: Falling back to default user "nobody"
Feb 14 14:38:28 onion elogd[34579]: Indexing logbook "demo" ...
Feb 14 14:38:28 onion elogd[34579]:
Feb 14 14:38:28 onion elogd[34579]: ID 1, 011108a.log, ofs 0, thead, MD5=
Feb 14 14:38:28 onion elogd[34579]: E4
Feb 14 14:38:28 onion elogd[34579]: 25
Feb 14 14:38:28 onion elogd[34579]: 4C
Feb 14 14:38:28 onion elogd[34579]: B8
Feb 14 14:38:28 onion elogd[34579]: AD
Feb 14 14:38:28 onion elogd[34579]: 4E
Feb 14 14:38:28 onion elogd[34579]: 88
Feb 14 14:38:28 onion elogd[34579]: 68
Feb 14 14:38:28 onion elogd[34579]: 08
Feb 14 14:38:28 onion elogd[34579]: 91
Feb 14 14:38:28 onion elogd[34579]: C9
Feb 14 14:38:28 onion elogd[34579]: 4D
Feb 14 14:38:28 onion elogd[34579]: 1E
Feb 14 14:38:28 onion elogd[34579]: B7
Feb 14 14:38:28 onion elogd[34579]: CB
Feb 14 14:38:28 onion elogd[34579]: C3
Feb 14 14:38:28 onion elogd[34579]:
Feb 14 14:38:28 onion elogd[34579]: After sort:
Feb 14 14:38:28 onion elogd[34579]: ID 1, 011108a.log, ofs 0
Feb 14 14:38:28 onion elogd[34579]: ok
Feb 14 14:38:28 onion elogd[34579]: Server listening on port 8080 ...
I am still getting the exact same error in my Apache log.
Any more ideas?
-Erich- |
|
Re: Configuration problems, posted by Stefan Ritt on Mon Feb 14 20:43:48 2005
|
> No luck. I have the proxy definition in my httpd.conf file. I have the URL parameter
> in my elogd.cfg file.
Can you show me the proxy definition? I hope you don't treat elogd as a CGI script... |