Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 32 of 807  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown Text Attachments
  68699   Fri Nov 17 18:58:52 2017 Question Susan Jamessjames@lbl.govQuestionLinux3.1.2-bd7hosts allowI'm trying to wrap our elog instance
to our company domain which is lbl.gov

I add this entry below (without
  
  66881   Wed Aug 25 02:49:44 2010 Question Owen LaGardeolagarde@gmail.comQuestionLinux2.7.8honor "user" field in the Apache SSL request object or environment variables in SSL process groups?Will elog defer user identification and
authorization to the ssl engine of a *local*
Apache proxy?  I'd like to try elog
  
  69523   Tue Apr 26 18:03:03 2022 Reply Konstantin Olchanskiolchansk@triumf.caQuestionWindows3.1.4-a04faf9fhistory of long-removed freebsd package, Re: Vulnerability?> > > > debian package still outdated?

the freebsd elog package was removed back
  
  1280   Wed Jul 20 19:49:21 2005 Entry Juliana Pengjpeng@yorku.caRequestLinuxV2.6.0hide attributes when view the logbookHi Stefan,

Thanks for the great work. We have been using
  
  69291   Sun Jan 10 11:13:31 2021 Question Lahreche Abdelmadjidabdelmadjid.lahreche@yahoo.comQuestionWindows2006hidden filesHello;

Could I make change on program
only on the " elogd.cfg" ?
  
  66353   Wed May 6 20:49:24 2009 Question Alexander Withersalexw@bnl.govQuestionLinux2.7.5-2130help with substituting subjectsI am trying to add additional information
to the subject of new entries:

Subst subject = $subject [INCIDENT
  
  66697   Thu Jan 28 19:21:39 2010 Question stefan harjesstefanharjes@yahoo.deInfoLinuxlatesthandwritingI write my lab journal with pen and though
of getting a linux supported tablet. Has
anybody ever used ELOG and did input using
  
  624   Wed Jul 28 18:25:32 2004 Warning Steve Jonessteve.jones@freescale.comBug reportAll2.5.4?getcfg problem in v1.410: Truncation of long config stringsJust compiled 1.410 and have run into an issue
that *may* have been
introduced in 1.393.
  
ELOG V3.1.5-3fb85fa6