>Number:         33824
>Category:       pkg
>Synopsis:       couriertcpd gets installed in /usr/pkg/bin, instead of /usr/pkg/sbin
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jun 26 00:35:00 +0000 2006
>Originator:     Casey Carter
>Release:        NetBSD 3.0
>Organization:
>Environment:
	
	
System: NetBSD bsdbox.hive-mind.net 3.0 NetBSD 3.0 (BSDBOX-R3) #0: Mon May 15 21:41:39 PDT 2006 rockear@bsdbox.hive-mind.net:/usr/obj/sys/arch/i386/compile/BSDBOX-R3 i386
Architecture: i386
Machine: i386
>Description:
	
I was having difficulty getting the courierpop, courierpops, courierimap,
and courierimaps scripts in /usr/pkg/etc/rc.d/ to start their services.
authdaemond would start properly, but the others would report that they
started, put a pidfile in /var/run/, and not actually start anything. In
maillog this would show up as, for example, "pop3d: exec: no such file or
directory".

It turned out that the couriertcpd package installs couriertcpd to
/usr/pkg/bin. The scripts pop3d, pop3d-ssl, imapd, and imapd-ssl in
/usr/pkg/sbin, which are called by the rc.d scripts, expect couriertcpd to
also be in /usr/pkg/sbin. When it is not found there, the scripts fail
silently, and leave dangling pidfiles in /var/run.
>How-To-Repeat:
	
Install couriertcpd-0.53.2nb1 and courier-imap-4.1.1nb2.
Add "authdaemond=YES", "courierpop=YES" to /etc/rc.conf
/usr/pkg/etc/rc.d/authdaemond start
/usr/pkg/etc/rc.d/courierpop start
>Fix:
	
ln -s /usr/pkg/bin/couriertcpd /usr/pkg/sbin/couriertcpd

>Unformatted: