I get," The account is not currently available."
But this happens on good and bad configuration. The system it works on gives
me this error too..
Any other suggestion? The only difference I see is, in production I am using
mod_perl 1.99
On Tue, Mar 11, 2008 at 1:55 AM, Philippe M. Chiasson <[EMA
in a given situation we get xml data POSTed to our server, much alike RPC
calls (actually they're a number of http (webdav) requests).
A (mod_perl) Fixuphandler traps these requests, parses the xml, and (should)
from there on issue all requests to our server.
It seemed quite logical to (dynamical
Hi,
Anybody got any experiences of mod_perl on RHEL5?
The rpms in RHN suggest versions of:
mod-perl 2.0.2
apache 2.2.3
perl 5.8.8
which are reasonable enough (and it's not the pre-release mp2 problem that
RHEL4 had!)
However in the past there have been plenty of posts suggesting that Redhat
Mag Gam wrote:
I get," The account is not currently available."
That account has a disabled shell
$> su apache -s `which sh` -c '/bin/ls /tmp/.s.PGSQL.5432'
Look at the permissions on both /tmp and /tmp/.s.PGSQL.5432
$> ls -ld /tmp
$> ls -l /tmp/.s.PGSQL.5432
--
Philippe M. Chiasson G
Carl Johnstone wrote:
Hi,
Anybody got any experiences of mod_perl on RHEL5?
The rpms in RHN suggest versions of:
mod-perl 2.0.2
apache 2.2.3
perl 5.8.8
which are reasonable enough (and it's not the pre-release mp2 problem
that RHEL4 had!)
However in the past there have been plenty of posts
