Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 329 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  1368   Thu Aug 4 11:19:53 2005 Reply Emiliano GabrielliAlberT@SuperAlberT.itBug reportLinux | Windows2.60b3Re: Response is very slow with beta3

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 Crying


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 ...
  68449   Fri Oct 28 16:41:11 2016 Reply Stefan Rittstefan.ritt@psi.chQuestionAll3.1.1Re: Reset a user's password

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

 

  2139   Fri Feb 16 17:19:30 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionLinux | WindowsV2.6.3-177Re: Required and {}

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".
  2142   Mon Feb 19 20:46:39 2007 Reply bobbobgrang@yahoo.frQuestionLinux | WindowsV2.6.3-177Re: Required and {}

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
  66821   Fri May 14 17:03:36 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.8-2294Re: Required Attributes

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. 

  69319   Mon Mar 22 15:10:12 2021 Reply Stefan Rittstefan.ritt@psi.chRequestLinux | AllV3.1.4Re: Request: make $text available for "subst"

$text is the full body text and can go over many lines. Since attributes are restricted to single lines, it's not possible to substitute them with the body text.

Stefan

Andreas Luedeke wrote:

Hi Stefan,

I've just tried to read the $text with subst into another field and failed.
It looks like $text is only available for the execution of shell scripts in the "execute new|edit|delete = <script>" command.

Could that be added? I can think of a multitude of applications:

  • In my case I want to fill an attribute X either with free text or generated from other fields. The list view will show just X and not how it was generated.
  • I could fill an attribute automatically with the character length of the text.
  • I could parse the text in a shell script and set other attributes according to the content.

Thank you for considering it.

Cheers, Andreas

 

  69320   Mon Mar 22 19:59:13 2021 Reply Andreas Luedekeandreas.luedeke@psi.chRequestLinux | AllV3.1.4Re: Request: make $text available for "subst"

While the input widget of text attributes is a single line, they can easily be multi-line in the display - when you use HTML at least.
And of course the user can parse the text field and generate a single line, if he wants to.
If you leave it to me, I'll create wonderful applications to that feature :-)

Please? ;-)

Stefan Ritt wrote:

$text is the full body text and can go over many lines. Since attributes are restricted to single lines, it's not possible to substitute them with the body text.

Stefan

Andreas Luedeke wrote:

Hi Stefan,

I've just tried to read the $text with subst into another field and failed.
It looks like $text is only available for the execution of shell scripts in the "execute new|edit|delete = <script>" command.

Could that be added? I can think of a multitude of applications:

  • In my case I want to fill an attribute X either with free text or generated from other fields. The list view will show just X and not how it was generated.
  • I could fill an attribute automatically with the character length of the text.
  • I could parse the text in a shell script and set other attributes according to the content.

Thank you for considering it.

Cheers, Andreas

 

 

  69321   Tue Mar 23 13:42:27 2021 Reply Sebastian Schenksebastian.schenk@physik.uni-halle.deRequestLinux | AllV3.1.4Re: Request: make $text available for "subst"

I am not Stefan, but maybe I can add to this issue.

Personally I think it is not a good way to dump all the information into the text field and try to let the server parse it.
This could be archived more simply by using e.g. the python elog scripts or using the elog command tool to directly submit well structured elog entires.

As you have mentioned you could use the "execute new|edit|delete" commands to do the things you want to do.
Let the called script fetch the elog entry and alter it in the way you like and resubmit the entry.
(You have to make sure to don't generate a endless loop and you have to proably have to use a forwarding script as the elog "execute" command waits for finished execution).
This way you don't touch the 1500 characters limit of passing $text to the execute command.

Also the point "filling an attribute X with free text" needs some kind of (extended) parsing, which isn't possible with the subst command.
In our elog we such an attribute X, which is in some conditions filled with a set of other attributes and on other conditions just a normal input field, so the user could type custom text in.

"fill an attribute automatically with the character length of the text" could be done with the above mentioned execute command or it could be done on the clientside (e.g. browser using javascript or if automatically generated by a script, then directly by the script)

I hope it helps to build our application.
Best wishes,
Sebastian

Andreas Luedeke wrote:

Hi Stefan,

I've just tried to read the $text with subst into another field and failed.
It looks like $text is only available for the execution of shell scripts in the "execute new|edit|delete = <script>" command.

Could that be added? I can think of a multitude of applications:

  • In my case I want to fill an attribute X either with free text or generated from other fields. The list view will show just X and not how it was generated.
  • I could fill an attribute automatically with the character length of the text.
  • I could parse the text in a shell script and set other attributes according to the content.

Thank you for considering it.

Cheers, Andreas

 

ELOG V3.1.5-3fb85fa6