| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
1616
|
11 Jul 2019 |
Konstantin Olchanski | Bug Report | problems with the default mhttpd configuration | We installed recent mhttpd on a ubuntu machine
and discovered a number of problems
with the default mhttpd settings.
|
|
|
1006
|
06 Jun 2014 |
Alexey Kalinin | Forum | problem with writing data on disk | Hello,
Our experiment based on MIDAS 2.x DAQ.
I'm using several identical frontend-%d |
|
|
1009
|
16 Jun 2014 |
Alexey Kalinin | Forum | problem with writing data on disk | Hello, once again.
What I found is when I tryed to stop the
run, mlogger still working and writing some |
|
|
1010
|
18 Jun 2014 |
Alexey Kalinin | Forum | problem with writing data on disk | Hello,
I'm in deppression.
I removed Everything from computer with mserver |
|
|
1293
|
16 May 2017 |
Konstantin Olchanski | Bug Report | problem with odb strings and db_get_record() | Suddenly the mhttpd odb inline editor is truncating
the odb string entries to the actual length
of the
|
|
|
1295
|
31 May 2017 |
Konstantin Olchanski | Bug Report | problem with odb strings and db_get_record() | > What a mess.
The mess with db_get_record() and db_open_record() |
|
|
1296
|
31 May 2017 |
Konstantin Olchanski | Bug Report | problem with odb strings and db_get_record() | > 2) replace all uses of db_open_record(MODE_READ)
with db_watch() in conjunction with db_get_record1().
|
|
|
1297
|
02 Jun 2017 |
Stefan Ritt | Bug Report | problem with odb strings and db_get_record() | That all makes sense to me.
Stefan
|
|
|
1298
|
06 Jun 2017 |
Konstantin Olchanski | Bug Report | problem with odb strings and db_get_record() | > Done to all in-tree programs, except for
mana.c (not using it), sequencer.cxx (cannot
test it) and a few places where watching |
|
|
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
|
|
|
Draft
|
04 Nov 2016 |
Thomas Lindner | Bug Report | problem with error code DB_NO_MEMORY from db_open_record() call when establish additional hotlinks | Hi Tim,
I reproduced your problem and then managed |
|
|
1220
|
04 Nov 2016 |
Thomas Lindner | Bug Report | problem with error code DB_NO_MEMORY from db_open_record() call when establish additional hotlinks | Hi Tim,
I reproduced your problem and then managed |
|
|
1221
|
25 Nov 2016 |
Thomas Lindner | Bug Report | problem with error code DB_NO_MEMORY from db_open_record() call when establish additional hotlinks | The procedure I wrote seemed to work for Tim
too, so I added a page to the wiki about
it here:
|
|
|
434
|
18 Feb 2008 |
Konstantin Olchanski | Bug Report | potential memory corruption in odb,c:extract_key() | It looks like ODB function extract_key() will
overwrite the array pointed to by "key_name"
if given an odb
|
|
|
444
|
21 Feb 2008 |
Konstantin Olchanski | Bug Report | potential memory corruption in odb,c:extract_key() | > It looks like ODB function extract_key()
will overwrite the array pointed to by "key_name"
if given an odb
|
|
|
2071
|
13 Jan 2021 |
Isaac Labrie Boulay | Forum | poll_event() is very slow. | Hi all,
I'm currently trying to see if I can speed |
|
|
2072
|
13 Jan 2021 |
Konstantin Olchanski | Forum | poll_event() is very slow. | >
> I'm currently trying to see if I can speed
up polling in a frontend I'm testing.
|
|
|
Draft
|
13 Jan 2021 |
Pierre-Andre Amaudruz | Forum | poll_event() is very slow. | > Hi all,
>
> I'm currently trying to see if I can speed |
|
|
2074
|
13 Jan 2021 |
Stefan Ritt | Forum | poll_event() is very slow. | Something must be wrong on your side. If you
take the example frontend under
|
|