| 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.
|
|
|
1312
|
10 Aug 2017 |
Stefan Ritt | Suggestion | Increasing Max Number of Frontends | The sizeof checks were originally invented
by KO to check for binary compatibility between
processes attached to the same ODB and event |
|
|
1313
|
12 Aug 2017 |
Konstantin Olchanski | Suggestion | Increasing Max Number of Frontends | The checks for byte sizes of critical data
structures have been added to ensure (enforce)
binary compatibility
|
|
|
1314
|
13 Aug 2017 |
Stefan Ritt | Suggestion | Increasing Max Number of Frontends | I agree that the binary compatibility checks
are crucial. But I kind of find it strange
if one gets an assert failure some where |
|
|
1315
|
13 Aug 2017 |
Konstantin Olchanski | Suggestion | Increasing Max Number of Frontends | > if (sizeof(INT) != 4) then severe_error_and_stop_all_programs()
Quick reply.
|
|
|
1316
|
13 Aug 2017 |
Stefan Ritt | Suggestion | Increasing Max Number of Frontends | The type INT has been defined in 1989 when
I for the first time sent data between a
16-bit MS-DOS computer and a 32-bit VAX computer |
|
|
2397
|
06 May 2022 |
Stefan Ritt | Info | Increased timeout for program shut down | We had the problem in our lab that a frontend
took about 6 seconds to gracefully
shut down, mainly it needed to park some |
|
|
147
|
29 Sep 2004 |
Stefan Ritt | Info | Increased number of clients in midas.h, important! | Due to some request several limitations like
the maximal number of clients to the ODB
have
|
|
|
149
|
03 Oct 2004 |
Konstantin Olchanski | Info | Increased number of clients in midas.h, important! | > It is important to note that clients compiled
> with the old limits cannot coexist with
clients compiled with the new limits. You |
|
|
151
|
03 Oct 2004 |
Stefan Ritt | Info | Increased number of clients in midas.h, important! | > Stefan, to avoid confusion from crashes
caused by incompatible ODBs would it be possible
to add a "version number" to ODB,
|
|
|
152
|
03 Oct 2004 |
Konstantin Olchanski | Info | Increased number of clients in midas.h, important! | > However, we are planning to make a new release
1.9.5 soon (next week), so can can people
tell not to "mix" 1.9.5 with pre-1.9.5 programs.
|
|
|
153
|
04 Oct 2004 |
Stefan Ritt | Info | Increased number of clients in midas.h, important! | > Right. We cannot fix the past, but we should
fix the future. BTW, "do not mix versions"
is hard to enforce and mismatches did, do |
|
|
154
|
08 Oct 2004 |
chris pearson | Info | Increased number of clients in midas.h, important! |
> > For one thing, looking at a given midas-using
executable, how do I tell what version of |
|
|
155
|
08 Oct 2004 |
Konstantin Olchanski | Info | Increased number of clients in midas.h, important! | > A lot of programs have a commandline
option, such as "--version", where they return
the program version number then exit. As |
|
|
302
|
20 Sep 2006 |
Stefan Ritt | Suggestion | Increase of maximum event size | Dear midas users,
The current event size in midas is limited |
|
|
303
|
20 Sep 2006 |
Stefan Ritt | Suggestion | Increase of maximum event size | Since nobody complained so far, I increased
MAX_EVENT_SIZE to 2MB. If anybody has problems
with this setting, please report. Note that |
|
|
308
|
27 Sep 2006 |
Konstantin Olchanski | Suggestion | Increase of maximum event size | > The current event size in midas is limited
to 512k (MAX_EVENT_SIZE in midas.h)
|
|
|
309
|
28 Sep 2006 |
Stefan Ritt | Suggestion | Increase of maximum event size | [quote="K.O."]Now, we have per-buffer tunable
size (see message
https://ladd00.triumf.ca/elog/Midas/283) |
|
|
Draft
|
07 Jun 2017 |
Alberto Remoto | Forum | Increase MAX_EVENT_SIZE | Hello,
I am using a CAEN v1720 to digitise signal |
|
|
514
|
23 Oct 2008 |
Konstantin Olchanski | Bug Report | Inconsistent handling of odb and evet buffer timeouts | In midas.c there are several places where
client last activity time stamps are checked
against the
|
|