Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 792 of 801  Not logged in ELOG logo
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject Text Attachments
  69650   Wed Feb 8 10:05:03 2023 Reply CryptageThgacryptage@hotmail.frBug reportLinux3.1.5Re: 3.1.5 - Mass edit bug + Wrong versionThanks !

Sometime I need to edit multiple
values to add a new choice.
  
  69681   Mon Aug 14 08:35:58 2023 Reply Stefan RittTherestefan.ritt@psi.chQuestionLinux3.1.5-1Re: line breaks in 'Subject'There are two locations where 'Subject'
is shown, the list display and the individual
message display. I guess you mean the first
  
  69770   Mon Mar 25 16:19:02 2024 Reply scottThank shiva.ps@stfc.ac.ukQuestionLinux3.1.5-1Re: Installation with amp on Rocky LinuxHi,

Thanks for the links to EL8/EL9. 
  
  69834   Wed Sep 25 13:26:07 2024 Reply Patrick UpsonTahpatrick.upson@dfo-mpo.gc.caQuestionWindows2.9.2Re: Looking for version update adviceThanks. I did eveuntaully find the change
log and made the decision to upgrade the
at-sea machines. So far the configuration
  
  67055   Sat Apr 23 14:32:38 2011 Reply PelleSorry, found it InfoLinux2,3.8Re: elog2sql - a script to convert elog logbooks to a MySQL database>  > I know this thread was started
2003 but if anyone have this MySQL export
script please attach it to this thread. >
  
  69561   Mon Sep 26 12:38:29 2022 Reply Stefan RittPermistefan.ritt@psi.chQuestionLinux3.1.4-395Re: Need help with permissionPermissions are handled by the operating
system and have nothing to do with elog.
Make sure you run elog under an account which
  
  69708   Thu Nov 2 11:46:42 2023 Reply Stefan RittNo, stefan.ritt@psi.chQuestionWindows3.1.3Re: Restricting entries view by userNo, this is not possible with the current
version of Elog, so indeed everybody needs
their own logbook.
  
  69567   Wed Oct 5 08:21:12 2022 Reply Stefan RittMoststefan.ritt@psi.chQuestionLinuxELOG V3.1.4-3d7Re: Anyone else running elogd on redhat ES 8 having random crashes?Most likely these are some currupt logbook
files. If you get a coredump (or stack trace)
you can maybe figure out which file it was.
  
ELOG V3.1.5-3fb85fa6