Re: Support for modern Linux, posted by Louis de Leseleuc on Wed Nov 7 20:48:03 2012
|
| Vinícius Ferrão wrote: |
|
Hello folks,
Can we have a better support under modern Linux distributions?
I'm trying to install elog in our webserver and it's becoming a boring task. First of all theres only RPM packages. And we really don't like the Red Hat method, so we use Debian Servers. More package mainteners would be nice.
The software appears to be working correctly, but there are some bugs (or perhaps missing dependencies?); the init script put in /etc/rc.d/init.d is broken under Debian:
First of all because it's in /etc/rc.d.
The second problem is in this line:
# Source function library.
#. /etc/rc.d/init.d/functions
The file doesn't even exists.
|
The Debian init script contributed here has been working quite well for me for the last few Ubuntu versions. Unless you edit it, it sets the elog base directory to /etc so that's where you have to put your themes dir, resources, .conf file, scripts, logbooks, etc. I use symlinks to actually store my logbooks elsewhere.
I would also vote for a sane deb package. Right now, when I upgrade ELOG, I don't even run make install, I just copy the compiled binaries to their respective directories (/usr/bin or /usr/sbin). The rest stays the same. |
|
Re: Support for modern Linux, posted by David Pilgram on Wed Nov 7 22:29:11 2012
|
| Louis de Leseleuc wrote: |
|
| Vinícius Ferrão wrote: |
|
Hello folks,
Can we have a better support under modern Linux distributions?
I'm trying to install elog in our webserver and it's becoming a boring task. First of all theres only RPM packages. And we really don't like the Red Hat method, so we use Debian Servers. More package mainteners would be nice.
The software appears to be working correctly, but there are some bugs (or perhaps missing dependencies?); the init script put in /etc/rc.d/init.d is broken under Debian:
First of all because it's in /etc/rc.d.
The second problem is in this line:
# Source function library.
#. /etc/rc.d/init.d/functions
The file doesn't even exists.
|
The Debian init script contributed here has been working quite well for me for the last few Ubuntu versions. Unless you edit it, it sets the elog base directory to /etc so that's where you have to put your themes dir, resources, .conf file, scripts, logbooks, etc. I use symlinks to actually store my logbooks elsewhere.
I would also vote for a sane deb package. Right now, when I upgrade ELOG, I don't even run make install, I just copy the compiled binaries to their respective directories (/usr/bin or /usr/sbin). The rest stays the same.
|
Hi Louis,
I'm a little surprised by your comment that you use symlinks 'to store your logbooks elsewhere'.
I start the daemon with
/usr/local/sbin/elogd -p 8080 -c /home/logbooks/elogd.cfg -d /home/logbooks
so that both my logbooks *and* the config file are both based on my preferred location, which is a subdirectory of /home. No symlinks OK, themes are elsewhere, but for backup purposes, that's a rather lesser issue.
I have no idea why the default logbook location is /usr/local/elog/logbooks which does not strike me as a sensible location (at least on Slackware). Maybe such an odd location was to force users to choose a better location...(the -d switch).
To all:
I use Slackware (currently 13, I hear there are some issues with 14 for programs I wish use), and I compile from the sources. Usually from random svn versions as a general pain-in-the-neck for Stefan. I've never had to make a [Slackware] package for distribution - I have issued patches and/or source distribution, depending on your point of view. If someone can provide the advice, I'd certainly try and do a Slackware distribution, but I do have Real Work to do as well, so it may not be done immediately. I think Ubuntu is fairly close to Slackware, not sure about Debian, which I *thought* was close to Red Hat.
Now I *do* understand what some of the other contributors to this thread are doing, as I do something similar for other programs that are now unmaintained and no longer compile with GCC4 or earlier. The email program I use is a ten-year-old binary & libraries I compiled under Slackware 7 (if not, 4), and I copy the relivent binaries, libraries and dependances across when I upgrade the o/s. Yes, one day it will fall down. Three other programs I regularly use are similarly now 'legacy'. My 'C' coding isn't up to the major changes apparently needed to allow them to compile again with a modern compiler.
|
|
Re: Support for modern Linux, posted by Achim Dreyer on Sat Apr 27 14:09:13 2013
|
| Vinícius Ferrão wrote: |
Hello folks,
Can we have a better support under modern Linux distributions?
I'm trying to install elog in our webserver and it's becoming a boring task. First of all theres only RPM packages. And we really don't like the Red Hat method, so we use Debian Servers. More package mainteners would be nice.
The software appears to be working correctly, but there are some bugs (or perhaps missing dependencies?); the init script put in /etc/rc.d/init.d is broken under Debian:
First of all because it's in /etc/rc.d.
The second problem is in this line:
# Source function library.
#. /etc/rc.d/init.d/functions
The file doesn't even exists.
The third problem is the echo_success; echo_failure commands that doesn't even exist. As I can see it's definitions are sourced in the functions file that doesn't exist.
After removing this missing commands or files from the init.d; I can call elogd script and start the daemon under root. Appears to be working...
And last but not least; there's a way to standardize the init script to run in other Linux distros, so we can put it to start automatically at boot time?
Many thanks in advance,
Vinícius Ferrão
PS: I'm not asking to support any creepy distros, but to support the .deb package format and system style.
|
/etc/rc.d/init.d/functions is part of the initscripts.rpm - so only usable on RedHat/CentOS..
Can someone also update https://midas.psi.ch/elog/download.html ? It was last updated in 2001 and the download directory contains a debian package that was last updated 2004. If debian is not supported in a current version that bit should be removed from the page.
Kind regards,
Achim
|
Re: Summary view: View only most recent entry for all values of a given attribute?, posted by Stefan Ritt on Thu May 17 14:02:39 2007 
|
| Dennis Seitz wrote: | | I would like to filter the summary view so it only shows me the most recent entry for every value in the serial number attribute. This would be very useful for quickly viewing the present status and location of every assembly, for example. |
I don't know if that is what you want, but have you tried clicking on the column headings in the summary view to sort the table according to that attribute:
 |
|
Re: Summary view: View only most recent entry for all values of a given attribute?, posted by Dennis Seitz on Fri May 18 02:15:41 2007
|
| Stefan Ritt wrote: |
| Dennis Seitz wrote: | | I would like to filter the summary view so it only shows me the most recent entry for every value in the serial number attribute. This would be very useful for quickly viewing the present status and location of every assembly, for example. |
I don't know if that is what you want, but have you tried clicking on the column headings in the summary view to sort the table according to that attribute:
|
Rather than simply sorting, I would like to actually reduce the number of entries listed to show only the most recent entry for each serial number. In this way, I can see at a glance what the present status of each serial number is. This is similar to Quick Filters but would be a "Most Recent" filter that could be applied conditionally, for example: "Most Recent" -> "By Serial".
Here is the display now:
Here is what I'd like to have the option to view (I used a graphic editor to fake it):
It would also be nice to have the option to then sort the resultant view, for example, to group together all serial numbers that have the same status.
Is this a little clearer? It's just a suggestion - this is not terribly important, but if it were possible I think it would be useful.
Thanks! |
|
Re: Summary view: View only most recent entry for all values of a given attribute?, posted by Stefan Ritt on Fri May 18 08:04:38 2007
|
Ok, now I understand. Well, your request is very special for your case. Usually I implement things only if several independent people ask for it. What you can try is to save your logbook in CSV format, import it into Excel or another spreadsheet program, and achieve the filtering there.
Best regards,
Stefan |
|
Re: Summary view: View only most recent entry for all values of a given attribute?, posted by Dennis Seitz on Fri May 18 16:07:31 2007
|
| Stefan Ritt wrote: | Ok, now I understand. Well, your request is very special for your case. Usually I implement things only if several independent people ask for it. What you can try is to save your logbook in CSV format, import it into Excel or another spreadsheet program, and achieve the filtering there.
Best regards,
Stefan |
OK, I've done that before and it works fine. I'd rather be able to do it in Elog but I understand if it's not worth the effort. It never hurts to ask!
Cheers,
Dennis |
|
Re: Summary view - Umlauts, posted by Stefan Ritt on Thu Nov 29 15:04:49 2007
|
| Uwe wrote: |
|
Hello,
when using the summary view, the text field displays umlauts as HTML-charachters, for e. g. diesbezüglich.
Is there a chance that also this view displays umlauts as ä, ü, ö?
Thank you!
Uwe
|
I fixed this in svn revision #1971. The fix will be contained in the next release. You can test it already in the demo logbook. |
|