Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 784 of 806  Not logged in ELOG logo
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  631   Wed Jul 28 22:07:31 2004 Agree Steve Jonessteve.jones@freescale.comBug reportAll2.5.4?Re: getcfg problem in v1.410: Truncation of long config strings
> > Just compiled 1.410 and have run into an issue that *may* have been
> > introduced in 1.393.
> > 
> > Config file directives such as "Welcome title" could be very long strings. 
> > After compiling 1.410, our "Welcome title" is truncated and, while I haven't
> > counted the actual chars, I suspect that the truncation happens at 1024
> > characters.  The procedure 'getcfg' has a declared passed paramater "int
> > vsize". 
> 
> Actually before 1.393 you got a buffer overflow if any string in the
> configuration file was longer than 500 chars, so it's a miracle that your elogd
> did not crash on the long Welcome Title. I added the "vsize" parameter to avoid
> such crashes. To satisfy your need for a long Welcome title, I increased the
> string size for that particular case to 10000 chars. Hope this is enough.

Hmmm, it is a wonder.  Our welcome text was not significantly longer (about 20
chars longer) so perhaps . . . ?

Thanks, will recompile and report back.
  632   Wed Jul 28 22:08:16 2004 Agree Steve Jonessteve.jones@freescale.comRequestAll2.5.3Re: WISHLIST: Type <attribute> = user
> Acknowledged. Added your vote to the wishlist.

Thanks!
  634   Wed Jul 28 22:32:39 2004 Agree Steve Jonessteve.jones@freescale.comBug reportAll2.5.3Re: Date format problem in "Thread display = "
> > I get the following in my THREADED logbook view:
> > 
> > "Adding new services, planned for 1090519200. Last revised: Thu Jul 15
> > 18:03:52 2004"
> 
> That should be fixed by the current version. Please update.

Thanks!
  635   Wed Jul 28 22:33:08 2004 Agree Steve Jonessteve.jones@freescale.comBug reportAll2.5.3Re: BUG?: Preset text = causes replication of text when re-editing a logbook entry.
> > With the "Preset text = " specified, when re-editing a logbook entry (say to
> > correct a spelling error) the text of the "Message" is replicated and placed
> > directly below the original text.
> 
> That should be fixed since revision 1.370 from Jul 7th, 2004. Please update.

Thanks!
  639   Fri Jul 30 12:26:10 2004 Agree Guenter NowakGuenter.Nowqak@t-systems.at   Re: ?cmd=New&pType=PC does not work
> according to the users guide,
> 
> http://midas.psi.ch/elogs/Database/?cmd=New&pType=PC
> 
> should create an entry with the type value set to PC, but this doesn't work

Thanks!
  643   Mon Aug 2 19:27:56 2004 Agree Steve Jonessteve.jones@freescale.comRequestAll2.5.3Re: Wishlist: TOOLTIP for ATTRIBUTES
> Ok, I added the option
> 
> Tooltip <attribute> = ...
> 
> I apply the HTML "title" tag to the whole table row, so the tooltip appears on the
> whole line, not only the attribute name. I guess this is much more intuitive. Give
> it a try. New version under CVS and available as a snapshot.

I like the implementation, especially with the tooltip popping up anywhere in the
area.  Thanks.
  658   Tue Aug 10 20:11:38 2004 Agree Steve Jonessteve.jones@freescale.comBug reportAll2.5.4Re: THREAD DISPLAY = sucks up coded spaces
> > I was trying to do some hard coded spaces using:
> > 
> > Thread display = For: $Date for Shutdown.&nbsp;&nbsp;&nbsp;$DataCenter:
> > $short summary. Coordinator: $Shutdown Coordinator.
> > 
> > The spacing actually works mthe first time, but upon going back into editing
> > the config file, the coded spaces are gone, replaced with real spaces, and
> > when saved all real multiple spaces are, as one would expect, ignored.  The
> > spacing reverts back to normal.
> > 
> > I tried other html tags but these show up as literals.
> 
> I fixed that in revision 1.448. The problem also showed up even in normal
> logbook entry displays and in replies (before this fix, the &nbsp; in this text
> whould not have shown up). Get the new version from CVS.

As always - fantastic!

Thanks
  665   Thu Aug 12 22:17:01 2004 Agree Steve Jonessteve.jones@freescale.comQuestionAll2.5.4Re: Q: on 'FIND MENU commands =' <menu list>
> > The help text on the website says the following:
> > 
> > "The command Select can be used to select multiple messages for deletion of
> > moving to other logbooks."
> > 
> > This is not clear but was the intent to indicate that SELECT can be used to
> > either select multiple log entries for deletion OR for moving to another
> > logbook?  If the latter, then this does not work if one adds the MOVE TO
> > menu item to the list.  If the former then the helptext is a little misleading.
> 
> SELECT can be used for deletion OR moving OR copying. To enable the copy and move
> commands, they have to be present in the "Menu commands" list, like
> 
> Menu commands = Back, New, Edit, Delete, Reply, Find, Config, Logout, Move to, Copy
> to, Help
> 
> I added an appropriate note to the documentation, sorry for the misleading descriptoin.

Thank you.  I had added the "Move To" and this works at the log entry level (i.e., "Move
To <name>) but in the threaded view one does not get the enumerated list of logbooks.

I'll play around with it a little more before re-posting.  When it didn't work as I
expected I read the docs and ran across the confusing text - so I stopped and asked!

Thanks again.
ELOG V3.1.5-3fb85fa6