Piotr Pokora schrieb:
Hi!
Hi!
I just updated my Suse server to 2.8, and have had two issues with it:
-like on my Debian machines, I run a self-compiled Midgard with prefix
set to /usr/local. Unfortunately this always causes "Midgard not
initialized!" errors when doing PEAR upgrades, because it looks for the
config file in /etc/midgard/conf.d, but make install created it in
/usr/local/etc/midgard/conf.d. I worked around this by creating a
symlink, but it would be nice if this could either be auto-detected or
if there was a config option to influence it.
Have a look at /usr/local/include/midgard/midgard_config_auto.h
and at /usr/include/midgard/midgard_config_auto.h ( if exists ).
This file defines your local setup configuration.
Either you have midgard installed twice or there's some issue with
MIDGARD_LIB_PREFIX defined in this header file.
I just looked it up and the file looks ok:
cat /usr/local/include/midgard/midgard_config_auto.h
#define MIDGARD_LIB_PREFIX "/usr/local"
#define MIDGARD_GLOBAL_SCHEMA "/usr/local/share/midgard/MgdObjects.xml"
/* Define directory path where all 'local' schemas are stored.
* Global schema is basic midgard schema , while local ones are defined
* per virtual host or per application.
*/
#define MIDGARD_LSCHEMA_DIR "/usr/local/share/midgard/schema"
#define MIDGARD_SHARE_DIR "/usr/local/share/midgard"
#define MIDGARD_PARSER_HACK_EVAL 1
#define MIDGARD_PARSER_DEBUG 0
#define HAVE_CACHE_FIX 1
#define HAVE_MIDGARD_MULTILANG 1
#define HAVE_MIDGARD_PAGE_OWNER 1
#define HAVE_MIDGARD_VC 1
#define HAVE_MIDGARD_QUOTA 1
#define HAVE_MIDGARD_PAGELINKS 0
#define MIDGARD_PREPARSER_FUDGE_ARRAYS 0
#define MIDGARD_PHP_REQUEST_CONFIG_BUG_WORKAROUND 1
#define MIDGARD_LIB_VERSION "1.8.4.1"
#define MIDGARD_LIB_VERSION_STRING ""
locate midgard_config_auto.h reveals that I have three extra copies of
that file, but they are all in the directories of the unpacked Midgard
sources, so they shouldn't be a problem (at least that's what I hope)
I got around this by setting MidgardUsername and MidgardPassword in the
config file (although the comments say "You shouldn't use configuration
below in real life"). Mysteriously, this didn't happen on my Debian
machines, because there, the values were already present (but I didn't
set them manually).
So, I don't know if this is an issue with me messing up config files or
if Midgard should somehow take care of this, but at least the comment is
a bit misleading..
Datagard checks if values are correct and set them if needed. Please
double check if you do not have midgard installed twice with different
prefixes.
I'm not really sure how to do this, but when I try "locate libmidgard" I
get a lot of source files and
/usr/local/lib/libmidgard.a
/usr/local/lib/libmidgard.la
/usr/local/lib/libmidgard.so
/usr/local/lib/libmidgard.so.9
/usr/local/lib/libmidgard.so.9.0.0
locate midgard-config returns the following:
/home/flack/Midgard_AllinOne-1.8.4/midgard-core-1.8.4/man/midgard-config.1
/home/flack/Midgard_AllinOne-1.8.4/midgard-core-1.8.4/midgard-config
/home/flack/Midgard_AllinOne-1.8.4/midgard-core-1.8.4/midgard-config.in
/home/flack/Midgard_AllinOne-1.8.2.2/midgard-core-1.8.2.2/man/midgard-config.1
/home/flack/Midgard_AllinOne-1.8.2.2/midgard-core-1.8.2.2/midgard-config
/home/flack/Midgard_AllinOne-1.8.2.2/midgard-core-1.8.2.2/midgard-config.in
/home/flack/Midgard_AllinOne-1.8.4.1/midgard-core-1.8.4.1/man/midgard-config.1
/home/flack/Midgard_AllinOne-1.8.4.1/midgard-core-1.8.4.1/midgard-config
/home/flack/Midgard_AllinOne-1.8.4.1/midgard-core-1.8.4.1/midgard-config.in
/usr/local/bin/midgard-config
/usr/local/share/man/man1/midgard-config.1
I don't know if the old source files can cause problems, but apart from
them, the system looks clean
Bye,
Andreas
Piotras
_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user
_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user
