Hi Chris,

On Mon, 16 Jun 2003 04:19:13 -0700 (PDT) Chris Pugh wrote:

>>>> Are you sure the '/usr/sbin/vchkpw' resutls from
>>>> your compile operation?
>>> No, it doesn't.
>> Well, than why do you use it? :-)
> Don't ask me, ask the system! It chose to to do it,
> not I.

Well ... but you know this ain't Windows? You're not enforced to
accept silently anything your system does :-)
Your system does what it's told to do, not what it wants.
Tell it to use "the other" vchkpw :-)

> maybe I should just get nasty and delete them?

Do it. As it doesn't belong to any packet any longer you'll not confuse
the package management.  As it doesn't belong to your manually compiled
stuff you'll not break functionality coming from the manually compiled
So delete it (or move it to /tmp and delete it from there after some
time has passed w/o errors).

>> Well ... give it a try. Replace '/usr/sbin/vchkpw' with
>> '/home/vpopmail/bin/vchkpw' in your POP3 startup script and report
>> back if this solved your problem

> First thing I thought of actually, and as it happens
> already the case. So where the reference is, I don't
> really know.( I dropped tcpserver temporarily,
> and pasted the code into inetd.conf )
> # below an entry for vpopmail
> pop3 stream tcp nowait root \
> /var/qmail/bin/qmail-popup \
> qmail-popup mail.extras.co.uk \
> /home/vpopmail/bin/vchkpw \
> /var/qmail/bin/qmail-pop3d \
> Maildir
> Is it maybe catching the first entry in the $PATH??

Usually it would, but in above exmaple you didn't give system the chance
to search the path for vchkpw. You specified a very dedicated location
of vchkpw binary you intend to be used. Did you '-HUP' inetd after
changing the line for pop3?

Reply via email to