Re: Restrict Top Groups to logged-in users?, posted by Chris Green on Tue Jul 26 21:54:39 2005
|
| Stefan Ritt wrote: |
If you move the "password file = <file>" entry around, you can get fooled by stored cookies. So after each modification, make sure to delete all cookies in your browser. |
This didn't work, but after corresponding with Stefan privately, the following did:
[global]
Show Top Groups = 1
[global top_group]
Protect selection page = 1
Password file = papers.pwd
Thanks again, Stefan.
Chris |
|
Re: Response is very slow with beta3, posted by Emiliano Gabrielli on Wed Aug 3 13:01:17 2005
|
| PJ Meyer wrote: | I finally got 2.60 Beta3 running on my server (explicit statements in cfg for most of the defaults)
Now I'm seeing a veerrry slooooow response time - over 3 minutes to open a logbook vs 10 sec in 2.54
Utilization of CPU runs to 60% on elogd.
Tried slimning down elog.cfg, 'emptying' userlog file (actually renamed so Elog created a new one).
Still 2.60b3 is very slow to respond.
When I rolled back to 2.54 speed was fast again.
Any ideas?
this is on a dual processor Win2000 server with 2 gb memory.
attached is the elog.cfg if that helps.
i'm stumped
7/28 Follow-up testing and trials
When I stopped using a password file - speed was quick and responsive (on test book with no password file speed was good which got me thinking about the password file)
When I added back in the 'old' xml password file - slow response
I created new password file with only one user - slow response (took almost 3 minutes to save new account)
I've attached the password file so you can try it out if yo want....
This has me very stumped. |
I can confirm .. it's very very slow for me too:
munmap(0xb7db4000, 4096) = 0
select(1024, [5], NULL, NULL, {6, 0}) = 1 (in [5], left {5, 996000})
recv(5, "GET /calendar_filter/imgs/window"..., 100000, 0) = 485
open("/usr/share/elog/scripts/calendar_filter/imgs/window_close.gif", O_RDONLY) = 6
close(6) = 0
open("/usr/share/elog/scripts/calendar_filter/imgs/window_close.gif", O_RDONLY) = 6
lseek(6, 0, SEEK_END) = 648
lseek(6, 0, SEEK_CUR) = 648
lseek(6, 0, SEEK_SET) = 0
time([1123066183]) = 1123066183
read(6, "GIF89a\20\0\20\0\306`\0\16\26 \r\27!\16\30!\24 .\25 .I"..., 648) = 648
close(6) = 0
send(5, "HTTP/1.1 200 Document follows\r\nS"..., 879, 0) = 879
close(5) = 0
select(1024, [3], NULL, NULL, {1, 0}) = 0 (Timeout)
select(1024, [3], NULL, NULL, {1, 0}) = 0 (Timeout)
select(1024, [3], NULL, NULL, {1, 0}) = 0 (Timeout)
select(1024, [3], NULL, NULL, {1, 0}) = 0 (Timeout)
select(1024, [3], NULL, NULL, {1, 0}) = 0 (Timeout)
select(1024, [3], NULL, NULL, {1, 0}) = 0 (Timeout)
select(1024, [3], NULL, NULL, {1, 0}) = 0 (Timeout)
select(1024, [3], NULL, NULL, {1, 0}) = 0 (Timeout)
select(1024, [3], NULL, NULL, {1, 0}) = 0 (Timeout)
select(1024, [3], NULL, NULL, {1, 0}) = 1 (in [3], left {0, 81000})
accept(3, {sa_family=AF_INET, sin_port=htons(57723), sin_addr=inet_addr("127.0.0.1")}, [16]) = 5
time(NULL) = 1123066193
socket(PF_FILE, SOCK_STREAM, 0) = 6
connect(6, {sa_family=AF_FILE, path="/var/run/.nscd_socket"}, 110) = -1 ENOENT (No such file or directory)
close(6) = 0
for every image elog has to serve one can see something similar to the above ... lot of time lost in selects.. then a lot of data (serving an image I suppose), then a lot of time in select again and again ... untill everything is sent, in a couple of minutes or more 
Maybe an issue related to the dns search you introduced in order to guess the correct host name ?? .. |
|
Re: Response is very slow with beta3, posted by Stefan Ritt on Wed Aug 3 22:44:43 2005
|
| Emiliano Gabrielli wrote: | for every image elog has to serve one can see something similar to the above ... lot of time lost in selects.. then a lot of data (serving an image I suppose), then a lot of time in select again and again ... untill everything is sent, in a couple of minutes or more
Maybe an issue related to the dns search you introduced in order to guess the correct host name ?? .. |
This is strange to me, since I did not change anything which could slow down the server this much. The dns search your mentioned is only evaluated once on startup of elogd, so it cannot be the cause. The select() statements with Timeouts are normal. If there is no HTTP request (elogd is idling), the select should time out after one second, to be able to check a changed config file for example. If a HTTP request arrives, the select() call is immediately terminated and the request served.
There is however some problem with DNS server which I saw on midas.psi.ch. If the DNS host name resolution is slow due to a slow DNS server, this could slow down elogd considerably significantly, but only occasionally. I saw elogd hanging on midas.psi.ch like once or twice a day for ~30 seconds.
I order to address this problem, I imlemented a global flag "resolve host names = 0|1". The default is "0", which means that elogd does not contact the DNS server, and rather save the raw IP address in log files etc.
Can you check the CVS version and see if it makes any difference? |
|
Re: Response is very slow with beta3, posted by Emiliano Gabrielli on Thu Aug 4 11:19:53 2005
|
| Stefan Ritt wrote: |
| Emiliano Gabrielli wrote: | for every image elog has to serve one can see something similar to the above ... lot of time lost in selects.. then a lot of data (serving an image I suppose), then a lot of time in select again and again ... untill everything is sent, in a couple of minutes or more
Maybe an issue related to the dns search you introduced in order to guess the correct host name ?? .. |
This is strange to me, since I did not change anything which could slow down the server this much. The dns search your mentioned is only evaluated once on startup of elogd, so it cannot be the cause. The select() statements with Timeouts are normal. If there is no HTTP request (elogd is idling), the select should time out after one second, to be able to check a changed config file for example. If a HTTP request arrives, the select() call is immediately terminated and the request served.
There is however some problem with DNS server which I saw on midas.psi.ch. If the DNS host name resolution is slow due to a slow DNS server, this could slow down elogd considerably significantly, but only occasionally. I saw elogd hanging on midas.psi.ch like once or twice a day for ~30 seconds.
I order to address this problem, I imlemented a global flag "resolve host names = 0|1". The default is "0", which means that elogd does not contact the DNS server, and rather save the raw IP address in log files etc.
Can you check the CVS version and see if it makes any difference? |
No, ok it appears to be a very strange problem related to my JS calendar filter ... I'll change it's state to beta in contributions, but the very strange thing is that it works fine when no stunnel is used ... |
|
Re: Reset a user's password, posted by Stefan Ritt on Fri Oct 28 16:41:11 2016
|
Sure. Hit "Config", select other user, and click on "Change password".
Stefan
| Val Schmidt wrote: |
|
Is it possible for an administator to reset a user's password?
Thanks,
Val
|
|
|
Re: Required and {}, posted by Stefan Ritt on Fri Feb 16 17:19:30 2007
|
| bob wrote: | | generally, can one handle "Required" and "{}" or "{ , }", ... |
For simple configuration files, that should work. If I have for example:
Attributes = Author, Type, Category, Subject
Options Type = Routine{r}, Software Installation{s}, Problem Fixed{p}, Configuration, Other
{r} Required Attributes = Author
Then the attributes "Author" is only required if "Type" equals "Routine". |
|
Re: Required and {}, posted by bob on Mon Feb 19 20:46:39 2007
|
| Stefan Ritt wrote: |
| bob wrote: | | generally, can one handle "Required" and "{}" or "{ , }", ... |
For simple configuration files, that should work. If I have for example:
Attributes = Author, Type, Category, Subject
Options Type = Routine{r}, Software Installation{s}, Problem Fixed{p}, Configuration, Other
{r} Required Attributes = Author
Then the attributes "Author" is only required if "Type" equals "Routine". |
you are right, I try to re-examine my configuration and I will say to you |
|
Re: Required Attributes, posted by Stefan Ritt on Fri May 14 17:03:36 2010
|
| Eric Krise wrote: |
|
Is there a way to require a certain attribute on reply, but not on an original entry? In some cases info. for these fields only exists on reply.
|
No. There is only "Preset on reply ..." and "Remove on reply...". You could for example require that attribute, preset it for new entries with some dummy value, and remove that value with "Remove on reply...". Maybe that works. |
|