Right now, Obsequieummeum requires that the mysql server be running on
the same machine as Obseeqeum. You'll get that message if this is not
the case. You can manually edit the sources at each restart to fix
this, but it's far from clean. At this very moment, though, I'm trying
to make that not the case - I just hacked my own fix into the latest CVS
sources. If my patch works, I'll post it here shortly ... a 486/66
w/16MB RAM is no speed daemon ...
Luckily, the source is fairly clean (for being Perl code and all <g>) so
I suspect it'll at least mostly work. I remember seeing a problem in
one of the CGI scripts that I may have to look into but as long as I get
it to start and to broadcast I'll post it. Let me know what CGI has the
problem, if indeed it does, and I'll post a second patch shortly ...
Chris
Rob's mailing list account wrote:
>
> I am having a problem similar to what others have encountered, I have read
> the archives of this list, and have seen the problem in them, but i can
> not find a resolve that works for me.
>
> The scene:
> I have a RedHat 7.0 box, fully patched and updated to the latest from
> RedHat. I have compiled libshout, along with the patch supplied on the obs
> website.
>
> I have also compiled and installed obs.
>
> When I go to http://myurl/obs - I get 4 panes complaining about not being
> able to connect through mysql.sock
>
> When i run obsd -d -n, it hangs on:
>
> ----- Obsequieum started Tue Jan 23 14:03:06 2001
>
> I have checked, and I am sure that the mysql server is working properly,
> as per the archives of this mailing list.
>
> What have I missed? What am I doing wrong, or what do I need to change?
>
> Thanks -
>
> Rob Hoyle
>
> _______________________________________________
> Obs-dev mailing list
> [EMAIL PROTECTED]
> http://www.freeamp.org/mailman/listinfo/obs-dev
--
Oh My God! They Killed init! You Bastards!!
make install; not war
_______________________________________________
Obs-dev mailing list
[EMAIL PROTECTED]
http://www.freeamp.org/mailman/listinfo/obs-dev
