Running httpd as a user
I build websites for a living. I'd like to get /usr/sbin/httpd running as a regular user. I've setup a directory with a simple httpd.conf on my F15 install. When it starts up, I get a single message in the error log: [Fri Jul 01 23:36:53 2011] [notice] SELinux policy enabled; httpd running as context unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 I've poked at Google for a while but I don't see a way to tune SELinux to allow myself to run httpd. Any pointers? Turning SELinux off is an option, but I'd rather learn more about how SELinux really works so that I can take advantage of its benefits. -- Jonathan Gardner jgard...@jonathangardner.net -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: FluidSynth configuration
On Fri, Dec 10, 2010 at 4:05 AM, Rodolfo Alcazar Portillo nosp...@gmail.com wrote: On Thu, 2010-12-09 at 14:46 -0800, Jonathan Gardner wrote: I installed FluidSynth and qsynth on my F13 / KDE install. When qsynth comes up, it asked me to do some additional configuration by modifying /etc/security/limits.conf to add: @audio - rtprio 100 @audio - nice -10 After I made the changes and restarted it, it then asked me to add myself to the audio group. I'm not sure what I did or why this needs to be done. I'd appreciate a pointer or some better advice. Logging in with my new group showed that qsynth was working, although I have yet to hear any sound from it. I tested with pianobooster, musescore, firefox on a site with MIDI, and a few other MIDI apps I thought would make MIDI sound. (I haven't logged out and back in through X yet. I'd prefer not to have to do so.) Am I doing something wrong? Should I go talk with the FluidSynth guys about my particular situation? Do we need to tweak the fluidsynth RPM? (I'm volunteering to help.) Jonathan, Im' not sure about Fedora's right config concerning fluidsynth, but this is how I did (still working on F14). 1. Config some defaults: # usermod -a -G audio rodolfoap # requires relogin # vi /etc/security/limits.conf ... # End of file �...@audio - rtprio 99 �...@audio - nice -19 �...@audio - memlock 1443915 2. Disable pulseaudio $ echo autospawn = no ~/.pulse/client.conf $ pulseaudio -k Then, start qjackctl. Furthermore, you can start qsynth. I use BIAB and Finale, so then I start it with wine, config the midi port and start playing. I wish we can find some better and smooth fedora way. On f13 I needed the planetccrma version of qjackctl, I think, but Im not sure, so I installed the repo and updated qjackctl. Thanks for sharing your experience. I wish I understood better what FluidSynth, PulseAudio, and these other tools were really doing. I'm going to do some research on these things. -- Jonathan Gardner jgard...@jonathangardner.net -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
FluidSynth configuration
I installed FluidSynth and qsynth on my F13 / KDE install. When qsynth comes up, it asked me to do some additional configuration by modifying /etc/security/limits.conf to add: @audio - rtprio 100 @audio - nice-10 After I made the changes and restarted it, it then asked me to add myself to the audio group. I'm not sure what I did or why this needs to be done. I'd appreciate a pointer or some better advice. Logging in with my new group showed that qsynth was working, although I have yet to hear any sound from it. I tested with pianobooster, musescore, firefox on a site with MIDI, and a few other MIDI apps I thought would make MIDI sound. (I haven't logged out and back in through X yet. I'd prefer not to have to do so.) Am I doing something wrong? Should I go talk with the FluidSynth guys about my particular situation? Do we need to tweak the fluidsynth RPM? (I'm volunteering to help.) -- Jonathan Gardner jgard...@jonathangardner.net -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Helping with Hardware
I've been using Linux for over 10 years, and I've been with Red Hat since the 7.2 days and I've been using Fedora since it was first announced. I've never gotten around to dealing with hardware issues seriously, instead content to let things be and just hope the next release fixes the problems I see. (It's surprising how well wait-and-upgrade works as a strategy in Fedora!) My question is, how can I contribute to Fedora and thus the larger Linux community through getting my hardware better supported? Or is it just not suitable for a lay-person who knows how to program but doesn't already have a background in these things to get involved? Do I need to set up my system so either I use it for work or I use it to tinker with the hardware but not both at the same time? -- Jonathan Gardner jgard...@jonathangardner.net -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Helping with Hardware
On Tue, Dec 7, 2010 at 11:34 AM, Dr. Michael J. Chudobiak m...@avtechpulse.com wrote: On 12/07/2010 02:20 PM, Jonathan Gardner wrote: I've been using Linux for over 10 years, and I've been with Red Hat since the 7.2 days and I've been using Fedora since it was first announced. I've never gotten around to dealing with hardware issues seriously, instead content to let things be and just hope the next release fixes the problems I see. (It's surprising how well wait-and-upgrade works as a strategy in Fedora!) My question is, how can I contribute to Fedora and thus the larger Linux community through getting my hardware better supported? Or is it just not suitable for a lay-person who knows how to program but doesn't already have a background in these things to get involved? Do I need to set up my system so either I use it for work or I use it to tinker with the hardware but not both at the same time? File bugs, and read bugs, both in the Fedora bugzilla and upstream (for whatever project). Often, hardware bugs will end up as NEEDINFO because the developer doesn't have the right hardware. You can help fill that gap by supplying the requested logs and running tests. You learn a lot just by reading bug reports in your area of interest, even if they don't affect you directly. I will definitely do this. Install lots of *-debuginfo packages, so that crashing software supplies good backtraces. I imagine the process is this. (1) Use some software, watch it crash. (2) Install the debuginfo packages (3) Use it again til it crashes (4) File a bug report Right? If you feel adventurous, install rawhide on a spare computer, so you can file bugs early. Do not use rawhide on a must-work system. It WILL cause grief. The few times in the past where I did feel adventurous, it wasn't enough to get rawhide working at the time. I came really close when a particular version of Fedora didn't like my video card, but I found a way to manage. Buy cool hardware for developers, and for people who reply to you on mailing lists :-) Actually, this last idea doesn't sound too bad. With hardware so cheap nowadays, I might as well buy one for myself and three for some developers. It'd be cheaper than the time. ;-) Speaking of which, how does Fedora handle testing on hardware? Do we just rely on individual developers and testers running Rawhide, or is there a computer lab somewhere running umpteen different configurations of hardware? -- Jonathan Gardner jgard...@jonathangardner.net -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Re: Helping with Hardware
On Tue, Dec 7, 2010 at 12:35 PM, Alan Cox a...@lxorguk.ukuu.org.uk wrote: My question is, how can I contribute to Fedora and thus the larger Linux community through getting my hardware better supported? Or is it just not suitable for a lay-person who knows how to program but doesn't already have a background in these things to get involved? It depends a lot what the hardware is. If it's a variant of existing hardware that is badly supported or the like then even with no tech skills you can still be extremely helpful as a tester for anyone working on it, or to assist the actual maintainer in checking it works with that card variant for example. Is there some registry somewhere where we tell people what we are using and that we are willing to test? For the record, F13 on a Gigabyte 880GM-USB3 with a dual-core AMD Phenom II (that reportedly could be unlocked to quad-core). While I got dual-display working at 1920x1080 each, one of which is rotated. I don't have MIDI working, nor can I use the surround sound. I just have basic stereo. I had the fglrx driver working for a while, then it mysteriously stopped working with newer kernels and now the radeon driver works beautifully. Though not nearly as fast as the fglrx driver, at least I don't have white lines at the edge of the rotated monitor. -- Jonathan Gardner jgard...@jonathangardner.net -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Running xrandr for kdm and after login
I've been playing around with a dual-monitor setup on my F13 install. I can run a command like the following to get them to display properly: /usr/bin/xrandr --output DFP2 --auto --rotate left --output CRT1 --auto --pos 1080x420 I added the above line to /etc/kde/kdm/Xsetup. When I start the computer or log out, the kdm does start with both screens properly aligned, but the login box is too high on the CRT1 side so it is cut in half. I don't know how to fix where the login box shows up. Ideally, I'd like it to appear in the middle of the DFP2 screen. If someone has some tips, I'd appreciate it. I thought maybe it's getting confused with such a wide virtual space, so perhaps turning off CRT1 will get it to center it on DFP2 properly. I changed the line in /etc/kde/kdm/Xsetup to the following: /usr/bin/xrandr --output DFP2 --auto --rotate left --output CRT1 --off Now CRT1 is turned off, but the login box is nowhere to be seen on DFP2. Once I log in, it obviously preserves my xrandr configuration. I'd like to have it switch to dual-monitor mode, so I tried adding the following line to /etc/X11/xinit/Xsession, but that doesn't seem to run at all. As I've mucked with the files, I might have broken something. Now knetworkmanager isn't starting, although that may be a different problem. -- Jonathan Gardner jgard...@jonathangardner.net -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
