ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69209
|
Wed Sep 2 10:24:58 2020 |
| Florian Feldbauer | florian@ep1.ruhr-uni-bochum.de | Question | Linux | 3.1.3 | Using curl to post new entries |
Hey,
i'm trying to use curl to post new entries to our logbook as described here: https://elog.psi.ch/elogs/Forum/68597.
The Elog is installed via the Deban package on Buster.
I created a test logbook with attributes Author, Type, Category and Subject.
curl -u florian:foobaa -F cmd=Submit -F Author=Florian -F Type=Diary -F Category=General -F Subject="testing curl" -F Text="foo baa" http://localhost:8080/test
<!DOCTYPE html>
<html><head>
<meta name="ROBOTS" content="NOINDEX, NOFOLLOW">
<title>ELOG Login</title>
<link rel="stylesheet" type="text/css" href="elog.css">
<link rel="shortcut icon" href="favicon.ico" />
<link rel="icon" href="favicon.png" type="image/png" />
</head>
<body OnLoad="document.form1.uname.focus();">
<form name=form1 method="POST" action="./" enctype="multipart/form-data">
<input type=hidden name=redir value="">
<table class="login_frame" cellspacing=0 align=center><tr><td class="login_title">Please login</td></tr>
<tr><td class="login_form">
<span class="overlay_wrapper">
<label for="uname" id="uname" class="overlabel">Username</label>
<input type="text" class="login_input" name="uname" value="" title="Username" onInput="document.getElementById('uname').style.display='none';">
</span></td></tr>
<tr><td class="login_form">
<span class="overlay_wrapper">
<label for="upassword" id="upassword" class="overlabel">Password</label>
<input type="password" class="login_input" name="upassword" onInput="document.getElementById('upassword').style.display='none';">
</span></td></tr>
<tr><td align=center class="login_form"><input type=checkbox checked name=remember value=1>
Keep me logged in on this computer
for the next 31 days or until I log out</td></tr>
<tr><td align=center class="login_form">
<a href="?cmd=Forgot">Forgot password?</a></td></tr>
<tr><td align=center class="login_form_bottom"><input type="submit" class="login_submit" value="Submit"></td></tr></table>
<center><a class="bottomlink" title="Goto ELOG home page" href="https://midas.psi.ch/elog/">ELOG V3.1.3-7933898</a></center></form></body></html>
As you can see, curl only prints the login page of the logbook and no new entry has been created. Any suggestions what might go worng here?
Regards,
Florian |
542
|
Fri May 14 06:19:40 2004 |
| nait tauh | nait@no2bl.no-ip.com | Question | Linux | 2.5.2 | Using date and subst date |
I'm trying capture any edit/modified entry with the following, Using the
real date format instead of text string so that I could do a quick filter on it.
Type modified = date
Subst on Edit modified = $date
Problem: It seem that the Subst on Edit always default to 1 Jan 1970 instead
of current date on edit screen.
Could it be $date is a string and not compatible with tape date? or is there
a variable or function to convert $date to date format?
Thanks,
nait |
66341
|
Mon May 4 11:22:40 2009 |
| soren poulsen | soren.poulsen@cern.ch | Question | Linux | 2.7.5-2172 | Using preset text files |
Hi,
I am trying the Preset text option from the documentation: like:
Attributes = Author, Type
Options Type = Network check{1}, System check{2}
{1} Preset text = network.txt
{2} Preset text = system.txt
I have two questions:
1. Where are the preset text files searched from ? I guess I could put them in the logbook (and specify a relative path like in this example) but it appeared only to work when I specifiy an abcolute path. That is even better in my case.
2. How do I specify line feeds in the file ? I tried Linux and Windows new line characters - but I always end up with just one line in my e-log. I would really like a multi-line form.
Soren
|
557
|
Fri Jun 4 22:40:44 2004 |
| Robin Peterson | robin.h.peterson@state.or.us | | | 2.52 | Using select menu option to move multiple logbook entries to another logbook |
I'm trying to configure this thing to be able to filter on a set of
criteria, choose select, choose toggle all, and then choose "Move to
Complete Work Requests".
I've been able to select a specific logbook entry and move it, and I've
been able to filter and select and toggle, but I can't figure out how to
get the Move To option to show up on the main logbook menu....
what am I missing?
robin |
65943
|
Thu Aug 7 10:12:25 2008 |
| T. Ribbrock | emgaron@gmx.net | Question | Linux | 2.7.4-2111 | Using the command line tool to edit |
I intend to create a script that updates one of our elog logbooks based on mails it receives. I was hoping to be able to do this using the "elog" command line tool. Adding a new entry works fine, as does "replying" to an existing entry. The only thing I cannot get to work is editing an existing entry. All entries ahve several attributes and I intend not to use the "message" itself. I tried the following (on the machine this elogd is running on):
- Create a new entry with Attribute1 set to "value":
elog -a 'Attribute1=value' -x -h localhost -l 'LOGBOOK' -p 8080 -u USER PASSWD
This works - the entry gets created and is displayed properly.
NOTE: I found that this does not work if LOGBOOK has any spaces in it - I would get error messages where the logbook was not found.
- Edit this entry to set a second attribute:
elog -e 1 -a 'Attribute2=something' -x -h localhost -l 'LOGBOOK' -p 8080 -u USER PASSWD
The result was: Error transmitting message. Running the same command with -v gives me a whole bunch of text with at the end this message (I've stripped the HTML): "This entry has in meantime been modified by someone else. Submitting it now would overwrite the other modification and is therefore prohibited." However, I know for certain that this entry is not being editied by anyone at that moment, so I'm wondering what I'm doing wrong here...
Also, I have a second, related question: Editing by the ID of the entry seems to be the only way of editing an entry - this makes it a bit difficult for me, as all entries already have a unique ID (which is defined as one of the attributes) that is non-numerical and not sequential. What is the easiest way to retrieve an ID from the command line (basically something like: "What ID has the entry with Attribute1==NAME?")? Is it possible at all? Otherwise, I would not be able to automatically edit the entries, as I don't know which is which... :-} |
2129
|
Tue Feb 13 16:46:54 2007 |
| bob | bobgrang@yahoo.fr | Question | Linux | Windows | | Various attributes and columns “list” |
Re Hi,
Is it possible to put various (and choose them) the attributes in the SAME columns of the “list” ??
Thanks a lot
Bob |
395
|
Tue Jul 15 14:46:50 2003 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | | 2.3.9 | Version 2.3.9 released today |
Version 2.3.9 of elog has been released today. Enhancements are:
- Added options "Use Lock", "Title image"
- New "Email format" specifies what is sent exactly in an email
notification. This may now include also attachments
- "Format <attribute>" lets you assign separate style sheet classes to each
attribute, making the web display more powerful (see this forum,
the "subject" uses a separate formatting). Note that this feature requires
an update of the old "default.css" CSS file, if a elog version prior to
2.3.9 is already installed on a system.
- "Execute new/edit/delete" lets one execute shell commands on the server
side for new, edited or deleted messages. Since this can cause security
problems, a new flag "-x" has been added to the elogd daemon to enable this
feature. It can be used to synchronize the elog database with other
databases, or to send SMS messages to people.
- New "Logging level" option gives enhanced logging capabilities, including
read and write access logging to individual elog entries.
- The elog utility can now edit existing messages, and correctly quotes
messages with "> " on replies.
A few small bugs have been fixed, refer to the ChangeLog for more details. |
2098
|
Tue Nov 28 12:48:47 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | All | 2.6.3 | Version 2.6.3 released today |
Dear ELOG users,
ELOG version 2.6.3 has been released today. It contains all the bug fixes, security fixes and a few new features collected since the last release which was actually almost half a year ago. The changelog contains all the details.
Due to the security fixes it is recommended to upgrade from any version prior to 2.6.3. Please note that the location of all password and log files has been moved from the main elog directory to the logbook directory. This means that after upgrading you have to move your password file manually, otherwise you cannot log in any more. This modification was requested because some ELOG installations (especially ones with top groups) can now have a read-only main directory.
Stefan Ritt |