gnump3d-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnump3d-devel] dependencies on default gnump3d.conf file


From: kracker
Subject: [Gnump3d-devel] dependencies on default gnump3d.conf file
Date: Sun, 26 Mar 2006 14:47:25 -0600

Hey Everybody,

Alternately titled as GNUMP3d dependencies on default
/etc/gnump3d/gnump3d.conf configuration file in a multi
server/instance setup.

I ran into this bug a while back and ignored it as small negative
feature but more and more I find this behavior as part of a design.

I run 2 gnump3d servers on the same machine. to do this I had to hack
a number of features to allow duplicate instantiation with different
setting.

1. /size uri requires the default /etc/gnump3d/gnump3d.conf file to exist.

The Configuration File + Multi instances

The problem with this is that to get two instances of the server to
run I found I had to remove the default conf file and replace it with
a custom named copy for each server.

/etc/gnump3d/gnump3d.music.conf
/etc/gnump3d/gnump3d.books.conf

Then I would launch the server by hand passing the --CONFIG parameter
each time.
But it seems that /size (and other features) does not know to respect
or use the passed configuration file variable :\

2. I also ran into a problem with the search / index features in a
similar fashion
It seems gnump3d-index does not allow the passing of --CONFIG
parameter, am I wrong on this? I sure think it should, as for
multi-instance configurations need to specific which instance to index
(I hack a custom script to get around this bug as well, though I guess
I should consider submitting a patch).

3. I think I finally ran into having to create files by hand in
/var/log/gnump3d/ and /var/cache/gnump3d/

A. Like /var/log/gnump3d/access_instance-name.log or
/var/log/gnump3d/error_instance-name.log files by hand setting
permission correctly to get the server started, they would not create
themselves :\

B. Like /var/cache/gnump3d/ I had to create
/var/cache/gnump3d/serving.instance-name/

I got it all to work, mostly, I just wonder if other people think
these are reasons to extend the code with patches to support this
better out of the box. An some of what I bring up might make be better
served up in a HOWTO for the docs.

I don't expect anything, just thought I would point out what I saw,
right or wrong.

//kracker
Godsmack - I Stand Alone




reply via email to

[Prev in Thread] Current Thread [Next in Thread]