On Wed, May 21, 2008 at 8:37 AM, James B. Byrne <byrnejb at harte-lyne.ca> wrote: > > This indeed turned out to be an SELinux policy problem which I have since > resolved. Whoa, whoa, whoa, nice shooting, Tex! (Ghostbusters) Not so fast - please post the solution, too, for posterity (and those of us who don't use SELinux but might, someday, in the not too distant far future...). Thanks. mhr