| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
1309
|
27 Jul 2017 |
Wes Gohn | Suggestion | Increasing Max Number of Frontends | Below are the steps we used to increase the
maximum number of frontends that we could
run.
|
|
|
1382
|
21 Aug 2018 |
Wes Gohn | Bug Report | mserver problem | Hi. We've just updated our midas installation
to the newest version, and we now see repeated
errors from the
|
|
|
846
|
14 Dec 2012 |
Vinzenz Bildstein | Suggestion | Midas + Elog with SSL | I've been trying to set up midas to create
an automatic elog entry at the end of
each run and I've run into a problem. I've |
|
|
848
|
17 Dec 2012 |
Vinzenz Bildstein | Suggestion | Midas + Elog with SSL | > > I've been trying to set up midas to create
an automatic elog entry at the end of
> > each run and I've run into a problem. |
|
|
1597
|
08 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | I wrote a c++ frontend to read data from CAEN
VX1730 digitizers which is used in
parallel with the GRIFFIN frontend to read |
|
|
1601
|
08 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | > run the frontend inside gdb and post the
stack trace after the crash?
>
|
|
|
1603
|
08 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | > > > run the frontend inside gdb and post
the stack trace after the crash?
> > >
|
|
|
1605
|
08 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | > > >
> > > For SIGKILL, my gdb reports "Program
terminated with signal SIGKILL, Killed." |
|
|
1608
|
10 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | > > > >
> > > > For SIGKILL, my gdb reports "Program
terminated with signal SIGKILL, Killed." |
|
|
1613
|
11 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | > > ... finding a current midas.log file
>
> On the "help" page, see "midas.log".
|
|
|
1680
|
08 Sep 2019 |
Vinzenz Bildstein | Bug Report | https redirect and ODB access | I'm not sure if these issues are related or
not, but I'm getting an error
message when I want to access the root of |
|
|
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] |
|
|
994
|
28 Apr 2014 |
Tom Stuttard | Forum | Words written as zero in Midas bank | Hi,
I am having some trouble with the data in |
|
|
1152
|
05 Jan 2016 |
Tom Stuttard | Suggestion | 64 bit bank type | I've seen that a similar question has been
asked in 2011 but I'll ask again in
case there are any updates. Is there any |
|
|
Draft
|
15 Jan 2016 |
Tom Stuttard | Suggestion | 64 bit bank type | > > I've seen that a similar question has
been asked in 2011 but I'll ask again in
|
|
|
1155
|
19 Jan 2016 |
Tom Stuttard | Suggestion | 64 bit bank type | > > I've seen that a similar question has
been asked in 2011 but I'll ask again in
|
|
|
654
|
08 Oct 2009 |
Tim Nicholls | Bug Report | mserver linking fails when using shared library | I have experienced a problem building MIDAS
from the head of the SVN repository (rev
4458) when
|
|
|
1039
|
13 Nov 2014 |
Tim Gorringe | Forum | using single frontend with multiple "EQ_POLLED" equipments to generate different data streams |
We have a MIDAS frontend that provides both |
|
|
1216
|
24 Oct 2016 |
Tim Gorringe | Bug Report | problem with error code DB_NO_MEMORY from db_open_record() call when establish additional hotlinks | Hi Midas forum,
I'm having a problem with odb hotlinks after |
|
|
1218
|
25 Oct 2016 |
Tim Gorringe | Bug Report | problem with error code DB_NO_MEMORY from db_open_record() call when establish additional hotlinks | oOne additional comment. I was able to trace
the setting of the error code DB_NO_MEMORY
|
|