Re: uw-imapd won't start

2002-03-15 Thread Jaldhar H. Vyas
On Fri, 15 Mar 2002, Thomas Shemanske wrote: > The problem seems to be the tcp daemon tcpd. The logs are full of the > following message: > > Mar 14 16:59:40 buzoe tcpd[6026]: connect from unknown > Mar 14 16:59:40 buzoe tcpd[6026]: warning: can't get client address: > Socket operation on non-soc

Re: uw-imapd won't start

2002-03-15 Thread Thomas Shemanske
The problem seems to be the tcp daemon tcpd. The logs are full of the following message: Mar 14 16:59:40 buzoe tcpd[6026]: connect from unknown Mar 14 16:59:40 buzoe tcpd[6026]: warning: can't get client address: Socket operation on non-socket Looks like we are missing a package. Any ideas?

Re: uw-imapd won't start

2002-03-15 Thread Jaldhar H. Vyas
On Fri, 15 Mar 2002, Thomas Shemanske wrote: > I have a colleague who just did a clean install of woody and once again > wanted to setup his imap server. He installed uw-imapd, but the daemon > won't start. > * Use lsof to check if there isn't anything else listening to port 143. * Telnet to por

Re: uw-imapd won't start

2002-03-15 Thread Chris Hilts
On Fri, Mar 15, 2002 at 11:00:56AM -0500, Thomas Shemanske wrote: > There is the appropriate entry in /etc/inetd.conf (which starts the > daemon through tcpd). One can start the daemon manually with > /usr/sbin/imapd, but we can't figure out why the daemon doesn't start > with the rest of the s

uw-imapd won't start

2002-03-15 Thread Thomas Shemanske
I have a colleague who just did a clean install of woody and once again wanted to setup his imap server. He installed uw-imapd, but the daemon won't start. There is the appropriate entry in /etc/inetd.conf (which starts the daemon through tcpd). One can start the daemon manually with /usr/s