Re: [cobalt-users] moving users from group to another group

[Jeff Lasman <jblists@xxxxxxxxxxxxx>]

Julius wrote:

> From then on the GUI has
> slowly been 'corrupted' with faulty entries.

Since the gui is powered by the PostgreSQL database my guess is you're
saying, in other words, that the database IS corrupted.

> Basically this is what I need to do;
> 1. Change to httpd.conf back to the orignal state
> (to what the RaQ ui created it as)

You should already have this on your RaQ as httpd.conf.master.

> 2. Drop the entry in postgres's vsite table which points
> this to site1 or the default site (I need to decide on that)
> 3. Re-run meta-verify and probably check virtusertable
> and maybe shadow and password files for wrong group entries
> for some user (the ones created after or during the time
> the faulty postgres existed, some are in group 112, while
> they should be in 100).

That sounds pretty straightforward; is something keeping you from doing
it?

> > You're using a Raq in an environment it really isn't designed for;
> > that's okay, but it may cause you "issues" downstream.
> 
> Well, I've done it before, with a RaQ3, and never
> had any problems with it running webmail and email.
> (in fact; you will not find a smarter solution for the same price).
> I don't see why a RaQ4i could not be used as a dedicated
> webmail and email server. You can patch things along the way,
> and never have issues downstream. So far it's running like
> a charm, by the way, no problems whatsoever anywhere, no
> strange memory leaking, none of that. The only problem
> is the admin GUI not being able to change site settings
> (and therefore not being able to add users or email-aliases).

Okay, so it should run.  There's no huge difference between the RaQ3 and
RaQ4 GUIs, what works on one should work on the other.

> I don't think it will be soon, http://www.ams-ix.net/news.html
> not all bb-providers are that confident, so they cut off
> their connection to KPNQwest's network.

So you could just move the server or set up another, right?

> Linux is not a Cobalt RaQ4i. They sure don't do it in a way
> that each user has a correct entry in the postgres database.

Okay, I'll rephrase myself:  There are a few of us right here, on
cobalt-users, who do this work all the time.

> Well, that is what I'm doing, so your point is?

Excuse me; it didn't seem like you were doing it; you've been posting
for days now, and this is something that could have been done in a few
hours, from what you say it is.

> Here's what I need to know:
> What files hold the user and site defaults and
> how to change them using the commandline, or if
> that is not an option; what to hexedit in them to get
> those settings to be different from what they are now.

I'm going to pass on this one on to some of the others who read here; I
know some of this has been discussed before and should be in the
archives.

> I've already discussed my problem with Jeff Bilicki
> (the shell tool guy), if I have the user and site settings
> changed, i can enter a user using the GUI again, as soon
> as the GUI has updated the databases the correct way,
> I can change quota, recreate a database to work with,
> etc. Right now I simply can't even create the base
> for a good recovery of it.

Have you brought this up on cobalt-developers?  Some people who read
there have a lot of experience with the internals of how the Cobalt
"sauce" works.

> It's been set to the defaults, which is 5 MB/user,
> and it's been switched off entirely by me using quotaoff.
> 0 means "Unlimited", or so I've read from those dreaded man pages.

Hmmm... I still think it's because it can't find what it needs to in the
PostgreSQL database.

I think you've exhausted the limits of my ability to help you onlist; I
wish you luck.

Jeff
-- 
Jeff Lasman <jblists@xxxxxxxxxxxxx>
Linux and Cobalt/Sun/RaQ Consulting
nobaloney.net
P. O. Box 52672, Riverside, CA  92517
voice: (909) 778-9980  *  fax: (702) 548-9484