By default, elog enties are sorted by their ID number.  When viewing a logbook in Full or Summary, they are
shown in strict order of ID.  In Threaded, entries are shown in strict order of ID for the latest entry of each
thread, and then previous entries (in reply to) back from the latest one.  

In collapsed mode, it is only the starting entry of each thread is shown (or the latest one if "collapse to
last" chosen, but that's a detail).

I have a couple of logbooks where I'd like the default sorting to be by another numeric attribute that I enter. 

Now this works fine in Full or Summary mode.  In threaded mode (e.g. default for this forum, where every entry
is shown but are grouped by thread), it works in as much as all the entres are there and in order, but it
doesn't quite look the same as when sorting by ID - the replies are not each offset further right beneath the
entry it is in reply to, but all just slightly offset to the first entry.  

If you try to [completely] collapse the threaded mode to just one line per threaded topic - it doesn't.  Looks
(almost) the same as threaded.

I was hoping to get the list of entries collapsed to one line per thread, in order of the numeric attribute, but
I cannot seem to get this to happen.   Have I missed something here?  Or is it possible at all?

Usually the problem comes from the fact that a daemon runs from the root directory ('/') by definition. I might not find your scripts if they are not in the path. Try to call them explicitly with the ful path like "/usr/local/elog/script.sh".

/Stefan 

Hi all

I have setup an logbook that executes a number of shell scripts to preset attributes and append standart information, which works great. Now I am trying to daemonise the whole thing. I have tried the -D option as well as daemontools. In both cases the logbook itself is functional but the bash scripts do not get executed.

Any ideas how I can resolve this problem?

Martin

Norm wrote:

Andreas Luedeke wrote: Norm wrote: I attempted to install the newest version of elog on our site elog server from an old old version.  Around 2008 I believe.  I then received an application failed to initialize properly 0xc0150002 after installing the newest version.  I then tried installing the Feb 2013 version and received the same message.  Panicked, I rolled back our server to its state yesterday.  I would like to update our elog software, anyone know why I am receiving this error??  Hi Norm. I have not much experience with windows, but I can give you my two cent on how to proceed: Check the old elogd version. It is shown at the bottom of your elog web page (this forum shows ELOG V2.9.2-2475). Copy your logbook data to a different PC, maybe your office PC. Then compile the latest elog on your office PC, run it with the copied data and access it as http://localhost:8080 (or whatever port number you are using) If it is still crashing: re-compile it using "make debug" and run it from a debugger (I don't know any C-debugger for Windows). Post the precise error message.   Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English   Good luck! Andreas, We do not have the current revision at the bottom of any of the pages.  Is there another way I can find out the current revision I'm using? Thanks!

Try:

/usr/local/sbin/elogd -h

Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish

Detect language » English

 

This is the path for Linux, it is likely different on Windows. But you could just run "elogd -h" in the directory where you compile elogd.

It should print out the version in the first line.

Andreas Luedeke wrote:

Norm wrote: I attempted to install the newest version of elog on our site elog server from an old old version.  Around 2008 I believe.  I then received an application failed to initialize properly 0xc0150002 after installing the newest version.  I then tried installing the Feb 2013 version and received the same message.  Panicked, I rolled back our server to its state yesterday.  I would like to update our elog software, anyone know why I am receiving this error??  Hi Norm. I have not much experience with windows, but I can give you my two cent on how to proceed: Check the old elogd version. It is shown at the bottom of your elog web page (this forum shows ELOG V2.9.2-2475). Copy your logbook data to a different PC, maybe your office PC. Then compile the latest elog on your office PC, run it with the copied data and access it as http://localhost:8080 (or whatever port number you are using) If it is still crashing: re-compile it using "make debug" and run it from a debugger (I don't know any C-debugger for Windows). Post the precise error message.   Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English   Good luck!

 Andreas,

We do not have the current revision at the bottom of any of the pages.  Is there another way I can find out the current revision I'm using?

Thanks!

Andreas Luedeke wrote:

scogordo wrote: I've been asked to export one of our logbooks to xls or csv. Doable? Thanks, Scott Hi Scott, yes, every user can export entries using the "find" command. Just select the export format in the first line Export to:  CSV ("," separated)   CSV (";" separated)   XML   Raw     Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English     Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English     Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English     Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English     Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English   I often use the XML Format, but CSV is fine if you just want to import the entries to some spreadsheet program. I was shocked to find out that this feature has not yet made it into the documentation?!? But it is that simple to use that there is not much to document. There is even an "Import" command, to reimport entries from a file. But this is tricky to use: if you have fields of type date or datetime, then you have to convert those fields in the proper format.

I tried EXPORTING logbooks as .csv but have not been fully successful.  Elog seems to only export the data entered for various fields with the exception of the text field.

Here is an example export from my logbook (used to track simulator problems), I would like to also export the TEXT field so it can be used by my managers in excel...but as you can see there is no entry for "TEXT" fields...

Thanks in advance!

"Message ID","Date","Author","Type","Status","Priority"

107,Thu  30 May 2013 11:28:57 -0700,"Jim Tinlin","Graphic Display","Evaluated","Low"

106,Thu  30 May 2013 10:02:24 -0700,"Jim Tinlin","Graphic Display","Identified","Low"

105,Thu  30 May 2013 08:07:27 -0700,"Jim Tinlin","Problem ID","Identified","Medium"

104,Thu  30 May 2013 08:04:30 -0700,"Jim Tinlin","Problem ID","Identified","Medium"

103,Wed  29 May 2013 09:36:11 -0700,"Jim Tinlin","Problem ID","Evaluated","High"

102,Wed  29 May 2013 08:58:02 -0700,"Jim Tinlin","Problem ID","Evaluated","High"