ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
382
|
Mon Jun 30 05:15:14 2003 |
| Joseph Giaime | giaime@phys.lsu.edu | Bug fix | Mac OSX | 2.3.8 | Re: runtime error under Mac OS X 10.2 |
Sridhar & Recai,
Thanks to both of you for the rapid and effective advice. Fixing the limit corrected my problem.
I think I last got tripped up this way 10 years ago...
I suppose that the advice to increase Mac OS X's default stacksize limit might make a fine entry
in the FAQ or README file.
Thanks again,
Joe |
461
|
Thu Jan 29 00:24:44 2004 |
| Joseph Giaime | giaime@phys.lsu.edu | Bug report | Mac OSX | 2.3.9 | Strange timezone in email sent with Postfix |
Hi all,
I'm having trouble getting a sensible timezone to be attached to e-mail that
gets sent out when messages are posted. I'm using Postfix, not sendmail
(Mac OS X Server uses this beginning with version 10.3). In this set-up,
the 'sendmail' program is a front-end for Postfix, not the real thing. I
suspect that there are subtle differences that cause this problem.
Instead of something like "Date: Wed, 28 Jan 2004 14:46:16 -0600", the
"-0600" is replaced by a large number that doesn't correspond with anything
I can figure out. This is the sort of thing that does no real harm, but the
notebook users keep complaining
Any thoughts or suggestions would be appreciated. -Joe
Here is what gets mailed when a messages is posted:
Return-Path:
Received: from ligo.phys.lsu.edu ([unix socket])
by ligo.phys.lsu.edu (Cyrus v2.1.13) with LMTP; Wed, 28 Jan 2004 16:27:03 -0600
X-Sieve: CMU Sieve 2.2
Received: from ligo.phys.lsu.edu (ligo.phys.lsu.edu [130.39.181.231])
by ligo.phys.lsu.edu (Postfix) with SMTP
id 5E12A788D1; Wed, 28 Jan 2004 16:27:03 -0600 (CST)
To: ELOG@ligo.phys.lsu.edu, user@ligo.phys.lsu.edu
From: elog@ligo.phys.lsu.edu
Subject: New playground elog entry
X-Mailer: Elog, Version 2.3.9
X-Elog-URL: http://ligo.phys.lsu.edu:8080/playground/13
X-Elog-submit-type: web|elog
Date: Wed, 28 Jan 2004 22:27:03 +52182819
Content-Type: TEXT/PLAIN; charset=US-ASCII
Message-Id: <20040128222703.5E12A788D1@ligo.phys.lsu.edu>
A new entry has been submitted on ligo.phys.lsu.edu
Logbook : playground
Author : Joseph Giaime
Type : Other
Category : Other
Subject : yet another test
Logbook URL : http://ligo.phys.lsu.edu:8080/playground/13
|
67336
|
Sun Sep 16 18:40:06 2012 |
| Josef Uher | josef.uher@gmail.com | Question | All | 2.9.2 | HTML editor |
Hi All,
maybe I missed something in the configuration, but how do I get this nice editor for HTML like the one available on this forum?
Thanks a lot for advice. |
67337
|
Sun Sep 16 21:14:12 2012 |
| Josef Uher | josef.uher@gmail.com | Bug report | Mac OSX | 2.9.2 | Crash with long image names |
Hi All,
I found that elog crashes if I try to upload an image with long name. It actually uploads the file after the crash. It crashes also if in the full view with attachments visible. If I shorten the name all is fine.
The crash report screenshot is attached. It looks like a too small buffer (?).

|
Attachment 1: Screen_Shot.png
|
|
67340
|
Mon Sep 17 15:14:46 2012 |
| Josef Uher | josef.uher@gmail.com | Question | All | 2.9.2 | Re: HTML editor |
Andreas Luedeke wrote: |
Josef Uher wrote: |
[...] maybe I missed something in the configuration, but how do I get this nice editor for HTML like the one available on this forum?[...]
|
The fckeditor is already installed with the elog package. All you need to do is to enable HTML in ELOG and Javascript in your browser.
The ELOG command "Allowed encoding = 7" gives you the same encoding choices as in this forum.
|
Hi Andreas, thank you for your reply. I have already found out that the problem on Mac was that I moved the cfg file to some other folder which did not contain the resources and scripts. I used the "-s" switch and now it works nicely. However, now I try to do the same thing on Windows and even the "-s" switch does not help (the default encodings etc. are set in the cfg file). I compiled the elog on Mac, but I used the installation package on Windows. |
69180
|
Thu Jul 30 17:03:12 2020 |
| Jose Caballero | jcaballero.hep@gmail.com | Question | Linux | 3.1.4 | testing the client: unclear it worked |
Hello,
I just gave it a quick try to the command line client, to see if I can use it to access our institution service.
[root@host ~]# cd /tmp/
[root@host ~]# mkdir elog
[root@host ~]# cd elog
[root@host ~]# wget https://elog.psi.ch/elog/download/RPMS/elog-3.1.4-2.el7.x86_64.rpm
[root@host ~]# rpm2cpio elog-3.1.4-2.el7.x86_64.rpm | cpio -idmv
[root@host ~]# cd usr/local/bin/
[root@host ~]# ./elog --help
[root@host ~]# ./elog -h <hostname> -l <logbook> -u <myusername> <mypassword> -w last
"Message successfully transmitted, ID=-1"
Is that the expected output? I was expecting to see info about the latest message in the server.
Cheers,
Jose |
69218
|
Mon Sep 14 15:40:02 2020 |
| Jose Caballero | jcaballero.hep@gmail.com | Question | Linux | 3.1.4 | Re: testing the client: unclear it worked |
Sorry for the late reply. I didn't get email notification about an answer to my question :)
Actually, I just wrote <hostname> and so on for privacy. In my attempt, they have real values.
And yet, I got as result: "Message successfully transmitted, ID=-1".
Follow up question: do I really need to install everything even though I only want the client? Or is there somewhere a package just with the client code?
Thanks
Jose
Stefan Ritt wrote: |
The <hostname> you have to actually replace with your real host name. Same for logbook, username and password.
On my local test system I get (actual password hidden here with "...")
~$ elog -h localhost -p 8080 -l demo -u stefan ... -a Authort=SR -a Subject=test test
Message successfully transmitted, ID=5
~$
Jose Caballero wrote: |
Hello,
I just gave it a quick try to the command line client, to see if I can use it to access our institution service.
[root@host ~]# cd /tmp/
[root@host ~]# mkdir elog
[root@host ~]# cd elog
[root@host ~]# wget https://elog.psi.ch/elog/download/RPMS/elog-3.1.4-2.el7.x86_64.rpm
[root@host ~]# rpm2cpio elog-3.1.4-2.el7.x86_64.rpm | cpio -idmv
[root@host ~]# cd usr/local/bin/
[root@host ~]# ./elog --help
[root@host ~]# ./elog -h <hostname> -l <logbook> -u <myusername> <mypassword> -w last
"Message successfully transmitted, ID=-1"
Is that the expected output? I was expecting to see info about the latest message in the server.
Cheers,
Jose
|
|
|
69426
|
Wed Dec 1 12:37:57 2021 |
| Jose Caballero | jcaballero.hep@gmail.com | Question | Linux | 3.1.4 | Unclear how to use the command line tool /usr/bin/elog |
Hello,
I am trying first time to use the tool /usr/bin/elog. From the documentation is not clear to if everything must be in quotes or not, if every attribute requires -a.
Here is how my attempt looks like (changing actual data by fake one):
/usr/bin/elog -h elog-1.matrix.com -l LogBook -u jcaballero mypassword -a Team='Team Name Here' Category='Category Here' -a 'Affected service'='Name of affected service here' -a Criticality=Normal -a 'Oncall Documentation'='No modifications required' -a Subject='here is the subject line' 'here is the text'
I just get "Error transmitting message".
Attributes Team and Category are of checkbox type. Attributes Criticality and Oncall Documentation are of radio type.
What is wrong with my command attempt?
Thanks a lot in advance.
Cheers,
Jose
|