On 1/29/16 3:54 PM, Till Straumann wrote:
> These would be my arguments:
>
> - it doesn't make much sense to use RT scheduling w/o memory locking
> as this would hurt determinism. Thus, selectively disabling
> mlockall() is a poor work-around.
Hi, Till.
True, but I think that just means the toggle is for the wrong thing.
It sounds like there should be a toggle for RT, not mlockall. The RT
toggle would enable both the RT scheduling and the mlockall.
> - the code uses these features (RT scheduling + mlockall) *only*
> if you give it sufficient privilege to use them. If it has the
> privileges then the code assumes you want it to use them.
This is perhaps the real issue: the code assumes it should use
something just because it has sufficient privileges to do so. If I'm
understanding things correctly, if I want to run something as root (or
with certain capabilities) *without* RT, I can't do it. But a toggle
for RT would allow me to do it.
Regards,
Lewis
- Replies:
- Re: set-user-id root and EPICS 3.15 Maren Purves
- Re: set-user-id root and EPICS 3.15 Till Straumann
- References:
- set-user-id root and EPICS 3.15 Gerry Swislow
- RE: set-user-id root and EPICS 3.15 Mark Rivers
- Re: set-user-id root and EPICS 3.15 Ralph Lange
- Re: set-user-id root and EPICS 3.15 Andrew Johnson
- Re: set-user-id root and EPICS 3.15 Till Straumann
- Navigate by Date:
- Prev:
Re: set-user-id root and EPICS 3.15 Michael Davidsaver
- Next:
Re: set-user-id root and EPICS 3.15 Maren Purves
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: set-user-id root and EPICS 3.15 Michael Davidsaver
- Next:
Re: set-user-id root and EPICS 3.15 Maren Purves
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
|