One of the annoying things about running qjackctl on a fresh Fedora install is that you have to remember to edit /etc/security/limits.conf as per /usr/share/doc/jack-audio-connection-kit-0.102.20/README.Fedora or else it doesn't work at all. I'm wondering if there's something we can do to make this easier.
One idea is to wrap qjackctl in a script that essentially parses limits.conf to see that everything is set up properly for $USER. If not, it pops up a dialog box explaining the problem and offering to edit it for $USER. If the user agrees, it runs a consolehelper app to fix up limits.conf and continues on with qjackctl.
I just can't imagine how a new user gets anything running without stumbling upon that README.Fedora file or searching for help on the web.
Good idea? Bad idea? Suggestions?
AG
Anthony Green wrote:
One of the annoying things about running qjackctl on a fresh Fedora install is that you have to remember to edit /etc/security/limits.conf as per /usr/share/doc/jack-audio-connection-kit-0.102.20/README.Fedora or else it doesn't work at all. I'm wondering if there's something we can do to make this easier.
One idea is to wrap qjackctl in a script that essentially parses limits.conf to see that everything is set up properly for $USER. If not, it pops up a dialog box explaining the problem and offering to edit it for $USER. If the user agrees, it runs a consolehelper app to fix up limits.conf and continues on with qjackctl.
I just can't imagine how a new user gets anything running without stumbling upon that README.Fedora file or searching for help on the web.
Good idea? Bad idea? Suggestions?
I was about to say "just let the install scripts do the change in the background, without asking, and be done with it" but then I remembered you have to specify the user name(s).
So, yeah, good idea, no doubt. Just make sure to distinguish between installs being performed via an xterm running in an X session, and a plain-text session via ssh, or via a local text console - the user will have to be prompted differently in each case.
The question is - should qjackctl do the change, or jack-audio-connection-kit? I can see arguments leaning each way.
On Sun, 2007-01-07 at 11:14 -0800, Florin Andrei wrote:
I was about to say "just let the install scripts do the change in the background, without asking, and be done with it" but then I remembered you have to specify the user name(s).
So, yeah, good idea, no doubt. Just make sure to distinguish between installs being performed via an xterm running in an X session, and a plain-text session via ssh, or via a local text console - the user will have to be prompted differently in each case.
If we do it around qjackctl, then we don't have to worry about this, since we're only talking about GUI console users.
The question is - should qjackctl do the change, or jack-audio-connection-kit? I can see arguments leaning each way.
Hand-holding for command line users can be counter-productive. Wrapping qjackctl also solves the problem you describe above.
It would be nice to have this for Fedora 7, but I can't volunteer to write it any time soon. I just thought I'd write it down while I was thinking of it, and would be really happy if somebody else had time to do this...
AG
On Sun, 2007-01-07 at 06:27 -0800, Anthony Green wrote:
I just can't imagine how a new user gets anything running without stumbling upon that README.Fedora file or searching for help on the web.
Good idea? Bad idea? Suggestions?
We really need to put together a decent "How to get started" guide on the wiki. Well, and a SIG page period. ;P Look at what the Games SIG is doing. And the CCRMA@home docs is a good template as well. I've been wanting to do this but I'm in need of round tuits...
Has jack's README.Fedora been changed to recommend a memlock of 131072 (128mb) or so? 50000 is really not enough. Its been like a year now and 131072 has served me well.
Not sure how we can do out-of-the-box setup that will be acceptable distribution-wide. Perhaps we can do it debian style, add yourself to the "jackuser" group if you want real time perms.
On Sun, 2007-01-07 at 15:09 -0600, Callum Lerwick wrote:
Has jack's README.Fedora been changed to recommend a memlock of 131072 (128mb) or so? 50000 is really not enough.
No, I don't think so. File a bug I guess.
Not sure how we can do out-of-the-box setup that will be acceptable distribution-wide. Perhaps we can do it debian style, add yourself to the "jackuser" group if you want real time perms.
Oh, I like this idea. So the jack-audio-connection-kit %post would create a jackuser group, and add the following to limits.conf...
@jackuser - rtprio 20 @jackuser - memlock 131072
Then we could still have a wrapper around qjackctl to see if the user is a member of the jackuser group and give them the option of joining if not (via consolehelper app).
Does that sound right?
AG
Anthony Green wrote:
Oh, I like this idea. So the jack-audio-connection-kit %post would create a jackuser group, and add the following to limits.conf...
@jackuser - rtprio 20 @jackuser - memlock 131072
Then we could still have a wrapper around qjackctl to see if the user is a member of the jackuser group and give them the option of joining if not (via consolehelper app).
Does that sound right?
Perfect.
On Sun, 2007-01-07 at 15:06 -0800, Florin Andrei wrote:
Does that sound right?
Perfect.
I've filed a bug for adding the jackuser group...
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221785
AG
On Sun, 2007-01-07 at 14:18 -0800, Anthony Green wrote:
Oh, I like this idea. So the jack-audio-connection-kit %post would create a jackuser group, and add the following to limits.conf...
@jackuser - rtprio 20 @jackuser - memlock 131072
Modifying other packages config files in %post is evil hackery that should be avoided at all costs. As we're entering the grand new era of the Unified Nation of Fedora, we should be able to push to have the proper settings in limits.conf to begin with....
On Mon, 2007-01-08 at 16:41 -0600, Callum Lerwick wrote:
On Sun, 2007-01-07 at 14:18 -0800, Anthony Green wrote:
Oh, I like this idea. So the jack-audio-connection-kit %post would create a jackuser group, and add the following to limits.conf...
@jackuser - rtprio 20 @jackuser - memlock 131072
Modifying other packages config files in %post is evil hackery that should be avoided at all costs. As we're entering the grand new era of the Unified Nation of Fedora, we should be able to push to have the proper settings in limits.conf to begin with....
I agree...
What I have done in the past (have not done it yet for fc6 as I have not released a low latency kernel) is to publish pam packages in Planet CCRMA so that things work "out of the box" for Planet CCRMA users. A lot less than optimal but the only way I could get things to work with no "hacking" of configuration files, etc, etc.
-- Fernando
On Sun, 2007-01-07 at 15:09 -0600, Callum Lerwick wrote:
On Sun, 2007-01-07 at 06:27 -0800, Anthony Green wrote:
I just can't imagine how a new user gets anything running without stumbling upon that README.Fedora file or searching for help on the web.
Good idea? Bad idea? Suggestions?
We really need to put together a decent "How to get started" guide on the wiki. Well, and a SIG page period. ;P Look at what the Games SIG is doing. And the CCRMA@home docs is a good template as well. I've been wanting to do this but I'm in need of round tuits...
I did make a start at this then got side tracked:
http://www.passback.co.uk/music/fedora-music-intro/
I really should get round to finishing the other parts.
Keith.
-
Anthony Green -
Callum Lerwick -
Fernando Lopez-Lezcano -
Florin Andrei -
Keith Sharp