ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
1381
|
Fri Aug 5 10:00:00 2005 |
| Kees Bol | kees.bol@wur.nl | Info | Linux | 2.6.0 | Re: "full" only changes color |
Stefan Ritt wrote: |
Kees Bol wrote: | I thougt when choosing the full-view the text would appear along with the other attributes. |
That's how it is supposed to be. I tried your config file, added three entries, and got the behaviour documented in the attached images. To me everything looks fine. |
Stefan, the output you see I expected to see with my logbook too but I don't.
I will upgrade to V2.6.0-beta3, perhaps that solves the problem. |
1382
|
Fri Aug 5 10:51:27 2005 |
| Kees Bol | kees.bol@wur.nl | Info | Linux | 2.6.0 | Re: "full" only changes color |
Stefan Ritt wrote: |
Kees Bol wrote: | I thougt when choosing the full-view the text would appear along with the other attributes. |
That's how it is supposed to be. I tried your config file, added three entries, and got the behaviour documented in the attached images. To me everything looks fine. |
Stefan, I installed V2.6.0-beta3 and there is a (unwanted) difference. The Text field now appears in the summary-view despite the config specifies:
List Display = ID, Logdate, Author, Book, Chapter, Type, Subject
so in my opinion the text-field should not show up here.
Now the full-view indeed shows the complete texts.
I also attached the complete config-file because perhaps I overlook some details.
Another point: there was some discussion about v2.6.0-beta3 being slow.
I have v2.6.0-beta and v2.6.0-beta3 running side by side on the same server and notice also a big difference in speed, beta3 being much slower. |
1383
|
Fri Aug 5 10:54:49 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | Linux | 2.6.0 | Re: "full" only changes color |
Kees Bol wrote: | Stefan, I installed V2.6.0-beta3 and there is a (unwanted) difference. The Text field now appears in the summary-view despite the config specifies:
List Display = ID, Logdate, Author, Book, Chapter, Type, Subject
so in my opinion the text-field should not show up here. |
If you do not want text display in the summary view, add
Summary lines = 0
into your config file.
Kees Bol wrote: | Another point: there was some discussion about v2.6.0-beta3 being slow.
I have v2.6.0-beta and v2.6.0-beta3 running side by side on the same server and notice also a big difference in speed, beta3 being much slower. |
This is still a mystery to me, since on all machines I try the speed is fine. I'm still waiting for some debugging analysis from users which have this problem. If I cannot reproduce it, I cannot fix it. |
1387
|
Fri Aug 5 14:30:52 2005 |
| Kees Bol | kees.bol@wur.nl | Info | Linux | 2.6.0 | Re: "full" only changes color |
Stefan Ritt wrote: |
Kees Bol wrote: | Stefan, I installed V2.6.0-beta3 and there is a (unwanted) difference. The Text field now appears in the summary-view despite the config specifies:
List Display = ID, Logdate, Author, Book, Chapter, Type, Subject
so in my opinion the text-field should not show up here. |
If you do not want text display in the summary view, add
Summary lines = 0
into your config file.
Kees Bol wrote: | Another point: there was some discussion about v2.6.0-beta3 being slow.
I have v2.6.0-beta and v2.6.0-beta3 running side by side on the same server and notice also a big difference in speed, beta3 being much slower. |
This is still a mystery to me, since on all machines I try the speed is fine. I'm still waiting for some debugging analysis from users which have this problem. If I cannot reproduce it, I cannot fix it. |
After upgrading to v2.6.0-beta4 everything works fine now.
Thanks for your help |
1420
|
Fri Sep 23 17:27:40 2005 |
| ScottK | snkgak@yahoo.com | | Linux | 2.6.0 | elog fails to connect with "cannot get host name: Success" message |
I can't seem to connect using elog: elog -h <myhost>:8080 -v -l Servers -a "Type=Routine" -a "Author=ScottK" -m ~/test.txt it run fine through the web interface on http://<myhost>:8080/Servers I have URL = http://<myhost>:8080 in my elogd.cfg Any clues what I'm doing wrong? Thanks for any help. ScottK |
1428
|
Wed Oct 5 13:24:52 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | | Linux | 2.6.0 | Re: elog fails to connect with "cannot get host name: Success" message |
ScottK wrote: | I can't seem to connect using elog:
elog -h <myhost>:8080 -v -l Servers -a "Type=Routine" -a "Author=ScottK" -m ~/test.txt
|
Maybe a
elog -h <myhost> -p 8080 -v -l .... ??? |
1448
|
Tue Oct 11 15:09:42 2005 |
| ScottK | snkgak@yahoo.com | Question | Linux | 2.6.0 | Re: elog fails to connect with "cannot get host name: Success" message |
Stefan Ritt wrote: |
ScottK wrote: | I can't seem to connect using elog:
elog -h <myhost>:8080 -v -l Servers -a "Type=Routine" -a "Author=ScottK" -m ~/test.txt
|
Maybe a
elog -h <myhost> -p 8080 -v -l .... ??? |
Oops - amazing when I read the syntax correctly -- it works! Thanks for taking the time to reply to a "dumb, RTFD" question, Stefan. Thank you for making a great program!
ScottK |
1465
|
Sat Oct 15 16:50:25 2005 |
| Johan Nyberg | johan.nyberg@tsl.uu.se | Question | Linux | 2.6.0 | How to connect to an ELOG server running behind apache+ssl using the elog command line program? |
Hi,
I need to post a large number of "old" messages to one of my logbooks and I am trying to modify the script doelog (see http://midas.psi.ch/elogs/Contributions/10) to suit my needs. I am using apache + ssl for secure logins to my ELOG server. The doelog script uses the elog utility program, which is useful for posting ELOG messages from scripts or from the command line. My problem is that I cannot talk to my ELOG server with elog.
Here is what happens:
-------------------------------------------------------------------------------------------------
$ elog -v -h my.server.org -p 443 -l mylogbook -a Category=Other-u myusername mypasswd testmsg
Successfully connected to host my.server.org, port 443
Request sent to host:
POST /mylogbook/ HTTP/1.0
Content-Type: multipart/form-data; boundary=---------------------------1028A8C27FFD1021AAB342B
Host: my.host.org
User-Agent: ELOG
Content-Length: 811
Content sent to host.
Response received:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>400 Bad Request</title>
</head><body>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br />
Reason: You're speaking plain HTTP to an SSL-enabled server port.<br />
Instead use the HTTPS scheme to access this URL, please.<br />
<blockquote>Hint: <a href="https://my.server.org/"><b>https://my.server.org/</b></a></blockquote></p>
<hr>
<address>Apache Server at <a href="webmaster@my.server.org">my.server.org</a> Port 443</address>
</body></html>
Error transmitting message
-------------------------------------------------------------------------------------------------------
Access to the logbook works perfectly if I use a web browser. If I can find out how to use the elog command line program to connect to my ELOG server running behind apache+ssl, I think I can change the doelog script to suit my needs. Any help is appreciated.
Johan |