Re: [vchkpw] Re: ONCHANGE behavior

[John Simpson]

On 2006-04-16, at 0639, Robin Bowes wrote:

If you look at qpsmtpd (which is where I believe the idea of onchange
hooks came from)

not really... it's something i've wished that vpopmail had for several years, but never had the time to write.

It also calls different "scripts" for each hook rather than having one

for vpopmail?

monolithic "something's changed" script. Would that be a better approach

        #!/bin/sh
        if [ -e ~vpopmail/etc/$1 ]
        then
                exec ~vpopmail/etc/$*
        fi
        logger -t onchange ignoring command "$*"
        exit 0

i don't think so. if you want to use this kind of approach, you can create an "onchange" script which looks like this: and then create scripts in ~vpopmail/etc with names matching the "cmd" parameter sent to the "onchange" script.

would it be better to use the vpopmail function names for all of the
notifications, so that they are all consistent? if so, now is the
time to make the decision, since nobody (as far as i know) has
written any onchange scripts which would look for specific strings.

I don't really care.  Robin - what do you think the names should be?

As far as I'm concerned, all I need is a complete list in front of me
when I sit down to write the script.

user_add, but not a mix.

I don't really care either, but they should be consistent - add_user or

--------------------------------------------------
| John M. Simpson - KG4ZOW - Programmer At Large |
| http://www.jms1.net/           <[EMAIL PROTECTED]> |
--------------------------------------------------
| Mac OS X proves that it's easier to make UNIX  |
| pretty than it is to make Windows secure.      |
--------------------------------------------------

since nobody really cares, i'm just going to leave them the way they are.

PGP.sig
Description: This is a digitally signed message part