| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
149
|
Fri Nov 1 13:39:41 2002 |
 | Willem Koster | W.Koster@rc.rug.nl | Request | | | New ELOG entry |
When I make a new entry I get an email with
subject: New ELOG entry
But when I or someone else changes an entry I also get an email with a
subject: New ELOG entry
I would prefer to see "Changed" , "Edited", or "Updated". This is beyond my
programming capabilities so I enter this request. |
|
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
|
|
1459
|
Thu Oct 13 19:15:48 2005 |
 | Carl Shirey | carl.shirey@pw.utc.com | | Linux | 2.6 | New Accounts |
I hope you can help me Stefan.
The problem that I am having is when someone request a account on elog I received e-mail message to activate there account. I click on the link from my e-mail to activate the account it takes me to the logon page. I log on and then I get a massage that the web does not exist.
What I found out was the elog Damon stops, and I have to restart it and everything work fine.
Here is a copy of me Elog config.
Also can you tell me how you set up the Subtext and the Show new entry buttons on the main page of the elog.
Thank for your help |
|
173
|
Thu Dec 12 14:12:41 2002 |
 | Stefan Ritt | stefan.ritt@psi.ch | Info | | | New "Quick filter" facility added |
Starting from version 2.2.4 which has been released today, the
option "quick filter" has been added. A "quick filter" is a drop down box
on the message display page. By selecting a value from the drop down box,
only messages of that type are displayed. See this forum which uses "Quick
filter = Date, Category".
This new option adresses a couple of installations which require a large
number of logbooks. Instead of using many similar logbooks, the old logbook
name can now be defined as an attribute. All messages get now mixed, but by
defining the logbook attribute as a quick filter, one can display the
messages belonging to the individual logbooks separately with a single
click. |
|
67707
|
Wed Oct 22 19:52:58 2014 |
| Hal Proctor | hproctor2@gmail.com | Question | Windows | 2.9 | Network Questions |
|
Our network team is doing some upgrades and would like the following questions answered if possible.
1: Is the application able to communicate with a Domain controller running Windows Server 2012 R2?
And....
2: Is the application able to function in a Windows 2008 R2 domain and forest functional level?
Thanks for your help,
Hal |
|
69673
|
Wed Jun 14 21:19:48 2023 |
| Leonardo Tacconi | leonardo.tacconi@unifi.it | Question | Windows | 3.1.3 | Nested commands in logbook |
Hi everybody,
I am trying to setup my personal ELog, defining attributes and stuff like that. I just tried to make some nested commands but I really could not achieve that.
The idea is something like this:
Attributes = Author
Options Author = Tizio{1}, Caio{2}, Sempronio{3}
{1} Attributes = Author, Project
{1} Options Project = Proj1{a}, Proj2{b}, Proj3{c}
{a} Attributes = Author, Project, Year
{a} Options Year = 2017, 2019
Anyway, when I select Proj1 nothing really happens. So, is there any way to set up nested commands like in the reported example?
Many thanks in advance!
P.S. Is there any documentation in which are reported all the possible commands that can be used? |
|
Draft
|
Wed Jun 24 19:22:10 2015 |
| Mario Gaertner | m.gaertner@estrel.com | Question | Windows | latest | Need to move ELOG to other host |
Hi there,
our host running ELOG crashed. I installed ELOG at another host with copying backup files / folders to new installation. New installation looks fine and seems to be working. But one big problem occurs I only can see some of former existing logbooks. Are there any suggestions how to build an new ELOG with old data?
Many thanks Mario |
|
68031
|
Wed Jun 24 19:27:49 2015 |
 | Mario Gaertner | m.gaertner@estrel.com | Question | Windows | latest | Need to move ELOG to other host |
Hi there,
our host running ELOG crashed. I installed ELOG at another host with copying backup files / folders to new installation. New installation looks fine and seems to be working. But one big problem occurs I only can see some of former existing logbooks. Are there any suggestions how to build an new ELOG with old data?
Many thanks Mario |