But it says locked on "websubmission" in the instructions for the command "Locked attributes".

Doesnt it  mean that for instance a logged in admin should be able to change a value of a submitted locked attribute.

I am looking for a possibility to have have certain attributes locked on submission but for instance admin should be able to change the data in them after they has been submitted.

As far as I can remember there is no floating point in elog. 

There is no problem. "Locked" means "Locked", and not "Locked but admin can change it". As admin you can only change the config file, remove the "Locked" option, change the attribute, and put back the "Locked" option.

- Stefan 

 Stefan,

Thanks for your feedback. 

We had confirmed that the CPU load is running at at least 95% while these requests are being processed.  Additionally, we were attempting to use gprof to determine where the code was spending its time.  We have had several problems with trying to use gprof on that platform, both with using it for elog (we get seg faults) and then with using it on a small program created to test gprof on our particular setup (program runs; we get an output file; but all routines show that zero seconds were used).  So, unfortunately, I can not, at this point, provide a good idea of which routines are using the most CPU on this platform.  If we are able to get profiling results on this particular platform, I will certainly share them with you.

A possibly more relevant angle is that we have determined that executing floating-point operations seems to have a drastic impact on software execution times.  Can you point us to routines in the elogd code where floating point operations are taking place?

Thanks,

Tim

Hi!

After submitting a new record with preset "Locked attributes" not even admin user is able to edit these entries.

What seems to be the problem?

Note my config

Logbook Tabs = 0
Theme = default
Date Format = %Y, %B
Title Image= <img border=0 src="konturlogo_dynamate.png" alt="DynaMate logo">
Logout to main = 1
Mode commands = 0
List after submit = 1
Use Email From = weblog@dynamate.se
Use Lock = 1
Password file=improvements_qpp.pwd
Admin User = sssuxo, sssuga
Self register = 3
Restrict edit = 1
Login expiration = 0
Display Email recipients = 0
Preset text = qpp_improvements.txt
Comment = Improvements Uppdragsprocessen
Attributes = Namn, Avdelning, Telefonnummer, Rubrik, Ansvarig, Beräknad klar, Verkligt klar, Status, Status2
Required Attributes = Namn, Avdelning, Telefonnummer, Rubrik
Locked attributes = Ansvarig, Beräknad klar, Verkligt klar, Status, Status2
Options Rubrik = Förfrågan - Mottagning, Förfrågan - Bearbetning, Förfrågan - Anbud, Genomförande - Beställning, Genomförande - Uppdragsplanering, Genomförande - Projektering/Konstruktion, Genomförande - Tillverkning/Utförande, Genomförande - Överlämning till kund, Genomförande - Avslut av uppdrag, Annat
Type Beräknad klar = date
Type Verkligt klar = date
Subst Beräknad klar = $Date
Subst Verkligt klar = $Date
Options Status = Ny, 0%, 25%, 50%, 75%, 100%
Options Status2 = Pågående, Avklarad
Preset Status = Ny
Preset Status2 = Pågående
Cell Style Status 25% = background-color:yellow
Cell Style Status 50% = background-color:orange
Cell Style Status 75% = background-color:33CCFF
Cell Style Status 100% = background-color:green
List Menu Commands = New, Find, Select, Logout, Config, Last day, Help          
Menu commands = List, New, Edit, Delete, Find, Help
List Display = Datum, Namn, Avdelning, Beräknad klar, Verkligt klar, Ansvarig, Status, Status2, Rubrik
Guest menu commands = List, Find, Login, Help
Guest List Menu commands = List, Find, Login, Help
Guest list Display = Datum, Namn, Avdelning, Beräknad klar, Verkligt klar, Ansvarig, Status, Status2, Rubrik
Allow Config = sssuxo
Page Title = Improvements Uppdragsprocessen QPP - $Subject
Suppress default = 3
Reverse sort = 1
Quick filter = Date, Ansvarig, Status, Status2

Regards
/UlfO

Yes there is lots of string handling in elogd, but compared with PHP this is still faster. The getcfg() call actually caches the contents of the config file to improve its performance. I stopped optimization when the response was quick on a 800 MHz Pentium originally, but your 250 MHz ARM might be slower. What you can try is to

1) Verify that the CPU is really the limit, just check that the CPU is at 100% with elogd during your 10 second response time. On some installations, the submit command triggers some email notification, and actually the email server was the bottleneck.

2) If it's indded the CPU for elogd, run it under the gcc profiler. Identify which routines take most CPU and let me know. Maybe I can do something about that.

- Stefan

 Yoshio,

Thanks for the suggestion.

We have actually tried running the elog server with a very minimal set of attributes, all of which were human entries, and still had response times that were entirely unacceptable.  So, unfortunately this path won't solve all our issues.

tt

Hi!

Looking at your config file it seems that a lot of the attributes are not user-specified but rather auto-generated content. You may want to consider using the elog client to submit such entries; this might avoid performance issues related to communication of the server with the web browser used for entry generation. This way, event entries can even be automatically created by other software rather than having a user to submit them.

Yoshio