| ID | 
Date | 
Author | 
Topic | 
Subject | 
Text | 
  | 
| 
  1035  
 | 
24 Oct 2014 | 
Konstantin Olchanski | Forum | Running a frontend on Arduino Yun | > INT read_event(char *pevent, INT off)
 
> {
 
>   WORD *data;
 | 
   | 
| 
  1034  
 | 
24 Oct 2014 | 
Stefan Ritt | Forum | Running a frontend on Arduino Yun | > Hello,
 
> 
 
> I'm currently trying to create a midas | 
   | 
| 
  1033  
 | 
24 Oct 2014 | 
Clemens Sauerzopf | Forum | Running a frontend on Arduino Yun | Hello,
 
 
I'm currently trying to create a midas bank | 
   | 
| 
  1032  
 | 
16 Oct 2014 | 
Stefan Ritt | Bug Report | Hostile network scans against MIDAS RPC ports | > Sometimes we have very small MIDAS installations, 
i.e. just one machine by itself, and such 
setups should be secure/secured easily -
 | 
   | 
| 
  1031  
 | 
16 Oct 2014 | 
Konstantin Olchanski | Bug Report | Hostile network scans against MIDAS RPC ports | > Doing this through the ODB seems ok to me. 
If the ODB cannot be accessed, you can fall 
back to no protection.
 | 
   | 
| 
  1030  
 | 
16 Oct 2014 | 
Stefan Ritt | Bug Report | Problem in mfe multithread equipments | > while (1)
 
>    wait 10 ms for an event
 
>    process event, loop back
 | 
   | 
| 
  1029  
 | 
16 Oct 2014 | 
Stefan Ritt | Bug Report | Problem with EQ_USER | I restructured the front-end code to enable 
multiple readout threads for EQ_USER equipment. 
Last summer I was definitively interrupted | 
   | 
| 
  1028  
 | 
15 Oct 2014 | 
Stefan Ritt | Bug Report | Problem with EQ_USER | Sure, each thread needs its own ring buffer 
for writing.
 
 | 
   | 
| 
  1027  
 | 
15 Oct 2014 | 
Stefan Ritt | Bug Report | Problem in mfe multithread equipments | Please disregard my previous posting, you 
don't need the while loop, since it's already 
in the scheduler (around lines 2160 under | 
   | 
| 
  1026  
 | 
15 Oct 2014 | 
Stefan Ritt | Bug Report | Problem in mfe multithread equipments | You are absolutely correct, the code is certainly 
wrong. It looks to me like the 
 
 | 
   | 
| 
  1025  
 | 
14 Oct 2014 | 
Stefan Ritt | Bug Report | Hostile network scans against MIDAS RPC ports | Doing this through the ODB seems ok to me. 
If the ODB cannot be accessed, you can fall 
back to no protection.
 | 
   | 
| 
  1024  
 | 
14 Oct 2014 | 
Konstantin Olchanski | Bug Report | Problem with EQ_USER | If you use EQ_USER in mfe.c and have multiple 
threads writing into the ring buffer, you 
will have a big 
 | 
   | 
| 
  1023  
 | 
14 Oct 2014 | 
Konstantin Olchanski | Bug Report | Problem in mfe multithread equipments | For my reference:
 
good version: https://bitbucket.org/tmidas/midas/src/6899b96a4f8177d4af92035cd84aadf5a7cbc875/src/mfe.c?at=develop
 
first breakage: https://bitbucket.org/tmidas/midas/src/c60259d9a244bdcd296a8c5c6ab0b91de27f9905/src/mfe.c?at=develop
 | 
   | 
| 
  1022  
 | 
14 Oct 2014 | 
Konstantin Olchanski | Bug Report | Hostile network scans against MIDAS RPC ports | At CERN I see a large number of hostile network 
scans that seem to be injecting HTTP requests 
into the 
 | 
   | 
| 
  1021  
 | 
14 Oct 2014 | 
Konstantin Olchanski | Bug Report | Problem in mfe multithread equipments | In the ALPHA experiment at CERN I found a 
problem in mfe.c handling of multithreaded 
equipments. This problem was in 
 | 
   | 
| 
  1020  
 | 
08 Sep 2014 | 
Clemens Sauerzopf | Forum | CAEN V1742 midas driver | Hello all,
 
 
As an addition to the driver functions I | 
   | 
| 
  1019  
 | 
06 Aug 2014 | 
Konstantin Olchanski | Info | MIDAS high speed test | > We have tested operation of MIDAS using 
a 10GigE network connection. Using a dummy 
frontend 
 | 
   | 
| 
  1018  
 | 
06 Aug 2014 | 
Clemens Sauerzopf | Forum | Adding Interrupt handling to SIS3100 driver | Hello Pierre-Andre,
 
 
thank you for your help with the interrupt | 
     | 
| 
  1017  
 | 
16 Jul 2014 | 
Clemens Sauerzopf | Forum | CAEN V1742 midas driver | Hello all, 
 
 
as discussed in the thread about Interrupt | 
     | 
| 
  1016  
 | 
15 Jul 2014 | 
Pierre-Andre Amaudruz | Forum | Adding Interrupt handling to SIS3100 driver | Hello Clemens,
 
 
The hardware readout is triggered by the | 
   |