| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
1150
|
10 Dec 2015 |
Amy Roberts | Suggestion | script command limited to 256 characters; remove limit? | Both the /Script and /CustomScript trees in
the ODB allow users to trigger a
script via Midas - which silently truncates |
|
|
1157
|
28 Jan 2016 |
Konstantin Olchanski | Suggestion | script command limited to 256 characters; remove limit? | Thank you for reporting this problem:
a) ODB key *names* are restricted to 31 characters |
|
|
1158
|
28 Jan 2016 |
Amy Roberts | Suggestion | script command limited to 256 characters; remove limit? | Using low-level memory allocation routines
in higher-level programs like mhttpd makes
me nervous.
|
|
|
1166
|
26 Feb 2016 |
Konstantin Olchanski | Suggestion | script command limited to 256 characters; remove limit? | > Using low-level memory allocation routines
in higher-level programs like mhttpd makes
me nervous.
|
|
|
1180
|
13 Jun 2016 |
Konstantin Olchanski | Info | running mhttpd on port 443 | mhttpd running as non-root cannot bind to
standard https port 443. By default, mhttpd
uses port
|
|
|
969
|
27 Feb 2014 |
Andreas Suter | Suggestion | runlog is "ugly" | I have a couple of questions and suggestions
concerning the "new" CSS style of the mhttpd,
especially related to the runlog
|
|
|
970
|
27 Feb 2014 |
Konstantin Olchanski | Suggestion | runlog is "ugly" | > If I am not mistaken, the mhttpd.css is
hard coded (path/name) into the mhttpd.
|
|
|
973
|
28 Feb 2014 |
Andreas Suter | Suggestion | runlog is "ugly" | Understand me right, I mostly like the new
style, except the runlog as reported.
Attached you will find the diff's you were |
|
|
974
|
28 Feb 2014 |
Stefan Ritt | Suggestion | runlog is "ugly" | > If I am not mistaken, the mhttpd.css is
hard coded (path/name) into the mhttpd.
|
|
|
977
|
07 Mar 2014 |
Stefan Ritt | Suggestion | runlog is "ugly" | I put mhttpd.css and mhttpd.js into the ODB,
so every experiment can change it. I put
also Andreas' modifications of the CSS file |
|
|
1273
|
18 Apr 2017 |
Andreas Suter | Bug Report | run start/stop oddity | I stumbled over an oddity which I would like
to understand better. Here the
boundaries:
|
|
|
1288
|
02 May 2017 |
Konstantin Olchanski | Bug Report | run start/stop oddity |
I should really get around to fix this junk
error message:
|
|
|
2633
|
22 Nov 2023 |
Pavel Murat | Forum | run number from an external (*SQL) db? | Dear MIDAQ developers,
I wonder if there is a non-intrusive way |
|
|
2634
|
22 Nov 2023 |
Ben Smith | Forum | run number from an external (*SQL) db? | > I wonder if there is a non-intrusive way
to have an external (wrt MIDAS)*SQL database
|
|
|
2635
|
22 Nov 2023 |
Stefan Ritt | Forum | run number from an external (*SQL) db? | > - multiple subdetectors are taking test
data during early commissioning
> - a postgres db is a single sorce of run |
|
|
2636
|
01 Dec 2023 |
Pavel Murat | Forum | run number from an external (*SQL) db? | > > - multiple subdetectors are taking test
data during early commissioning
> > - a postgres db is a single sorce of |
|
|
2638
|
02 Dec 2023 |
Stefan Ritt | Forum | run number from an external (*SQL) db? | > Stefan, I don't think we're talking 'mis-use'
- rather different subdetectors being commisisoned
|
|
|
2640
|
02 Dec 2023 |
Pavel Murat | Forum | run number from an external (*SQL) db? | >
> If you go in this direction, there is an
alternative to what Ben wrote: Use the sequencer |
|
|
2642
|
03 Dec 2023 |
Pavel Murat | Forum | run number from an external (*SQL) db? | > - how does one communicate with an external
shell script from MSL ?
|
|
|
2643
|
04 Dec 2023 |
Stefan Ritt | Forum | run number from an external (*SQL) db? | > - how does one communicate with an external
shell script from MSL ? I looked at the MIDAS
Sequencer page
|
|