Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 219 of 806  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6445 Entries 
Goto page Previous  1, 2, 3 ... 218, 219, 220 ... 804, 805, 806   Next  
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  65735   Tue Feb 12 08:54:48 2008 Reply Richard Ecclestonerichard.ecclestone@cern.chBug reportLinux | WindowsV2.7.2Re: Data Export:: Date Problem

Stefan Ritt wrote:

Stefan Ritt wrote:

Richard Ecclestone wrote:

Hi

Im currently experimenting with Elog to see if we can use it to track maintenance work. But Ive come up against a problem, When I export the data to a csv file,

the date has a comma inserted between the day of the week and the rest of the date. This means that all the fields are then shifted to the right after the date.

This looks like a bug to me, the test records included in the demo does not exhibit this problem, until a new record is added.

  What about exporting record separated by a semicolong ";" ?

I fixed that in SVN revision #2040, the comma is simply replaced by a space in the date string.

Hi Stefan

Thanks for the quick reply.

We seem to be running 2012 - Which may explain the problem - I will see with our system administrator why we are not running 2040. By the way I also had this problem when running the windows version.

Cheers.. Richard

  65736   Tue Feb 12 10:52:17 2008 Reply Richard Ecclestonerichard.ecclestone@cern.chBug reportLinux | WindowsV2.7.2Re: Data Export:: Date Problem

Richard Ecclestone wrote:

Stefan Ritt wrote:

Stefan Ritt wrote:

Richard Ecclestone wrote:

Hi

Im currently experimenting with Elog to see if we can use it to track maintenance work. But Ive come up against a problem, When I export the data to a csv file,

the date has a comma inserted between the day of the week and the rest of the date. This means that all the fields are then shifted to the right after the date.

This looks like a bug to me, the test records included in the demo does not exhibit this problem, until a new record is added.

  What about exporting record separated by a semicolong ";" ?

I fixed that in SVN revision #2040, the comma is simply replaced by a space in the date string.

Hi Stefan

Thanks for the quick reply.

We seem to be running 2012 - Which may explain the problem - I will see with our system administrator why we are not running 2040. By the way I also had this problem when running the windows version.

Cheers.. Richard

Hi Stefan

Our IT administrator has just downloaded and installed the latest source code from the site and installed it. We still now have version 2012?

Where do we get version 2041 ?

Cheers,  Richard

 

  65737   Tue Feb 12 11:42:01 2008 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux | WindowsV2.7.2Re: Data Export:: Date Problem

Richard Ecclestone wrote:

Our IT administrator has just downloaded and installed the latest source code from the site and installed it. We still now have version 2012?

Where do we get version 2041 ?

The bleeding edge version you get always from our SVN server, but you have to recompile it yourself. For your convenience, I just made you a version 2.7.2-3 containing the latest source code.

  65738   Tue Feb 12 20:40:53 2008 Reply Richard Ecclestonerichard.ecclestone@cern.chBug reportLinux | WindowsV2.7.2Re: Data Export:: Date Problem

Stefan Ritt wrote:

Richard Ecclestone wrote:

Our IT administrator has just downloaded and installed the latest source code from the site and installed it. We still now have version 2012?

Where do we get version 2041 ?

The bleeding edge version you get always from our SVN server, but you have to recompile it yourself. For your convenience, I just made you a version 2.7.2-3 containing the latest source code.

Thanks Stefan

Everything works now.

  65739   Tue Feb 12 23:57:52 2008 Reply Jochen Krempelkrempel@ill.frCommentAll2.7.2-2Re: Absolut links for images in FCK Editor

Stefan Ritt wrote:

Jochen Krempel wrote:

We use ELOG inside a local network, but we want to allow access also from outside the firewall.

The suggested solution from Elog Admin Guide worked fine until version ELOG V2.6.5-1844 (essentially without FCK Editor):

ssh -L 1234:your.server.name:8080 your.firewall.name
firefox http://localhost:1234/

Howerver, since the update to ELOG V2.7.1-2002 the FCK Editor uses absolute links to insert images.

An image uploaded from the local network will have an address like:

http://your.server.name:8080/logbookname/080207_101110/Picture.jpg

while the same image uploaded through the firewall tunnel will have a link like:

http://localhost:1234/logbookname/080207_101110/Picture.jpg

Obviously images uploaded from outside are not visible from inside and vice versa.

Is it possible to convince FCK Editor to use relative links?

PS
ELOG is great!!

 

I fixed this in SVN revision #2038.

Thank you for the quick support!

  65741   Fri Feb 15 06:59:52 2008 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.7.2Re: move mxml code into elog's src directory

Jeff Stoner wrote:

The mxml source code should be moved into the elog-*/src directory. This requires changing the Makefile to:

MXMLDIR = src/mxml

Reason for change: if you want to build several versions of elog and you unpack the distributions in the same top-level directory, the most recently unpackaged version will overwrite the mxml directory contents, possibly introducing bugs.

From your point of view that request is reasonable, but the reason of having mxml in a separate top level directory is that I use it in many different projects. If I would keep a copy of mxml in each project, I would have to update all of them manually if there is a bug. On the other hand the code of mxml changes very seldom. If you look at the history, it got ~5 changes last year, while elog itself had hundreds. And since I do not change the API, a bugfix in mxml should be to the benefit of all elog versions. It is like with other projects which depend on a number of packages. Like if you install Apache for example, you need a certain version of OpenSLL, a certain version of libcrypt, and so on.  So think of mxml like another package you have to combine with elog.

  65742   Fri Feb 15 15:46:38 2008 Reply Richard Ecclestonerichard.ecclestone@cern.chInfoWindowsELOG V2.7.Re: Message ID and trouble ticketing system

lance wrote:

Stefan Ritt wrote:

lance wrote:

I am trying to create a trouble ticket system however when you do a reply you get a new message ID.  I was hoping to use the message ID as a ticket number and just wanted to use the reply as an append to the orginal message id, however each reply creates a new message id. This would be a nightmare to track and if I closed the ticket I would have to close every log entry related to this.

Does anyone know how to either make the reply and appended reply (appended to the orignal message id) or how to create a field that automatically gives it a new trouble ticket number.

Has anyone configured a trouble ticket system that I could look at to get some ideas?

First of all, ELOG has been designed having shift logbooks in mind, so it probably will never be a perfect trouble ticket system. Nevertheless, there are some options which can help in that respect:

  • Use attributes Ticket and Status
  • Preset Ticket with a running ticket number via

    Preset ticket = TCK-#####

    This will increment the 5-digit ticket number whenever you create a new ticket, but will not update it when you do a reply

  • Use Status to determine the status of the whole trouble ticket chain (initial entry plus replies)

    Options Status = open, closed
    Preset Status = open

  • Once a ticked chain is closed, do the following:

    • Go to the threaded list display
    • Click on Select
    • Select the trouble ticket chain
    • Click on Edit
    • Now change Status from "Open" to "Closed"
    This will then modify the Status of the whole chain from "Open" to "Closed"

Stefan,

Thanks for this, I had already implemented the Preset Ticket Nr = TT-##### but I didnt use the threaded and Select to close the ticket, very nice tip thanks. I think this program can be have several uses, and working very well. The trouble ticketing will work for us.

Once again thanks for the very speedy support.

Lance

 

 

Hi

I tried the 'Preset ticket = TCK-#####' method to create unique numbers for our application. This worked very nicely until we replied to a earlier message, if we then create a new message the system creates a sequential number after the last message number we replied to. For example if we have 10 messages. If someone replies to message number #2 then when a new record is created it is then assigned number #3 not #11, thus making a duplicate entry for #3.

 Any ideas?

Cheers Richard

  65745   Mon Feb 18 07:03:29 2008 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows Re: error "Cannot retrieve host name: No error" using command line in Windows

Dan Gawarecki wrote:

I automatically install software on 3 machines in our lab, and at the end of the process, use eLOG to record relevant information for each machine (all running Windows XP) via the command line program elog.exe.  2 of the machines log their info correctly, but on third machine, I get the following error:

    Cannot retrieve host name: No error

The error is not very clear (i.e., the error is "no error"?), and furthermore, operationally, the error makes no sense to me, for the three machines are supposedly configured the same.


 

The error is produced by the C routine "gethostbyname". This routine tries to obtain the IP address of your host max13 and fails. The error "no error" is the error passed to elog from the underlying operating system, so please blame Windows for that. I guess you have a problem that on the machine you get the error you have some DNS problem, so this machine does not know max13. Try to "ping" max13 or do a "nslookup max13" to verify this. Maybe you have to add your domain after max13, or put this machine explicitly into \Windows\System32\drivers\etc\hosts.

Dan Gawarecki wrote:

I am not sure which version of eLOG is being used, but the size of the elog.exe is 139,264. 

I suggest a new option be added to display the version information, or display the version info whenever eLOG is execute, or display the version info when "-?" option is used.

I added some version information being displayed with the "-?" option. This feature will be contained in the next release.

Goto page Previous  1, 2, 3 ... 218, 219, 220 ... 804, 805, 806   Next  
ELOG V3.1.5-3fb85fa6