upgrading, posted by tony summerfelt on Wed Nov 20 17:55:07 2002
|
this is happened before, and it just happened upgrading from 2.2.2 to 2.2.3
the link at the bottom of the page shows a previously installed version.
i don't install to the elog directory, i install to a ram disk and copy over the new executables, the source, readme and help html.
the link showed 2.1.2 until i upgraded to 2.2.2 (i didn't do anything different than the above. now i'm at 2.2.3 and the link is showing 2.2.2...not that it's a big deal, i'm just wondering what i did wrong |
Re: upgrading, posted by tony summerfelt on Thu Nov 21 18:22:58 2002
|
> Of course you have to stop the old elogd program and start the new one. Have
> you done that?
on windows i run it as a service through firedaemon, but i stop it before upgrading...that was one of the first things i checked... |
Re: upgrading, posted by tony summerfelt on Wed Nov 27 07:22:07 2002
|
> Ooops, I just realized that the Windows 2.2.3 distribution contained the old
> (2.2.2) executable for elogd.exe. I apologize for that. I have updated the
that's ok. i just it was driving me nuts there for a while...everything is fine now...
i've tried other web based msg boards, but i keep coming back to elog... |
two features, posted by tony summerfelt on Fri Nov 29 17:00:36 2002
|
unless i missed these in the docs some place:
1) a threaded display but collapsed threads unstead of all replies showing
2) the subject is the link along with the icon. it would make it a little easier to click on the message if you run your montior on a high resolution... |
Re: two features, posted by tony summerfelt on Thu Dec 12 18:10:03 2002
|
> This feature has been added in Version 2.2.4 which has been released today.
> Use the "collase" button.
> This feature has been added in Version 2.2.4 as well. Use "line as link = 1"
> in elogd.cfg
thanks. that was quick :) |
expand flag, posted by tony summerfelt on Thu Dec 12 19:02:03 2002
|
i have expand flag set to 0 but it doesn't seem to be working...
i can expand and collapse via the links, or if i make sure the url includes it. |
Re: expand flag, posted by tony summerfelt on Thu Dec 19 16:16:42 2002
|
> I checked your elogd.cfg: The flag is called "Expand default" not "Expand" as
> you had it. With "Expand default = 0" it works fine. Just RTFM...
i could probably recite the manual from memory :/ i wouldn't ask if i wasn't confused about something.
i thought the 'default' word was explaining what the default was for the 'expand' flag, not an actual part of the flag. |
elog fails to connect with "cannot get host name: Success" message, posted by ScottK on Fri Sep 23 17:27:40 2005
|
I can't seem to connect using elog: elog -h <myhost>:8080 -v -l Servers -a "Type=Routine" -a "Author=ScottK" -m ~/test.txt it run fine through the web interface on http://<myhost>:8080/Servers I have URL = http://<myhost>:8080 in my elogd.cfg Any clues what I'm doing wrong? Thanks for any help. ScottK |