On Sun, Sep 26, 2010 at 3:22 PM, JD wrote:
> On 09/26/2010 10:04 AM, Tom H wrote:
>> On Sun, Sep 26, 2010 at 12:33 PM, JD wrote:
>>> I am trying to run a command in realtime mode just to see
>>> if it behaves any different as far as timings are concerned.
>>>
>>> Man page says:
>>>
>>> chrt - m
On 09/26/2010 06:04 PM, Gordon Messmer wrote:
> On 09/26/2010 12:22 PM, JD wrote:
>> $ sudo chrt 0 "./freq -s120 -u0 -r"
>> chrt: failed to set pid 0's policy: Invalid argument
>> $ sudo chrt 0 './freq -s120 -u0 -r'
>> chrt: failed to set pid 0's policy: Invalid argument
> 0 isn't valid for the d
On 09/26/2010 12:22 PM, JD wrote:
>
> $ sudo chrt 0 "./freq -s120 -u0 -r"
> chrt: failed to set pid 0's policy: Invalid argument
> $ sudo chrt 0 './freq -s120 -u0 -r'
> chrt: failed to set pid 0's policy: Invalid argument
0 isn't valid for the default policy (SCHED_RR). "chrt -m" displays the
mi
On 09/26/2010 10:04 AM, Tom H wrote:
> On Sun, Sep 26, 2010 at 12:33 PM, JD wrote:
>> I am trying to run a command in realtime mode just to see
>> if it behaves any different as far as timings are concerned.
>>
>> Man page says:
>>
>> chrt - manipulate real-time attributes of a process
>>
>> c
On Sun, Sep 26, 2010 at 12:33 PM, JD wrote:
> I am trying to run a command in realtime mode just to see
> if it behaves any different as far as timings are concerned.
>
> Man page says:
>
> chrt - manipulate real-time attributes of a process
>
> chrt [options] prio command [arg]...
> chrt [option
I am trying to run a command in realtime mode just to see
if it behaves any different as far as timings are concerned.
Man page says:
CHRT(1) Linux User’s Manual CHRT(1)
NAME
chrt - manipulate real-time attributes of a process
SYNOPSIS
chrt [options] prio command [arg]...
chrt [options] -p [
