Re: [vchkpw] vadddomain -O is broken in 5.4.0-pre1

2003-12-14 Thread Casey Zacek
Tom Collins wrote (at Sun, Dec 14, 2003 at 02:28:36PM -0700): > There's an open bug report for it on SourceForge now. I suppose I should get used to using that thing... sorry. > In the long run, the > solution is to cache the information on the newly-added domain so > vget_assign can pull from

Re: [vchkpw] vadddomain -O is broken in 5.4.0-pre1

2003-12-14 Thread Tom Collins
On Sunday, December 14, 2003, at 06:44 AM, X-Istence wrote: Submit a patch on sourceforge or put it on the list if possible, as you know why the problem happens. If not, let me know where to look exactly, and ill take a look. There's an open bug report for it on SourceForge now. It may have wor

Re: [vchkpw] vadddomain -O is broken in 5.4.0-pre1

2003-12-14 Thread Casey Zacek
X-Istence wrote (at Sun, Dec 14, 2003 at 08:44:53AM -0500): > Casey Zacek wrote: > > >'vadddomain -O' is broken in 5.4.0-pre1, and probably others. > > > >The problem is that vget_assign() looks in [/var/qmail/]users/cdb for > >the domain, and it's not there yet for the vadduser(postmaster) call.

Re: [vchkpw] vadddomain -O is broken in 5.4.0-pre1

2003-12-14 Thread X-Istence
Casey Zacek wrote: 'vadddomain -O' is broken in 5.4.0-pre1, and probably others. The problem is that vget_assign() looks in [/var/qmail/]users/cdb for the domain, and it's not there yet for the vadduser(postmaster) call. vsetuserquota(), after vadduser(), also uses vget_assign(), as does vadddoma