2008/6/3 John Simpson <[EMAIL PROTECTED]>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 2008-05-27, at 1016, Maurizio Rottin wrote: >> >> 2008/3/7 John Simpson <[EMAIL PROTECTED]>: >>> >>> On 2008-02-27, at 1126, Steve wrote: >>> the ONCHANGE mechanism was designed to be used in conjunction with some >>> mechanism which allows a non-root process (like the "onchange" script) to >>> trigger a root process to execute on demand. >>> >> >> and indeed it is working. >> but i don't understand why vpopmail is using the onchange mechanism, >> while qmailadmin is not! > > again. did you compile qmailadmin after having compiled and installed a > version of vpopmail which had the ONCHANGE code present and enabled?
yes > check the "qmailadmin" binary installed within your web site, and make sure > it has the "onchange" code in it. for example... > > > # strings qmailadmin | grep -i onchange > allow_onchange > onchange_buf > %s/etc/onchange > ONCHANGE script %s not executable. > ONCHANGE script %s unable to exec. > ONCHANGE script %s unable to fork. yes: > then, what are the ownership and permissions of each of the following items: > > - - your qmailadmin binary > - - ~vpopmail/etc/onchange > - - ~vpopmail/etc > - - ~vpopmail > - - all parent directories of "~vpopmail", all the way back to "/" this is the point, you are right! i always forget that centos adds users directory with mask 700 drwx------ 9 vpopmail vchkpw 4096 15 feb 11:43 vpopmail a chmod 755 does the job! thank you John! -- mr !DSPAM:4844f77032354984235750!
