on 5/1/01 11:14 AM, John Stile at [EMAIL PROTECTED] wrote:
> Bill Ship wrote:
>>
>> on 4/30/01 3:26 PM, John Stile at [EMAIL PROTECTED] wrote:
>>
>>> Bill Shupp wrote:
>>>>
>>>> on 4/30/01 12:22 PM, John Stile at [EMAIL PROTECTED] wrote:
>>>>
>>>>> Bill Shupp wrote:
>>>>>>
>>>>>> on 4/30/01 11:49 AM, John Stile at [EMAIL PROTECTED] wrote:
>>>>>>
>>>>>>> Is this is a vpopmail issue or a courier IMAP issue?
>>>>>>> When I try to add courier to qmail+vpopmail, at the "make check" step,
>>>>>>> it errors on authvchkpw.
>>>>>>> I have never debugged a problem with make, short of checking the paths
>>>>>>> in the Makefile.
>>>>>>> So, what can you sugest I do next?
>>>>>>> If it is a version compatablity problem, how do I tell what version of
>>>>>>> vpopmail is running?
>>>>>>>
>>>>>>> make check # failed at this step:
>>>>>>>
>>>>>>> gcc -I/home/vpopmail/include -g -O2 -Wall -I.. -I./..
>>>>>>> -L/home/vpopmail/lib -o authvchkpw modauthvchkpw.o libauthmod.a
>>>>>>> libauth.a ../md5/libmd5.a -lvpopmail -lm -lcrypt
>>>>>>> libauth.a(preauthvchkpw.o): In function `auth_vchkpw_pre':
>>>>>>> /home/jstile/courier-imap-1.3.7/authlib/preauthvchkpw.c:66: undefined
>>>>>>> reference to `vget_assign'
>>>>>>> /home/jstile/courier-imap-1.3.7/authlib/preauthvchkpw.c:78: undefined
>>>>>>> reference to `vclose'
>>>>>>> collect2: ld returned 1 exit status
>>>>>>> gmake[1]: *** [authvchkpw] Error 1
>>>>>>
>>>>>> Try typing vadduser -v to get the version info. I recommend upgrading to
>>>>>> the latest 4.9.10 anyway.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Bill Shupp
>>>>>
>>>>> How do I tell what version I'm running?
>>>>> The vadduser -v displays a help message, and -v is not an option.
>>>>> man vadduser does not show the version.
>>>>> The doc directory under vpopmail's home does not contain the version.
>>>>> They didn't make it too easy.
>>>>
>>>> The -v option wasn't added until 4.9.2, so your version is older than that.
>>>> I recommend upgrading.
>>>>
>>>> -Bill
>>>
>>> Thank you Bill. I am going to upgrade vpopmail tonight, however the
>>> install directions do not discuss an upgrade.
>>> Do I just instal the new version over what I have?
>>> I will upgrade from vpopmail-3.4.12 to vpopmail-4.9.10.
>>> What will this do to sqwebmail, or qmailadmin?
>>
>> Just use the same compile options as before, and you should be ok. You
>> should probably recompile sqwebmail and qmailadmin, but I'm not entirely
>> sure it's necessary. Perhaps someone else here does? I always do. But if
>> qmailadmin is as old as your vpopmail, it's changes a bit since then. Make
>> *sure* you backup your old copies if the software in case things go awry.
>> Or test the upgrade on another box ahead of time.
>>
>> -Bill
>
> After upgrading vpopmail (from v3.4.12 to v4.9.10), Courier-IMAP's "make
> check" did not have any errors, and all installed well.
>
> Question: Should executables found in ~vpopmail/bin/ exist in other
> parts of the system?
> After the upgrade, I listed all programs in ~vpopmail/bin/, and searched
> the system for files of the same name.
> I found 4 programs in /usr/bin, and they were the old vpopmail versions
> (vpopbull, vpasswd, vdeluser, vadduser).
> Additionally, the path for vpopuser, set in ~vpopuser/.bashrc to
> PATH=$PATH:$HOME/bin, so the old programs would be used before the new
> ones. Shouldn't the path for vpopmail be PATH=$HOME/bin:$PATH
As long as I've used vpopmail, the binaries were always in ~vpopmail/bin.
If you're concerned about using the old ones, I'd just delete them.
Regards,
Bill Shupp
