Gustin Johnson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Martin Horn wrote:
>
>> Hi All again,
>>
>> I am also not able to run the rtirq script on my 64studio install:
>>
>> r...@64studio:~/rtirq-20090920# sh rtirq.sh
>> rtirq.sh: 65: source: not found
>> rtirq.sh: 74: Syntax error: "(" unexpected
>>
>
> Don't use sh to execute the script. sh is actually dash on a Debian
> system. Instead, make the script executable with "chmod u+x rtirq.sh"
>
> To execute simply put ./ in front.
> sudo ./rtirq.sh start
>
> By default the file is marked as executable when you untar/gzip it.
>
>
>> Here is the relevant part of the script:
>>
>> # Check for existence of needed config file and read it.
>> RTIRQ_CONFIG=/etc/sysconfig/rtirq
>> [ -r ${RTIRQ_CONFIG} ] || RTIRQ_CONFIG=/etc/default/rtirq
>> [ -r ${RTIRQ_CONFIG} ] || RTIRQ_CONFIG=/etc/rtirq.conf
>> [ -r ${RTIRQ_CONFIG} ] || {
>> ��� echo "`basename $0`: ${RTIRQ_CONFIG}: not found."
>> ��� [ "${RTIRQ_ACTION}" = "stop" ] && exit 0 || exit 6
>> }
>>
>
> Basically the problem is that script is using bash specific syntax that
> dash does not support. Using sh to execute scripts is a bad habit.
Rtirq should automatically run without any problem on startup, just copy
the needed files to the correct places:
$ sudo mv /unknown_path/rtirq.conf /etc/default/rtirq
$ sudo mv /unknown_path/rtirq.sh /etc/init.d/rtirq
See Rui's answer, he's the author of rtirq:
-------- Original Message --------
Subject: Re: Question about rtirq
Date: Sat, 26 Dec 2009 21:54:51 +0000
From: Rui Nuno Capela <[email protected]>
To: Ralf Mardorf <[email protected]>
CC: 64 Studio Users <[email protected]>
References: <[email protected]>
<[email protected]> <[email protected]>
On 12/26/2009 09:41 PM, Ralf Mardorf wrote:
> Rui Nuno Capela wrote:
>> On 12/26/2009 11:45 AM, Ralf Mardorf wrote:
>>
>>> Hi Rui :)
>>> hi 64 Studio list :)
>>>
>>> the default kernel for 64 Studio is the 2.6.29-1-multimedia-amd64. I
>>> like to be able to run the default kernel and the latest 2.6.31.6-rt19.
>>>
>>> I guess I need to upgrade rtirq to be fine with the latest kernel? Will
>>> it be fine with 2.6.29 too?
>>>
>>> Do I need to include both scripts in one script?
>>> quasi ...
>>> if uname -r = 2.6.29 then go on with old script
>>> if uname -r = 2.6.31 then go on with new script
>>>
>>>
>>
>> you can and should run the latest rtirq
>> (http://www.rncbc.org/jack#rtirq) -- it works on all PREEMPT_RT enabled
>> kernels.
>>
>> kernel >= 2.6.31-rt just adds some niceties for your discretion eg. you
>> can pin point which devices in particular get higher priority, even
>> though that device is sharing the same irq line with others which won't
>> get touched.
>>
>> cheers
>
> What is rtirq.spec for?
>
rpm specification file; used to build the rpm package
> Should I only move rtirq.conf to /etc/default (there it is for 64
> Studio, renamed to rtirq) and move rtirq.sh to /etc/init.d (renamed to
> rtirq) or is there something additional to do by using rtirq.spec?
>
you have no use for rtirq.spec on debian based systems
byee
--
rncbc aka Rui Nuno Capela
[email protected]
_______________________________________________
64studio-users mailing list
[email protected]
http://lists.64studio.com/mailman/listinfo/64studio-users
