Re: upgrading, posted by Stefan Ritt on Mon Nov 25 09:05:06 2002
|
Ooops, I just realized that the Windows 2.2.3 distribution contained the old
(2.2.2) executable for elogd.exe. I apologize for that. I have updated the
elog223.exe distribution just now, so please download it again in order to
get the new file.
- Stefan |
Re: upgrading, posted by tony summerfelt on Wed Nov 27 07:22:07 2002
|
> Ooops, I just realized that the Windows 2.2.3 distribution contained the old
> (2.2.2) executable for elogd.exe. I apologize for that. I have updated the
that's ok. i just it was driving me nuts there for a while...everything is fine now...
i've tried other web based msg boards, but i keep coming back to elog... |
New directory scheme from version 2.2.5 on, posted by Stefan Ritt on Tue Jan 7 17:48:25 2003
|
Starting from version 2.2.5 on, an new directory scheme has been
implemented. The idea is to separate the config file from the theme/icon
and the logbook directories. This can now be achieved by specifying the
configuration file via the "-c" flag and the directories with the "-d" flag
for the logbook root and the "resource directory" with the "-s" flag.
Alternatively, the resouce and logbook directories can be specified in the
configuration file with
Resource dir = ...
Logbook dir = ...
The old "Data dir" statement is still possible but deprecated. Instead, the
statement "Subdir = ..." should be used which is taken relative to
the "Logbook dir". If no "Subdir" is given, the logbook name itself is used
as the subdir. For this demo logbook I use now:
[global]
...
Resource dir = /usr/local/elogdemo
Logbook dir = /usr/local/elogdemo/logbooks
and no "Data dir" statements any more. The logbooks "Linux", "Database"
and "Forum" are then located at
/usr/local/elogdemo/logbooks/Linux
/usr/local/elogdemo/logbooks/Database
/usr/local/elogdemo/logbooks/Forum
respectively. The help, theme and icon files are located at their old
position ("themes" is automatically added to the "resource dir" as it was
before). |
"User" and "Group" statements changed from Version 2.2.5, posted by Stefan Ritt on Tue Jan 7 17:49:40 2003
|
From Version 2.2.5 on, the configuration file entries
User = ...
Group = ...
have been changed to
Usr = ...
Grp = ...
in order not to conflict with the new "Group = ..." option which is used by
hierarchical logbooks. |
New Version, posted by Nick on Tue Feb 18 08:07:10 2003
|
I noticed the site has been updated as far as the documentation for 2.3.1,
however the latest version in the downloads section is 2.3.0, any other
places where I can get 2.3.1
Cheers |
Re: New Version, posted by Stefan Ritt on Tue Feb 18 09:21:34 2003
|
> I noticed the site has been updated as far as the documentation for 2.3.1,
> however the latest version in the downloads section is 2.3.0, any other
> places where I can get 2.3.1
>
> Cheers
Patience, patience! 2.3.1 is currently kind of in "beta" version, but will be
released this week. Not that you can always get the latest snapshot from the
CVS tree at
http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c
- Stefan |
Participation on development of ELOG, posted by Tomas Rudolf on Wed Feb 19 09:26:04 2003
|
Stefan,
We are interested in using your ELOG (which we consider to be a wonderful
application) even more. We would like to make a few adaptations in your
source code, above all to add some functionality that we are missing.
I was wondering if there is a way we could coordinate the development
together. For instance, would it be of your interest to receive the code
adaptations we do and implement it in your future releases?
To be more specific, for the moment we are really interested in
implementing the SHELL script execution on the server (I noticed it is in
your wishlist).
Best regards,
Tomas Rudolf
Micro Belgium Application |
Re: Participation on development of ELOG, posted by Stefan Ritt on Wed Feb 19 09:37:30 2003
|
> We are interested in using your ELOG (which we consider to be a wonderful
> application) even more. We would like to make a few adaptations in your
> source code, above all to add some functionality that we are missing.
>
> I was wondering if there is a way we could coordinate the development
> together. For instance, would it be of your interest to receive the code
> adaptations we do and implement it in your future releases?
Sure, I'm very interested in those and ready to merge it into the main
development tree.
- Stefan |