ID |
Date |
Author |
Topic |
Subject |
Text |
|
708
|
27 Jun 2010 |
Jimmy Ngai | Forum | Error connecting to back-end computer | > Hi, there. I have not recently run mserver
through inetd, and we usually do not do
> that at TRIUMF. We do this:
|
|
709
|
28 Jun 2010 |
Stefan Ritt | Forum | Error connecting to back-end computer | > > Hi, there. I have not recently run mserver
through inetd, and we usually do not do
> > that at TRIUMF. We do this:
|
|
710
|
28 Jun 2010 |
Jimmy Ngai | Forum | Error connecting to back-end computer | > The way connections work under Midas is
there is a callback scheme. The client starts
|
|
711
|
29 Jun 2010 |
Konstantin Olchanski | Forum | Error connecting to back-end computer | > > The way connections work under Midas is
there is a callback scheme. The client starts
|
|
2569
|
02 Aug 2023 |
Stefan Ritt | Bug Report | Error accessing history files | We sporadically (like once per few hours)
have an error message when we access the
|
|
2577
|
09 Aug 2023 |
Konstantin Olchanski | Bug Report | Error accessing history files | I confirm I see same on the agmini system.
Two problems: (a) error message is wrong,
it's a
|
|
2588
|
16 Aug 2023 |
Stefan Ritt | Bug Report | Error accessing history files | Tonight we got another error of that type
after the update:
|
|
2591
|
17 Aug 2023 |
Konstantin Olchanski | Bug Report | Error accessing history files | Confirmed. The error message is wrong. It
is printed after a short read(), but short
read() does not
|
|
2593
|
19 Aug 2023 |
Stefan Ritt | Bug Report | Error accessing history files | Still get the same error with the latest version:
3:28 [mhttpd,ERROR] [history_schema.cxx:2913:FileHistory::read_data,ERROR] |
|
2615
|
06 Oct 2023 |
Konstantin Olchanski | Bug Report | Error accessing history files | > Still get the same error with the latest
version:
> 3:28 [mhttpd,ERROR] [history_schema.cxx:2913:FileHistory::read_data,ERROR] |
|
2616
|
06 Oct 2023 |
Konstantin Olchanski | Bug Report | Error accessing history files | > two fixes forthcoming:
> a) check for short read in the 2nd place
that I missed
|
|
1255
|
05 Apr 2017 |
Andreas Suter | Bug Report | Equipment Expand doesn't work anymore | I'd liked very much the possibility to hide
away Equipment on the main page. It
is also nice to have the '+' to get it quickly |
|
1257
|
10 Apr 2017 |
Stefan Ritt | Bug Report | Equipment Expand doesn't work anymore | > I'd liked very much the possibility to hide
away Equipment on the main page. It
> is also nice to have the '+' to get it |
|
1258
|
10 Apr 2017 |
Andreas Suter | Bug Report | Equipment Expand doesn't work anymore | > > I'd liked very much the possibility to
hide away Equipment on the main page. It
> > is also nice to have the '+' to get it |
|
1264
|
15 Apr 2017 |
Konstantin Olchanski | Bug Report | Equipment Expand doesn't work anymore | > > > I'd liked very much the possibility
to hide away Equipment on the main page.
It
|
|
2014
|
17 Nov 2020 |
Stefan Ritt | Info | Equipment "common" settings in ODB | Today I addressed a topic which bugged me
since long time. The ODB contains
settings under /Equipment/<name>/Common which |
|
2019
|
20 Nov 2020 |
Pierre-Andre Amaudruz | Info | Equipment "common" settings in ODB | Indeed this "mirror" of the ODB in settings
option can cause frustration in
particular when we think the ODB is empty |
|
2032
|
27 Nov 2020 |
Konstantin Olchanski | Info | Equipment "common" settings in ODB | > Today I addressed a topic which bugged me
since long time.
|
|
2036
|
27 Nov 2020 |
Stefan Ritt | Info | Equipment "common" settings in ODB | Ok, so what about the following proposal:
- I change back the mfe.cxx code to behave |
|
2037
|
27 Nov 2020 |
Konstantin Olchanski | Info | Equipment "common" settings in ODB | Yes, I think this will work.
For old mfe.c frontends, global variable |
|