ID |
Date |
Author |
Topic |
Subject |
Text |
 |
958
|
11 Feb 2014 |
Stefan Ritt | Bug Report | mhttpd, etc. | [quote="Andreas Suter"]I found a couple of
bugs in the current mhttpd, midas version:
"93fa5ed"[/quote]
|
|
967
|
23 Feb 2014 |
Andre Frankenthal | Bug Report | Installation failing on Mac OS X 10.9 -- related to strlcat and strlcpy | Hi,
I don't know if this actually fits the Bug |
|
971
|
27 Feb 2014 |
Konstantin Olchanski | Bug Report | Installation failing on Mac OS X 10.9 -- related to strlcat and strlcpy | >
> I don't know if this actually fits the
Bug Report category. I've been trying to |
|
972
|
27 Feb 2014 |
Andre Frankenthal | Bug Report | Installation failing on Mac OS X 10.9 -- related to strlcat and strlcpy | > >
> > I don't know if this actually fits the
Bug Report category. I've been trying to |
|
1011
|
07 Jul 2014 |
Ryu Sawada | Bug Report | mhist does not show history when -s option is used | When I use -s option of mhist, it does not
show history, for example.
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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.
|
|
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
|
|
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 |
|
1028
|
15 Oct 2014 |
Stefan Ritt | Bug Report | Problem with EQ_USER | Sure, each thread needs its own ring buffer
for writing.
|
|
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 |
|
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
|
|
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.
|
|
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 -
|
|
1042
|
27 Jan 2015 |
Konstantin Olchanski | Bug Report | getaddrinfo() | To support IPV6, we need to migrate MIDAS
from gethostbyname() to getaddrinfo(). (Thanks
to
|
|
1072
|
16 Jul 2015 |
Thomas Lindner | Bug Report | jset/ODBSet using true/false for booleans | MIDAS does not seem to be consistent (or at
least convenient) with how it
handles booleans in AJAX functions.
|
|
1082
|
29 Jul 2015 |
Stefan Ritt | Bug Report | jset/ODBSet using true/false for booleans | See bitbucket for the solution.
https://bitbucket.org/tmidas/midas/issues/29/jset-odbset-using-true-false-for-booleans#comment-20550474 |
|