Good Morning,
> So I can live with the vince thing, thats kinda funny,,,
Vince is the name of our package builder. Seeing as its not really a
good idea to let everyone have root access, he builds the packages as
himself. Apologies if this causes you concern.
>
> I used the tar.gz this time so that I could install the addons for openssl,
>
> I followed the instructions to the letter as I always do,
>
> and now I cant even login to the server, a "blip" comes up so quickly that
> I cant read the whole thing, but what I think I get a glimpse of is
>
> vsd_priv access
This error has been seen before, and was discussed only a couple of days
ago. To get to this situation, the only way found was to have
accidentially installed the rpms in /usr/share/freevsd/pkgs on the
hosting server, but if you have followed the instructions to the letter,
this can't have possibly have happened, so if you could give me a more
detailed account of your installation process I shall endeavour to help
you out, as if this is a bug, I would have called it a show stopper.
> I dont mean to come off sounding rude or ignorant but dont you people test
> this stuff before you call it a release ?
This version has gone through intense testing, admittedly the majority
of it has been mod_bind related, but I've lost count of the number of
times I personally have un/installed this release over the last couple
of days, and have not come accross any login problems.
> further to my list of gripes I noticed that the default path that the
> tar.gz installs the binary and config files is not even native to RH
The paths set by a source install follow structure traditionally
associated with installations from source on any *NIX system. It is
usually presumed that if you are installing something from source then
you would only want it on your local machine to start with (whilst you
test it), and only make it availble to the other users on that machine
(or any other machine that may be mounting its /usr directory from the
machine in question), when you are happy with it. Thus, not installing
it into the default path, but instead mirroring the structure under
/usr/local makes sense.
I apologise for the grief you have suffered, and hope that the beer was
cold, but a call for help would have been better recieved, and if after
that it still doesn't work, then I feel that you would be right in
publicly expressing your feelings.
Damion.
