| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
1621
|
16 Jul 2019 |
Lukas Gerritzen | Info | Limitations of MSL | Dear Stefan,
another thing which does not work is the |
|
|
1620
|
12 Jul 2019 |
Konstantin Olchanski | Bug Report | rework of mhttpd configuration | > > - this will activate the mhttpd password
protection, so one would have to define a
username and password
|
|
|
1619
|
11 Jul 2019 |
Stefan Ritt | Bug Report | rework of mhttpd configuration | > - this will activate the mhttpd password
protection, so one would have to define a
username and password
|
|
|
1618
|
11 Jul 2019 |
Konstantin Olchanski | Bug Report | rework of mhttpd configuration | > Ubuntu LTS 18.04 does not run a restrictive
firewall and access to mhttpd ports 8080
and 8443 is not
|
|
|
1617
|
11 Jul 2019 |
Konstantin Olchanski | Bug Report | problems with the default mhttpd configuration, also elogd | > It turns out that unlike CentOS-7, Ubuntu
LTS 18.04 does not run a restrictive firewall
> and access to mhttpd ports 8080 and 8443 |
|
|
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.
|
|
|
1615
|
11 Jul 2019 |
Konstantin Olchanski | Bug Report | Header files missing when trying to compile rootana, roody and analyzer | > > You can confirm that you are linking against
the correct ROOT by running cmake with VERBOSE=1
> > and examine the linker command line to |
|
|
1614
|
11 Jul 2019 |
Konstantin Olchanski | Bug Report | Frontend killed at stop of run | > Wed Jul 10 06:23:58 2019 [mhttpd,ERROR]
[system.c:4580:ss_recv_net_command,ERROR]
timeout receiving network command header
|
|
|
1613
|
11 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | > > ... finding a current midas.log file
>
> On the "help" page, see "midas.log".
|
|
|
1612
|
11 Jul 2019 |
Stefan Ritt | Bug Report | Header files missing when trying to compile rootana, roody and analyzer | > You can confirm that you are linking against
the correct ROOT by running cmake with VERBOSE=1
> and examine the linker command line to |
|
|
1611
|
10 Jul 2019 |
Konstantin Olchanski | Bug Report | Header files missing when trying to compile rootana, roody and analyzer | >> [hh19285@it038146 ~]$ which root-config
> /software/root/v6.06.08/bin/root-config
> [hh19285@it038146 ~]$ root-config --cflags
|
|
|
1610
|
10 Jul 2019 |
Konstantin Olchanski | Bug Report | Frontend killed at stop of run | > ... finding a current midas.log file
On the "help" page, see "midas.log".
|
|
|
1609
|
10 Jul 2019 |
Stefan Ritt | Bug Report | mhttpd crashes when including nonexistent script in msequencer | The bug has been fixed. It was actually in
the mxml library. So you have to go to the
midas/mxml
|
|
|
1608
|
10 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | > > > >
> > > > For SIGKILL, my gdb reports "Program
terminated with signal SIGKILL, Killed." |
|
|
1607
|
10 Jul 2019 |
Hassan | Bug Report | Header files missing when trying to compile rootana, roody and analyzer | Hi, we have now done a clean install of Root
and after some dynamic linking we have been
able to make Rootana and analyzer. However |
|
|
1606
|
09 Jul 2019 |
Stefan Ritt | Info | Limitations of MSL | > Yes, this has been the way to do it for
years...
|
|
|
1605
|
08 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | > > >
> > > For SIGKILL, my gdb reports "Program
terminated with signal SIGKILL, Killed." |
|
|
1604
|
08 Jul 2019 |
Konstantin Olchanski | Bug Report | Frontend killed at stop of run | > >
> > For SIGKILL, my gdb reports "Program
terminated with signal SIGKILL, Killed." |
|
|
1603
|
08 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | > > > run the frontend inside gdb and post
the stack trace after the crash?
> > >
|
|
|
1602
|
08 Jul 2019 |
Konstantin Olchanski | Bug Report | Frontend killed at stop of run | > > run the frontend inside gdb and post the
stack trace after the crash?
> >
|
|