Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 681 of 807  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Hide attachments  Show only new entries    6451 Entries 
Goto page Previous  1, 2, 3 ... 680, 681, 682 ... 805, 806, 807   Next  
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  1961   Mon Oct 9 22:32:11 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionAll2.6.2-1714Re: "Supress Email Notification" checkbox
Suppress email on edit has been implemented in the current SVN revision just similar to the Suppress default flag having possible values of 0, 1, 2 and 3.
  1972   Tue Oct 10 15:32:21 2006 Idea Ben Shepherdbjs54@dl.ac.ukRequestAll2.6.2-1714'Inline' button for attachments
Hi,

It would be good if when you uploaded an image as an attachment, there was a button next to it that pasted the code 
[img]elog:1972/1[/img]
into the log entry. This way, it would be more easy to have inline images in a log entry.

cheers

ben
  1973   Tue Oct 10 16:09:12 2006 Reply Stefan Rittstefan.ritt@psi.chRequestAll2.6.2-1714Re: 'Inline' button for attachments

Ben Shepherd wrote:
Hi,

It would be good if when you uploaded an image as an attachment, there was a button next to it that pasted the code 
[img]elog:1972/1[/img]
into the log entry. This way, it would be more easy to have inline images in a log entry.


Just hit that button:


and it does exactly what you want.
  1974   Tue Oct 10 16:15:21 2006 Reply Ben Shepherdbjs54@dl.ac.ukRequestAll2.6.2-1714Re: Re: 'Inline' button for attachments

Stefan Ritt wrote:

Ben Shepherd wrote:
Hi,

and it does exactly what you want.

cool! thanks.
  1975   Tue Oct 10 23:27:41 2006 Agree Steve Jonessteve.jones@freescale.comQuestionAll2.6.2-1714Re: "Supress Email Notification" checkbox

Stefan Ritt wrote:
Suppress email on edit has been implemented in the current SVN revision just similar to the Suppress default flag having possible values of 0, 1, 2 and 3.



Works like a champ! Thanks
  2023   Fri Oct 27 19:11:32 2006 Warning Steve Jonessteve.jones@freescale.comBug reportAll2.6.2-1723Interesting behavior with $shell
eLog does not do math so I am trying to leverage the $SHELL function to perform the math. I am using GAWK to perform the math -- I started trying to use CONDITIONAL ATTRIBUTES to assign numeric values to attributes but with loading up the ATTRIBUTES with all of the options brings elog to its knees in terms of performance -- the parsing of attributes is simply too string intensive.

So, I embedded the numeric score in the OPTIONS of the ATTRIBUTE and leveraged the text processing prowess of GAWK:
Options WhoIsEffected =   1:...Single User, 5:...Project, 10:...Department, 50:...Site
Options ServiceOutage =   1:...0-1 Minutes, 2:...10 Minutes, 10:...20 Minutes, 30:...30 Minutes, 100:...gt60

Then pass the following command to GAWK:
Preset TotalScore = $shell(gawk 'BEGIN{split(\"$WhoIsEffected:$ServiceOutage\",scores,\":\");print scores[1]+scores[3]}' )

The interesting result is this works - the proper summation is returned but apparently elog parsing also returns everything after the first ')' as something that also needs to be returned. So the resulting contents of TotalScore is 
2;print scores[1]+scores[3]}' )
assuming one chose the first option of both attributes (the output pasted here are real results).

Before getting to this point I tried using the GAWK internal variable of $0 - but this did not work because apparently $0 in elog is defined as the OS shell!

Stefan, is it possible for you to try creating a logbook on the elog demo site that shows people how to perform math and in the process discover what the $SHELL function is doing?
  2024   Sun Oct 29 16:04:05 2006 Reply Steve Jonessteve.jones@freescale.comBug reportAll2.6.2-1723Re: Interesting behavior with $shell

Steve Jones wrote:
eLog does not do math so I am trying to leverage the $SHELL function to perform the math. I am using GAWK to perform the math -- I started trying to use CONDITIONAL ATTRIBUTES to assign numeric values to attributes but with loading up the ATTRIBUTES with all of the options brings elog to its knees in terms of performance -- the parsing of attributes is simply too string intensive.

So, I embedded the numeric score in the OPTIONS of the ATTRIBUTE and leveraged the text processing prowess of GAWK:
Options WhoIsEffected =   1:...Single User, 5:...Project, 10:...Department, 50:...Site
Options ServiceOutage =   1:...0-1 Minutes, 2:...10 Minutes, 10:...20 Minutes, 30:...30 Minutes, 100:...gt60

Then pass the following command to GAWK:
Preset TotalScore = $shell(gawk 'BEGIN{split(\"$WhoIsEffected:$ServiceOutage\",scores,\":\");print scores[1]+scores[3]}' )

The interesting result is this works - the proper summation is returned but apparently elog parsing also returns everything after the first ')' as something that also needs to be returned. So the resulting contents of TotalScore is 
2;print scores[1]+scores[3]}' )
assuming one chose the first option of both attributes (the output pasted here are real results).

Before getting to this point I tried using the GAWK internal variable of $0 - but this did not work because apparently $0 in elog is defined as the OS shell!

Stefan, is it possible for you to try creating a logbook on the elog demo site that shows people how to perform math and in the process discover what the $SHELL function is doing?




Steve Jones wrote:

So, in order to quickly get around the problem I did the following:
Preset TotalScore = $shell(echo \"$WhoIsEffected:$ServiceOutage\" | gawk -f <gawkscript>' )

This works since all of the script logic is contained in an external script but removes the logic from the elog config, so if anything changes one has to remember to change the script (which is in a comment).
  2053   Wed Nov 8 13:59:52 2006 Idea Stefan Rittstefan.ritt@psi.chInfoAll2.6.2-6Denial of Service Vulnerability of elog 2.6.2-6
Dear ELOG users,

a denial of service vulnerability has been reported which affects all elog versions prior to 2.6.2-7. With a special request one can crash the elogd server, given that one has access either through a public read access or through an account. This vulnerability has been fixed in version 2.6.2-7. It is advised that all sensitive installations of ELOG are being updated.

Stefan Ritt
Goto page Previous  1, 2, 3 ... 680, 681, 682 ... 805, 806, 807   Next  
ELOG V3.1.5-3fb85fa6