| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
103
|
15 Nov 2003 |
Konstantin Olchanski | | Phantom "open records" | Sometimes (maybe after a client uncleanly
exits?), I see phantom "open
records", for example:
|
|
|
104
|
16 Nov 2003 |
Stefan Ritt | | Phantom | I have seen the same behaviour and it annoys
me, too. What I did in the past
is a "cleanup" in ODBEdit which removes these |
|
|
105
|
20 Nov 2003 |
Stefan Ritt | | Phantom | I tried to reproduce the problem, but without
success. So in case this happens
again, one should debug the code im cm_watchdog() |
|
|
873
|
11 Apr 2013 |
Thorsten Lux | Forum | Persistent ipcrm error | Hello,
I have a problem with our DAQ which is based |
|
|
874
|
11 Apr 2013 |
Konstantin Olchanski | Forum | Persistent ipcrm error | > [system.c:308:ss_shm_open,ERROR] Shared
memory segment with key 0x4d008002 already
exists,
|
|
|
875
|
11 Apr 2013 |
Stefan Ritt | Forum | Persistent ipcrm error | [quote="Thorsten Lux"]In addition now I cannot
start anymore the mlogger from the web interface
but only manually. However, I can stop it |
|
|
876
|
12 Apr 2013 |
Thorsten Lux | Forum | Persistent ipcrm error | [quote="Stefan Ritt"][quote="Thorsten Lux"]In
addition now I cannot start
anymore the mlogger from the web interface |
|
|
877
|
12 Apr 2013 |
Stefan Ritt | Forum | Persistent ipcrm error |
> Hi Stefan,
>
|
|
|
878
|
12 Apr 2013 |
Thorsten Lux | Forum | Persistent ipcrm error | >
> > Hi Stefan,
> >
|
|
|
879
|
12 Apr 2013 |
Thorsten Lux | Forum | Persistent ipcrm error | Hi,
it seems that I solved the problem in a quite |
|
|
880
|
12 Apr 2013 |
Stefan Ritt | Forum | Persistent ipcrm error | > [odb.c:6038:db_paste,ERROR] found string
exceeding MAX_STRING_LENGTH
|
|
|
192
|
20 Jan 2005 |
Konstantin Olchanski | Bug Report | Persistency problem with h1_book() & co | The current h1_book() macros (and the previous
example analyzer code) have an
odd persistency problem: for example, the |
|
|
193
|
21 Jan 2005 |
John M O'Donnell | Bug Report | Persistency problem with h1_book() & co | > The current h1_book() macros (and the previous
example analyzer code) have an
> odd persistency problem: for example, the |
|
|
194
|
21 Jan 2005 |
Stefan Ritt | Bug Report | Persistency problem with h1_book() & co | > I can't get onto cvs@midas.psi.ch right
now
> (cvs update
|
|
|
195
|
25 Jan 2005 |
Stefan Ritt | Bug Report | Persistency problem with h1_book() & co | > > I can't get onto cvs@midas.psi.ch right
now
> > (cvs update
|
|
|
196
|
25 Jan 2005 |
John M O'Donnell | Bug Report | Persistency problem with h1_book() & co | So now that cvs is reachable again I have
confirmed that
the code segment
|
|
|
471
|
23 Mar 2008 |
Konstantin Olchanski | Info | Per-variable history implementation in the mlogger | The changes to mlogger implementing per-variable
history have been committed to
svn. Revision 4145.
|
|
|
472
|
23 Mar 2008 |
Konstantin Olchanski | Info | Per-variable history implementation in the mlogger | > The changes to mlogger implementing per-variable
history have been committed to
> svn. Revision 4145.
|
|
|
474
|
25 Mar 2008 |
Stefan Ritt | Info | Per-variable history implementation in the mlogger | Before approving the code, two conditions
have to be fulfilled:
|
|
|
1329
|
21 Nov 2017 |
Konstantin Olchanski | Release | Pending release of midas | We are readying a new release of midas and
it is almost here except for a few buglets
on the new html status page.
|
|