Re: How to property install?, posted by Andreas Luedeke on Mon Dec 16 11:16:33 2013
|
| Ryan Blakeslee wrote: |
|
Hello,
I have followed the very simple steps on the Download page for checking out and compiling from GIT. That works perfect and there is no issue.
The problem I have is-- it is not clear to me where to put the 'elog' dir that I have after I 'make' and 'make install'. Or, is there an installer script afterwards that I run? I'm installing on Debian 7 and trying to upgrade from 2.5.2 (which was installed using apt-get.)
|
Hi Ryan,
as far as I remember the Debian package is not supported any more. The "make install" assumes Red-hat style installation directories (you can see it in elog/Makefile, all the installation directories are installed there).
I have no idea where Debian is supposed to install the binaries. But you should be able to use GNU "locate" to find the old files: "locate elog" and "locate elogd" should tell you where the old binaries had been installed.
Kind Regards, Andreas
⇄
English (auto-detected) » English
|
|
Re: How to property install?, posted by Ryan Blakeslee on Tue Dec 17 21:00:33 2013
|
| Andreas Luedeke wrote: |
|
| Ryan Blakeslee wrote: |
|
Hello,
I have followed the very simple steps on the Download page for checking out and compiling from GIT. That works perfect and there is no issue.
The problem I have is-- it is not clear to me where to put the 'elog' dir that I have after I 'make' and 'make install'. Or, is there an installer script afterwards that I run? I'm installing on Debian 7 and trying to upgrade from 2.5.2 (which was installed using apt-get.)
|
Hi Ryan,
as far as I remember the Debian package is not supported any more. The "make install" assumes Red-hat style installation directories (you can see it in elog/Makefile, all the installation directories are installed there).
I have no idea where Debian is supposed to install the binaries. But you should be able to use GNU "locate" to find the old files: "locate elog" and "locate elogd" should tell you where the old binaries had been installed.
Kind Regards, Andreas
⇄
English (auto-detected) » English
|
Hi Andreas,
Thank you so much for the reply and info; Much appreciated! I turned up a CentOS 6 VM and the installation, using the RPM's provided on the 'downloads' page here, worked perfectly and was very straight-forward and easy.
The D/L page includes the Debian repositories (which is how I installed on Debian in the first place) but only installed v2.5.2. I needed to get to the newest version (ELOG V2.9.2-2455) so I can setup authentication and SSH. (And also so that when I am reading the manuals and documentation online, provided at this site, that is makes sense to the version I am running.) I also want to add that it seems that I am able to bring over my older 2.5.2 logbooks to 2.9.2 without any problem. To do that, I just rsync'd the logbooks from old to new. They seem to work just fine under the newest version.
I'm good to go. Anyone looking for an easy deployment of ELOG, especially in a production environment, I can attest that the RPM's provided here make it very simple to deploy on Cent6.
Thanks! |
|
Re: How to prevent file path leaks on a 404 page, posted by Stefan Ritt on Tue Aug 4 13:44:01 2020
|
I removed the version info from the 404 error, but you have to recompile elogd from sources. The fix will be included in the next RPM, but that can usually take a few weeks.
| Rich Loring wrote: |
|
Hello,
We used the Elog RPM binary installation method to install Elog. Our security scanners are complaining that Elog discloses the version information when you hit a missing page (404 error). How can I hide this version info? Is there a snippet of code somewhere that I can comment out?
Any help is appreciated.
-Rich
|
|
|
Re: How to prevent file path leaks on a 404 page, posted by Stefan Ritt on Wed Aug 26 20:44:38 2020
|
A new RPM has been released at https://elog.psi.ch/elog/download/RPMS/elog-3.1.4-2.el7.x86_64.rpm containing that fix.
| Stefan Ritt wrote: |
|
I removed the version info from the 404 error, but you have to recompile elogd from sources. The fix will be included in the next RPM, but that can usually take a few weeks.
| Rich Loring wrote: |
|
Hello,
We used the Elog RPM binary installation method to install Elog. Our security scanners are complaining that Elog discloses the version information when you hit a missing page (404 error). How can I hide this version info? Is there a snippet of code somewhere that I can comment out?
Any help is appreciated.
-Rich
|
|
|
|
Re: How to pre-fill an attribute that was added later, posted by Stefan Ritt on Tue May 21 12:08:17 2019
|
Find all entries which have this attribute empty. Then click on Select, then select all, then click on Edit, then change all values. There might be a limit how many entries you can select in one go, so you might have to do it in bunches.
| Antonio Bulgheroni wrote: |
|
Dear all,
I have a question about my logbook. I have recently added a new attribute to my logbook and I would like to prefill all previous entries with a fixed value for this field. Is it possible?
Thanks for your help and best regards,
toto
|
|
|
Re: How to pre-fill an attribute that was added later, posted by Antonio Bulgheroni on Tue May 21 12:51:08 2019
|
Thanks, it worked great!
| Stefan Ritt wrote: |
|
Find all entries which have this attribute empty. Then click on Select, then select all, then click on Edit, then change all values. There might be a limit how many entries you can select in one go, so you might have to do it in bunches.
| Antonio Bulgheroni wrote: |
|
Dear all,
I have a question about my logbook. I have recently added a new attribute to my logbook and I would like to prefill all previous entries with a fixed value for this field. Is it possible?
Thanks for your help and best regards,
toto
|
|
|
|
Re: How to pass attachment names to an Execute line?, posted by Stefan Ritt on Thu Oct 19 19:45:35 2006
|
| Alexandre Lindote wrote: | Hi,
I'm trying to pass the name of an attachment in a "Execute new " line, but I can't seem to get the correct syntax...
I've tried:
Execute new = echo "New document with reference $Internal Ref with the name $attachements " >> /home/zeplin3/lixo.log
Execute new = echo "New document with reference $Internal Ref with the name $attachements1 " >> /home/zeplin3/lixo.log
Execute new = echo "New document with reference $Internal Ref with the name $1 " >> /home/zeplin3/lixo.log
but nothing seem to work. If I remove the $attachments bit the output is correct...
Any suggestions? |
Sorry there was a type in the documentation. You should write
$attachments
and not
$attachements
then it will work. |
|
Re: How to overide the Date attribute?, posted by Stefan Ritt on Wed Nov 24 12:12:37 2010
|
| Adam Blandford wrote: |
| Hi I have a logbook where I want to override the default Date attribute. I would like to set it by default to the entry date but enable the user to modify to a different date if desired. This is for entries that pertain to an activity performed on a date different to the entry date. To acheive this I have created an attribute called "Subject Date" and used preset = $date. In general this works but I would be happy to take any other suggestions on how to acheive it? Also, how do I remove the fixed "Date" attribute from the logbook summary page? I have tried: List = ID, Subject Date, Type, Subject in the config file but this doesn't appear to work? Thanks in advance! Adam |
The option to change what is displayed is called List display = ... and not List = ... Then it works.
- Stefan |