Midcom permission struggle

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,=20

I have an interesting setting forced upon me by our new provider STRATO =
(major one in Germany)
Looks like they use su_php for enforcing their access-policy and=20
Probably that is also the problem i am struggeling with...

I can get "Normal" Aegir clients up in no time, just have to make sure =
the lines like
- --- snip ---
php_admin_value open_basedir /users_public_html_base_dir/cache:\
/usr/local/lib/php:\
/tmp:\
/usr/lib/apache2:\
/var/lib/aegir/cvs:\
/var/local/lib/midgard/blobs/midgard:\
/var/www/blobs
- --- snap ---

Are set in my Vhost.conf

Now with midCom this seems to pose a bit of a problem...

Just adding=20
/usr/local/share/midgard/midcom/midcom-static:\
/usr/local/share/midgard/midcom/midcom:\

To that value didnt work, so i am unable to access the flatfile-cached =
php-scripts...

Oh by the way, this is an a SuSE 9.3 machine.
I did find a php4-dba rpm that installed without errors by using yast, =
but it is not "exactly" the same version.
Maybe the problems come from this????
Are there any official php4-dba RPMs out there fitting a "normal" SuSE =
9.3=20
- - m-p.org didnt list any sources on that...

As always, thankful for any help,

Alex aka med-men
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)

iD8DBQFD2S426ByBlKPys/0RAsawAKCWR9tEgLrCZeLFGroj2EVTX4EvPQCg+XY5
u8TNFdDQHEju3xwLdHDlb+U=3D
=3DH2hp
-----END PGP SIGNATURE-----