| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
943
|
Mon Feb 14 18:49:44 2005 |
 | Recai Oktas | roktas@omu.edu.tr | Info | Linux | 2.5.7 | Re: ELOG security vulnerability fixed, IMPORTANT!!!! |
Attention to Debian users;
I've prepared the fixed package and also contacted to Debian Security Team for
an urgent security upload. Since then you may wish to update your package from
the following URL:
http://l10n-turkish.alioth.debian.org/debian/elog_2.5.7+r1558-1_i386.deb
Or you can also make an update via apt-get by adding the below line to your
'/etc/apt/sources.list' file:
deb http://l10n-turkish.alioth.debian.org/debian/ ./
> The second vulnerability had to do with write passwords. If you put a "write
> password = xxx" statement into your config file, it was still possible to
> download the config file with a special hand-written URL, and decode the
> write password, which is usually only base-64 encoded unless you haven't
> compiled elog with the -DHAVE_CRYPT flag.
FYI, Debian package has already been compiled with this flag.
-- Recai Oktas, Maintainer of Debian package |
|
1002
|
Wed Mar 23 05:56:35 2005 |
| Recai Oktas | roktas@omu.edu.tr | Info | Linux | | New Debian package (2.5.8+r1592) -- needs testing |
Hi to all,
I've prepared a new Debian package. This version will probably be the one
which you'll find in Sarge/stable.
There are some invasive changes in this version which call for a serious
test. In accordance with a suggestion, I've changed the configuration
mechanism. For details, please read the NEWS.Debian file attached.
Could the Debian users who follow this forum test it and give some feedback?
You can download the package from the following link:
http://l10n-turkish.alioth.debian.org/debian/elog_2.5.8+r1592-1_i386.deb
Thanks in advance for your participation, |
| Attachment 1: NEWS.Debian
|
elog (2.5.7+r1589-1) unstable; urgency=low
* Starting from this version, /etc/default/elog is installed as part
of the package. Following variables (with default values) can
be used in /etc/default/elog:
# Host where elogd will run.
# HOST=localhost
# Be verbose.
# VERBOSE=yes
# Port where elogd will run.
PORT=8080
# Logbook root directory.
LOGBOOKDIR=/var/lib/elog
# Resource directory (i.e. themes, icons).
RESOURCEDIR=/usr/share/elog
These variables will become the command line options of elogd.
Since command line options always supersede the corresponding
options in config file, the existence of such a file provides a
way to discriminate two roles: System admin (root) and Elog admin.
Elog config file (/etc/elog.conf) now represents the Elog admin's
settings, while /etc/default/elog corresponds to the system admin's
settings. For example, if system admin defines the following line,
the Elog admin's port setting in config file will be ignored and
ELOG will always listen port '80' (note that the compiled-in
default port is '8080'):
PORT=80
One can also change the logbook repository location by using the
same mechanism, e.g. to set the data directory as '/srv/elog' (as
suggested in FHS v2.3) use the following line:
LOGBOOKDIR=/srv/elog
Maintainer scripts should gracefully handle this transition. But
please note that those system admin's settings listed above should
not be used in elog.conf, even though Elog allows it.
-- Recai Oktaş <roktas@omu.edu.tr> Sun, 20 Mar 2005 05:09:57 +0200
|
|
1006
|
Wed Mar 23 16:44:32 2005 |
 | Recai Oktas | roktas@omu.edu.tr | Info | Linux | | Re: New Debian package (2.5.8+r1592) -- needs testing |
> It seems to work nice to me.
> Just another suggestion: I think it would be better to insert a commented out
> example for all allowed parameters in the distributed /etc/default/elog
Thanks for the test. Please note that, /etc/default/elog is partially auto
created during the installation. All options except PIDFILE and CONFFILE are
currently listed (as configured or commented out). If you didn't see these
options (after the update), there must be a problem. Did you mean the lack of
PIDFILE and CONFFILE in the default file? |
|
69669
|
Tue May 9 17:24:37 2023 |
 | Trevor Moore | rogue_boy1@gmail.com | Question | Windows | V3.1.5-fc6679b | Quick Filter "New Entries" Button |
Hello,
I would like to utilize the "New Entries" button on the quick filter bar, but it dates back to 1969. Is there a way to customize this or fix it? |
|
69060
|
Mon Nov 18 16:58:21 2019 |
 | Roger Kalt | roger.kalt@psi.ch | Info | Linux | 3.1.4 | Example scripts how to migrate or combine logbooks |
Attached the shell scripts using awk and sed how I have migrated two separated logbooks into one single and how I re-adjusted certain attributes. |
| Attachment 1: run_modif.sh
|
#!/bin/bash
# KR84, 28.10.2019
# the input files are the exported XML files from ELOG -> Finden
# search in XML for sring between <DATE> and </DATE>
# and replace with: <DATE> and </DATE><When> and </When>
echo "converting export_rf.xml ..."
cat ./export_rf.xml |
sed 's/<Personnel\(.*\)Personnel>/<Author\1Author>/g' |
sed 's/<DATE\(.*\)DATE>/<DATE\1DATE>\n\t\t<When\1When>/g' |
sed 's/<Subject>\(.*\)<\/Subject>/<Title>\1<\/Title><Entry_Type><\/Entry_Type>/g' |
sed '/<Machine>SwissFEL<\/Machine>/ {N;N; s/<Machine>SwissFEL<\/Machine>.*<Domain>OBLA<\/Domain>.*<Section>TRFCB/<Machine>OBLA<\/Machine>\n\t\t<Domain>All<\/Domain>\n\t\t<Section>TRFCB/g}' |
sed 's/<When>Mon, /<When>/g' |
sed 's/<When>Tue, /<When>/g' |
sed 's/<When>Wed, /<When>/g' |
sed 's/<When>Thu, /<When>/g' |
sed 's/<When>Fri, /<When>/g' |
sed 's/<When>Sat, /<When>/g' |
sed 's/<When>Sun, /<When>/g' |
sed '/<When>.*<\/When>/{s/ Jan 20/.01./g}' |
sed '/<When>.*<\/When>/{s/ Feb 20/.02./g}' |
sed '/<When>.*<\/When>/{s/ Mar 20/.03./g}' |
sed '/<When>.*<\/When>/{s/ Apr 20/.04./g}' |
sed '/<When>.*<\/When>/{s/ May 20/.05./g}' |
sed '/<When>.*<\/When>/{s/ Jun 20/.06./g}' |
sed '/<When>.*<\/When>/{s/ Jul 20/.07./g}' |
sed '/<When>.*<\/When>/{s/ Aug 20/.08./g}' |
sed '/<When>.*<\/When>/{s/ Sep 20/.09./g}' |
sed '/<When>.*<\/When>/{s/ Oct 20/.10./g}' |
sed '/<When>.*<\/When>/{s/ Nov 20/.11./g}' |
sed '/<When>.*<\/When>/{s/ Dec 20/.12./g}' |
sed 's/ +0100<\/When>/<\/When>/g' |
sed 's/ +0200<\/When>/<\/When>/g' > export_rf_modified.xml
# sed 's/ Jan 20/.01./g' |
# sed 's/ Feb 20/.02./g' |
# sed 's/ Mar 20/.03./g' |
# sed 's/ Apr 20/.04./g' |
# sed 's/ May 20/.05./g' |
# sed 's/ Jun 20/.06./g' |
# sed 's/ Jul 20/.07./g' |
# sed 's/ Aug 20/.08./g' |
# sed 's/ Sep 20/.09./g' |
# sed 's/ Oct 20/.10./g' |
# sed 's/ Nov 20/.11./g' |
# sed 's/ Dec 20/.12./g' |
# search in XML and add offset to all IDs because they shall not overlap when merged.
echo "converting export_llrf.xml ..."
cat ./export_llrf.xml | sed 's/<Subject>\(.*\)<\/Subject>/<Entry_Type><\/Entry_Type>\n\t\t<Status><\/Status>\n\t\t<Title>\1<\/Title>\n\t\t<Inv_ID><\/Inv_ID>/g' > export_llrf_modified1.xml
cat ./export_llrf_modified1.xml | awk -F'\t\t<MID>|</MID>||' '{ if ($2!="") {print "\t\t<MID>"$2+2016"</MID>"} else { print $1} }' > export_llrf_modified2.xml
cat ./export_llrf_modified2.xml | awk -F'\t\t<REPLY_TO>|</REPLY_TO>||' '{ if ($2!="") {print "\t\t<REPLY_TO>"$2+2016"</REPLY_TO>"} else { print $1} }' > export_llrf_modified3.xml
cat ./export_llrf_modified3.xml | awk -F'\t\t<IN_REPLY_TO>|</IN_REPLY_TO>||' '{ if ($2!="") {print "\t\t<IN_REPLY_TO>"$2+2016"</IN_REPLY_TO>"} else { print $1} }' > export_llrf_modified.xml
rm -rf ./export_llrf_modified1.xml ./export_llrf_modified2.xml ./export_llrf_modified3.xml
cat ./export_llrf_modified.xml |
sed '/<Machine>SwissFEL<\/Machine>/ {N;N; s/<Machine>SwissFEL<\/Machine>.*<Domain>Test Systems<\/Domain>.*<Section>TRFCB/<Machine>OBLA<\/Machine>\n\t\t<Domain>All<\/Domain>\n\t\t<Section>TRFCB/g}' |
sed 's/<When>Mon /<When>/g' |
sed 's/<When>Tue /<When>/g' |
sed 's/<When>Wed /<When>/g' |
sed 's/<When>Thu /<When>/g' |
sed 's/<When>Fri /<When>/g' |
sed 's/<When>Sat /<When>/g' |
sed 's/<When>Sun /<When>/g' |
sed 's/-Jan-/.01./g' |
sed 's/-Feb-/.02./g' |
sed 's/-Mar-/.03./g' |
sed 's/-Apr-/.04./g' |
sed 's/-May-/.05./g' |
sed 's/-Jun-/.06./g' |
sed 's/-Jul-/.07./g' |
sed 's/-Aug-/.08./g' |
sed 's/-Sep-/.09./g' |
sed 's/-Oct-/.10./g' |
sed 's/-Nov-/.11./g' |
sed 's/-Dec-/.12./g' |
sed 's/ +0100<\/When>//g' |
sed 's/ +0200<\/When>//g' |
sed 's/<\/When>/:00<\/When>/g' |
sed 's/<When>-:00<\/When>/<When><\/When>/g' > export_llrf_modified_datetime.xml
echo "export_llrf_modified_datetime.xml need manual edit for empty <When></When>"
|
| Attachment 2: generate_import_llrf_fwd.sh
|
#!/bin/bash
# KR84, 28.10.2019
# generate emtpy auto-fwd text for LLRF for 3100 entries and offset of 2000
echo "generated import_llrf_fwd.xml"
echo "<?xml version=\"1.0\" encoding=\"UTF-8\"?>" > import_llrf_fwd.xml
echo "<ELOG_LIST>" >> import_llrf_fwd.xml
declare -i ID
declare -i IDNEW
for ID in {1..3013}
do
IDNEW=$ID+2016
echo -e "\t<ENTRY>" >> import_llrf_fwd.xml
echo -e "\t\t<MID>${ID}</MID>" >> import_llrf_fwd.xml
echo -e "\t\t<DATE>Mon, 28 Oct 2019 20:00:00 +0200</DATE>" >> import_llrf_fwd.xml
# echo -e "\t\t<DATE>28.10.2019 20:00:00</DATE>" >> import_llrf_fwd.xml
echo -e "\t\t<ATTACHMENT></ATTACHMENT>" >> import_llrf_fwd.xml
echo -e "\t\t<ENCODING>HTML</ENCODING>" >> import_llrf_fwd.xml
echo -e "\t\t<When>28.10.2019 20:00:00</When>" >> import_llrf_fwd.xml
# echo -e "\t\t<When>1572289200</When>" >> import_llrf_fwd.xml
echo -e "\t\t<Author>Kalt Roger (KR84)</Author>" >> import_llrf_fwd.xml
echo -e "\t\t<Machine>SwissFEL</Machine>" >> import_llrf_fwd.xml
echo -e "\t\t<Domain></Domain>" >> import_llrf_fwd.xml
echo -e "\t\t<Section></Section>" >> import_llrf_fwd.xml
echo -e "\t\t<System></System>" >> import_llrf_fwd.xml
echo -e "\t\t<Subsystem></Subsystem>" >> import_llrf_fwd.xml
echo -e "\t\t<Subject>Automatic forward</Subject>" >> import_llrf_fwd.xml
echo -e "\t\t<TEXT><meta http-equiv="refresh" content="0; URL='https://elog-gfa.psi.ch/SwissFEL+RF/${IDNEW}'" /></TEXT>" >> import_llrf_fwd.xml
echo -e "\t</ENTRY>" >> import_llrf_fwd.xml
done
echo "</ELOG_LIST>" >> import_llrf_fwd.xml
|
|
517
|
Wed Mar 31 04:22:57 2004 |
| Robin Peterson | robin.h.peterson@state.or.us | Info | Windows | 2.5.2 | Using Javascript files |
I develop multiple client server apps and web apps deployed on intranets. I
need my users to send me bugs with screenshots attached.
So I'm interested in auto opening a new elog page in an embedded browser and
automatically doing an attachment. I've seen a couple messages about
recently added Javascript hooks (message 465). The message specified a URL
that would fire off javascript(http://localhost/demo/?cmd=New&js=test.js).
Now apparently that wasn't fully working or at least you couldn't bring up
multiple alerts. Has that been fixed, or is it just a problem with alerts?
Can I write a url that has my attributes, plus a short js script that just
adds an attachment?
Anyhow, any info on where this functionality is would be appreciated. I'm
going back to my mgmt for signoff on using this, and if I get it (fairly
high probability), then I'll have a coder start implementing it. :-)
BTW, great tool! Very clean design.
Cheers,
Robin |
|
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 |
|
66222
|
Wed Feb 25 22:01:32 2009 |
 | Robert Risher | robert@gmail.com | Request | Windows | V2.7.5-217 | Text Limit for Subject line |
Is there any way I can limit the ammount of characters in the Subject line?
Thank you, |