Re: [vchkpw] Question about Dir Control (.dir-control)
On Jun 30, 2004, at 4:18 PM, Ken Jones wrote:
Yep. Looks like whoever added the Warning message code needed to
ifdef it with the big user dir define.
Added to CVS and scheduled for 5.4.7.
--- vpopmail.c 26 Jun 2004 02:20:56 - 1.28.2.4
+++ vpopmail.c 1 Jul 2004 05:29:45 - 1.28.2.5
@@ -262,9 +262,11 @@
fprintf(stderr, "Failed while attempting to delete domain from
the qmail control files\n");
}
+#ifdef USERS_BIG_DIR
if (vdel_dir_control(domain) != 0) {
- fprintf (stderr, "Failed while attempting to delete domain from
dir_control\n");
+ fprintf (stderr, "Warning: Failed to delete dir_control for
%s\n", domain);
}
+#endif
/* send a HUP signal to qmail-send process to reread control files
*/
signal_process("qmail-send", SIGHUP);
@@ -379,10 +381,12 @@
*/
vdel_limits(domain);
+#ifdef USERS_BIG_DIR
/* delete the dir control info for this domain */
if (vdel_dir_control(domain) != 0) {
fprintf (stderr, "Warning: Failed to delete dir_control for
%s\n", domain);
}
+#endif
/* Now remove domain from filesystem */
/* if it's a symbolic link just remove the link */
--
Tom Collins - [EMAIL PROTECTED]
QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/
Info on the Sniffter hand-held Network Tester: http://sniffter.com/
Re: [vchkpw] Question about Dir Control (.dir-control)
On Jun 30, 2004, at 6:18 PM, Tom Collins wrote:
What version of vpopmail? I thought we took care of that error
message ("Warning: Failed to delete dir_control for test.com") during
the development cycle leading up to 5.4.0. It was due to the domain's
directory getting deleted before the dir_control file (for user
directories) inside of it.
vpopmail-5.4.0.tar.gz
Like Ken mentioned, its trying to delete .dir-control with out first
checking if that feature is enabled or not.
Perhaps someone could look into making a patch to add a
--disable-domains-big-dir (or would that be enable?) to disable
hashing when creating new domains. It shouldn't be too hard to ifdef
out the code responsible for hashing.
I think that feature would be a very welcome one.
Brian
--
Tom Collins - [EMAIL PROTECTED]
QmailAdmin: http://qmailadmin.sf.net/ Vpopmail:
http://vpopmail.sf.net/
Info on the Sniffter hand-held Network Tester: http://sniffter.com/
Re: [vchkpw] Question about Dir Control (.dir-control)
On Jun 30, 2004, at 4:13 PM, Brian Feeny wrote:
Thanks for answering. I did see that disable-users-big-dir option,
so I configured with it.
It seems to still do the following though:
1. create .dir-control in the domains directory.
2. complain when removing a domain that it can't delete the dir
control.
[EMAIL PROTECTED] bin]$ ./vadddomain test.com testcom
[EMAIL PROTECTED] bin]$ ./vdeldomain test.com
Warning: Failed to delete dir_control for test.com
Even though /home/cust/vpopmail/domains/test.com is gone,
there is a .dir-control file in /home/cust/vpopmail/domains. I
manually
deleted this file, but every time I add a new domain it creates this
file
again. Not sure why ./vdeldomain would be complaining when there
wasnt a .dir-control in the first place associated with the domain I
was
deleting.
What version of vpopmail? I thought we took care of that error message
("Warning: Failed to delete dir_control for test.com") during the
development cycle leading up to 5.4.0. It was due to the domain's
directory getting deleted before the dir_control file (for user
directories) inside of it.
Perhaps someone could look into making a patch to add a
--disable-domains-big-dir (or would that be enable?) to disable hashing
when creating new domains. It shouldn't be too hard to ifdef out the
code responsible for hashing.
--
Tom Collins - [EMAIL PROTECTED]
QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/
Info on the Sniffter hand-held Network Tester: http://sniffter.com/
Re: [vchkpw] Question about Dir Control (.dir-control)
On Wednesday 30 June 2004 06:13 pm, Brian Feeny wrote: > Ken, > > Thanks for answering. I did see that disable-users-big-dir option, > so I configured with it. > > It seems to still do the following though: > > 1. create .dir-control in the domains directory. > 2. complain when removing a domain that it can't delete the dir control. Yep. Looks like whoever added the Warning message code needed to ifdef it with the big user dir define. > > [EMAIL PROTECTED] bin]$ ./vadddomain test.com testcom > [EMAIL PROTECTED] bin]$ ./vdeldomain test.com > Warning: Failed to delete dir_control for test.com > > Even though /home/cust/vpopmail/domains/test.com is gone, > there is a .dir-control file in /home/cust/vpopmail/domains. I manually > deleted this file, but every time I add a new domain it creates this > file > again. Not sure why ./vdeldomain would be complaining when there > wasnt a .dir-control in the first place associated with the domain I was > deleting. > > Any ideas? Looks like the only way to stop domains from being hashed would be in 2 steps: rm -rf /home/vpopmail/domains/.dir-control vadddomain domainname If the /home/vpopmail/domains/.dir-control file does not exist then it creates a default one and puts the domain in /home/vpopmail/domains. So you can fake it out by deleteing the .dir-control every time. Also looks like we need to fix that warning message. Ken > > Brian > > On Jun 30, 2004, at 5:27 PM, Ken Jones wrote: > > On Wednesday 30 June 2004 03:37 pm, Brian Feeny wrote: > >> First, is there a way to disable the Dir Control functionality of > >> vpopmail? > > > > Sure. Use this option > > > > --disable-users-big-dir > > > >> If not, is there any downside to just not using it? > > > > Just the optimization for keeping the number of directories in > > a directory to a efficent level. > > > >> You may ask why I need to do this. > >> > >> We do our own hashing of directories and usernames here, using our own > >> script systems. > >> I like this because the paths that we are creating are predictable > >> since we are determining them > >> instead of dir control/vadduser. > > > > Since you do your own hashing, no need to use vpopmail's. > > > > Cheers, > > Ken Jones > > > >> Brian > >> > >> -- > >> Brian Feeny, CCIE #8036e: [EMAIL PROTECTED] > >> Network Engineer p: 318.213.4709 > >> ShreveNet Inc. f: 318.221.6612
Re: [vchkpw] Question about Dir Control (.dir-control)
Ken, Thanks for answering. I did see that disable-users-big-dir option, so I configured with it. It seems to still do the following though: 1. create .dir-control in the domains directory. 2. complain when removing a domain that it can't delete the dir control. [EMAIL PROTECTED] bin]$ ./vadddomain test.com testcom [EMAIL PROTECTED] bin]$ ./vdeldomain test.com Warning: Failed to delete dir_control for test.com Even though /home/cust/vpopmail/domains/test.com is gone, there is a .dir-control file in /home/cust/vpopmail/domains. I manually deleted this file, but every time I add a new domain it creates this file again. Not sure why ./vdeldomain would be complaining when there wasnt a .dir-control in the first place associated with the domain I was deleting. Any ideas? Brian On Jun 30, 2004, at 5:27 PM, Ken Jones wrote: On Wednesday 30 June 2004 03:37 pm, Brian Feeny wrote: First, is there a way to disable the Dir Control functionality of vpopmail? Sure. Use this option --disable-users-big-dir If not, is there any downside to just not using it? Just the optimization for keeping the number of directories in a directory to a efficent level. You may ask why I need to do this. We do our own hashing of directories and usernames here, using our own script systems. I like this because the paths that we are creating are predictable since we are determining them instead of dir control/vadduser. Since you do your own hashing, no need to use vpopmail's. Cheers, Ken Jones Brian -- Brian Feeny, CCIE #8036 e: [EMAIL PROTECTED] Network Engineerp: 318.213.4709 ShreveNet Inc. f: 318.221.6612
Re: [vchkpw] Question about Dir Control (.dir-control)
On Wednesday 30 June 2004 03:37 pm, Brian Feeny wrote: > First, is there a way to disable the Dir Control functionality of > vpopmail? Sure. Use this option --disable-users-big-dir > > If not, is there any downside to just not using it? Just the optimization for keeping the number of directories in a directory to a efficent level. > > You may ask why I need to do this. > > We do our own hashing of directories and usernames here, using our own > script systems. > I like this because the paths that we are creating are predictable > since we are determining them > instead of dir control/vadduser. Since you do your own hashing, no need to use vpopmail's. Cheers, Ken Jones > > Brian > > -- > Brian Feeny, CCIE #8036 e: [EMAIL PROTECTED] > Network Engineer p: 318.213.4709 > ShreveNet Inc.f: 318.221.6612
[vchkpw] Question about Dir Control (.dir-control)
First, is there a way to disable the Dir Control functionality of vpopmail? If not, is there any downside to just not using it? You may ask why I need to do this. We do our own hashing of directories and usernames here, using our own script systems. I like this because the paths that we are creating are predictable since we are determining them instead of dir control/vadduser. Brian -- Brian Feeny, CCIE #8036 e: [EMAIL PROTECTED] Network Engineerp: 318.213.4709 ShreveNet Inc. f: 318.221.6612
