| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
633
|
06 Sep 2009 |
Exaos Lee | Bug Report | Delete key "/A_Str" problem | Another problem while using odbedit.
I tried the batch mode of "odbedit". I created
a key as "/A_Str" by mistake and
|
|
|
639
|
06 Sep 2009 |
Exaos Lee | Bug Report | Delete key "/A_Str" problem | > Another problem while using odbedit.
> I tried the batch mode of "odbedit". I
created a key as "/A_Str" by mistake and |
|
|
2943
|
19 Feb 2025 |
Lukas Gerritzen | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | We have a frontend for slow control with a
lot of legacy code. I wanted to add a new
equipment using the
|
|
|
2944
|
24 Feb 2025 |
Stefan Ritt | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | The commit that introduced the write cache
size check is https://bitbucket.org/tmidas/midas/commits/3619ecc6ba1d29d74c16aa6571e40920018184c0
|
|
|
2972
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | I think I added the cache size correctly:
{"Trigger", /* equipment |
|
|
2973
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | the main purpose of the event buffer write
cache is to prevent high contention for the
|
|
|
2974
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | > the main purpose of the event buffer write
cache
|
|
|
2975
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | > > the main purpose of the event buffer write
cache
> how to control the write cache size:
|
|
|
2979
|
21 Mar 2025 |
Stefan Ritt | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | > All this is kind of reasonable, as only
two settings of write cache size are useful:
0 to
|
|
|
3004
|
25 Mar 2025 |
Konstantin Olchanski | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | > > All this is kind of reasonable, as only
two settings of write cache size are useful:
0 to
|
|
|
2451
|
13 Jan 2023 |
Denis Calvet | Suggestion | Debug printf remaining in mhttpd.cxx | Hi everyone,
It has been a long time since my last message. |
|
|
2452
|
13 Jan 2023 |
Stefan Ritt | Suggestion | Debug printf remaining in mhttpd.cxx | These debug statements were added by K.O.
on June 24, 2021. He should remove it.
|
|
|
604
|
02 Jul 2009 |
Dawei Liu | Forum | Data taking hangs in the middle of run | Hi,
We are using midas to read ADC. It sometimes |
|
|
605
|
03 Jul 2009 |
Pierre-Andre Amaudruz | Forum | Data taking hangs in the middle of run | Hi Dawei,
Could you give more info on your setup:
|
|
|
606
|
06 Jul 2009 |
Dawei Liu | Forum | Data taking hangs in the middle of run | Hi Pierr-Andre,
|
|
|
1728
|
21 Oct 2019 |
Vinzenz Bildstein | Forum | Data for key truncated | I keep on getting messages like this:
16:25:35 [fecaen,ERROR] [odb.c:4567:db_get_data,ERROR] |
|
|
1729
|
23 Oct 2019 |
Konstantin Olchanski | Forum | Data for key truncated | > I keep on getting messages like this:
> 16:25:35 [fecaen,ERROR] [odb.c:4567:db_get_data,ERROR]
data for key
|
|
|
699
|
22 Apr 2010 |
Jimmy Ngai | Forum | Customized "Start" page | Dear All,
After clicking the "Start" button, there |
|
|
1436
|
14 Jan 2019 |
Becky Chislett | Bug Report | Custom script with new MIDAS | I am having difficulty getting the custom
scripts to work within the updated MIDAS.
Before the
|
|
|
1437
|
18 Jan 2019 |
Konstantin Olchanski | Bug Report | Custom script with new MIDAS | > I am having difficulty getting the custom
scripts to work within the updated MIDAS.
Before the
|
|