Well it would appear i answered my own problem.

Start page = page1

Hello All,

The subject is roughly what i'm asking about so here are the details. I have combed through the forums for an answer and didn't come up with anything regarding what i need.

Issue:

Below is what the logbook is setup as. However once there are more than 10 entries on the page, when a user views the logbook, elog automatically puts them to the higher value page # (ie entry number 11 is on page 2).

As I am sorting the entries by status and by Dist or Beat to organize entries for quicker viewing and access, I would prefer that elog always shows on page 1 when a user views the log book. The statuses are setup for sorting properly but when reverse sort is turned on, status "3-Closed" appears at the top instead of status "1-Open" to appear at the top, Status "2-Sent to Next Shift" next, then "3-Closed" after that.

Is there a to just view page 1 without doing the reverse sort?

Theme = default
Page Title = ELOG - $logbook
Entries per page = 10
Attributes = Entered By, Call Type, Date/Time Reported, Customer Name, Customer Phone Number, Location, Dist or Beat, Description, Badge, Updated By, Action Taken, Report Time, Status
List Display = Entered By, Call Type, Date/Time Reported, Customer Name, Location, Dist or Beat, Description, Badge, Updated By, Status
Locked Attributes = Entered By, Updated By
Preset Entered By = $long_name
Preset on edit Updated By = $long_name
Options Status = 1-Open, 2-Sent to Next Shift, 3-Closed
Preset Status = 1-Open
Cell Style Status 1-Open = background-color:red
Cell Style Status 2-Sent to Next Shift = background-color:yellow
Cell Style Status 3-Closed = background-color:green
Type Date/Time Reported = Datetime
Type Customer Phone Number = numeric
Type Report Time = Datetime
Sort Attributes = Status, Dist or Beat
Reverse sort = 0
Use Lock = 0
Summary lines = 0
Self Register = 0

Thanks in advance.

G

 I will check out the "Top Groups". But another question, the documentation says "Prior to ELOG version 2.4.1, one had to run two elogd servers in parallel, listening under different ports." ... how do you set this up?

Just for completeness: I was running two elogd servers (2.9.0) on one Linux host in order to provide an english and a german web interface to the same logbooks, synchronised by the mirror server mechanism.

That didn't work out well, the elogd crashed infrequently. But of course mirror servers are not intended to run on the same host. Eventually I've just dropped the english server.

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

 

Have you checked the option "Top groups", which was made especially for that case? You can create several independent sets of logbooks not seeing each other. 

Thank you.. that version works fine for me.

 I need to do this because there are 2 different groups that each have 6 or 7 different logbooks in their elogd.cfg files.  (and they can't access each others log books)

Currently the first group  accesses elog as http:elog.com:8080.  The elogd windows service executes "C:\Program FilesELOG\elogd.exe" -D -c "C:\Program Files\ELOG\elogd.cfg"  

From what I can tell, whats needed is either some way to get the windows service to run a different config file or there needs to be a way of creating a second elog windows service that points to a different elogd.cfg file. Is there some way of doing this?

 It's probably not of much help, but for a short time I ran two elog daemons on the same linux box, using different ports.  It was thus able to run with two separate elogd.cfg files.   This is linux, and heavily biased to my eccentric way of running this linux box, but started them as:

/usr/local/sbin/elogd -p 8080 -c /home/logbooks1/elogd1.cfg -d /home/logbooks1

/usr/local/sbin/elogd -p 8081 -c /home/logbooks2/elogd2.cfg -d /home/logbooks2

Do note that as I was the only user on that linux box, I didn't have login etc.

However, I was soon asked questions by Andreas as to how I found this running, as he had encountered problems with an earlier version.  To be honest, that stopped me experimenting too far with this at that point, as well as a coincidental upgrading of my hardware.

But I was doing this *not* because I had to run two separate elogd.cfg files, but other reasons which meant splitting into two at that time vastly improved the performance of elog on the linux box at that time.  So while I didn't actually enounter any problems in doing so, I only have limited experience - and, of course, absolutely none on running even one [windows equivalent of a daemon] on Windows.

I am assuming here you have good reason for two separate elogd.cfg files, rather than just wanting to run two separate logbooks - guessing here, but one set public (no login) and one set private (with login)?