| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
345
|
17 Feb 2007 |
Konstantin Olchanski | Bug Report | segmentation violation of analyzer on a x86_64 | > Yes right, Problem of a segmentation violation
is solved with this patch. Now it works
> fine on x86_64.
|
|
|
346
|
23 Feb 2007 |
Konstantin Olchanski | Info | RFC- support for writing to removable hard disk storage | At triumf, we are developing a system to use
removable hard drives to store data collected
by midas
|
|
|
347
|
23 Feb 2007 |
Konstantin Olchanski | Info | RFC- history system improvements | While running the ALPHA experiment at CERN,
we stressed and broke the MIDAS history system.
We
|
|
|
360
|
06 Mar 2007 |
Konstantin Olchanski | Info | commited mhttpd fixes & improvements | I commited the mhttpd fixes and improvements
to the history code accumulated while running
the ALPHA
|
|
|
361
|
15 Mar 2007 |
Konstantin Olchanski | Info | mhdump: a standalone MIDAS history dump utility | While working on improvements to the MIDAS
history system, I understood the data
format of the MIDAS .hst files and wrote |
|
|
363
|
16 Mar 2007 |
Konstantin Olchanski | Info | RFC- history system improvements | > Let's improve the midas history system...
After implementing 2 prototypes, one aspect |
|
|
367
|
09 Apr 2007 |
Konstantin Olchanski | Info | move history, elog and alarm functions into separate files | As approved by Stefan, I moved the history
(hs_xxx), alarm (al_xxx) and elog (el_xxx)
functions out of
|
|
|
371
|
09 May 2007 |
Konstantin Olchanski | Forum | Splitting data transfer and control onto different networks | > I'm setting up a system with two networks
with the intension of having
> control info (odb, alarm) on the 192.168.0.x
|
|
|
372
|
10 May 2007 |
Konstantin Olchanski | Bug Fix | mhttpd: fix broken boolean arrays in "edit on start" | For some time now, boolean arrays did not
work correctly in "/experiment/edit on start".
This is now fixed
|
|
|
373
|
10 May 2007 |
Konstantin Olchanski | Bug Fix | Fix error reporting from cm_transition() | For some time now, error reporting from cm_transition()
was broken.
|
|
|
374
|
10 May 2007 |
Konstantin Olchanski | Info | RHEL5/SL5 success! | FWIW, I am running latest 32-bit MIDAS on
an AM2 dual core AMD machine under 64-bit
SL5. Everything
|
|
|
376
|
21 May 2007 |
Konstantin Olchanski | Info | mhttpd changes to use /History/Tags data | I am slowly commiting the changes to the history
code. This installement adds
code to mhttpd to use the /History/Tags data |
|
|
381
|
07 Jun 2007 |
Konstantin Olchanski | Suggestion | RFC- ACLs for midas rpc, mserver, mhttpd access | Running MIDAS at CERN is proving more challenging
than I expected. The network environement
is not
|
|
|
391
|
29 Jun 2007 |
Konstantin Olchanski | Bug Fix | mscb, musbstd fixed on Linux, MacOS | I commited a few minor changes to musbstd
and mscb code to make them work on
MacOSX (tested on 10.3.9) and Linux (tested |
|
|
394
|
06 Jul 2007 |
Konstantin Olchanski | Bug Fix | mscb, musbstd fixed on Linux, MacOS | > I commited a few minor changes to musbstd
and mscb code...
>
|
|
|
395
|
12 Jul 2007 |
Konstantin Olchanski | Forum | Midas on a x86_64 - incompatible with x86_32 | > We run 64-bit MIDAS on RHEL4 with 64-bit
ROOT and everything generally works,
> except for compatibility problems with |
|
|
398
|
12 Aug 2007 |
Konstantin Olchanski | Info | Change of pointer type in mvmestd.h | > I had to change the pointer type of mvme_read
and mvme_write to (void *) instead
> to (mvme_locaddr_t *) to avoid warnings |
|
|
399
|
12 Aug 2007 |
Konstantin Olchanski | Forum | Midas on a x86_64 - incompatible with x86_32 | > I agree to make 32-bit and 64-bit compatible.
In the long run, everything will be 64-bit,
so I would suggest
|
|
|
400
|
20 Aug 2007 |
Konstantin Olchanski | Forum | Midas on a x86_64 - incompatible with x86_32 | > > I agree to make 32-bit and 64-bit compatible.
In the long run, everything will be 64-bit,
so I would suggest
|
|
|
401
|
20 Aug 2007 |
Konstantin Olchanski | Bug Report | how to handle end of run? | I am having problems with handling the end-of-run
situation in my midas
frontend. I have a device that continuously |
|