Hi,
On Thu, 2003-02-27 at 20:47, Rob G wrote:
> Do a netstat -na | grep LISTEN and see if anything else is listening on port
> 110 as that is what is holding the address open.
Try a netstat -lnp | grep 110 instead. It will also show the pid of the
listening program.
--
Anders Brander - http://a
On Thursday 27 February 2003 20:42, Kevin L Aleshire wrote:
> when i try to run the vpop script i get this error message "tcpserver:
> fatal: unable to bind: address already used"
>
> below is the script that i'm using.
>
> #!/bin/sh
> env - PATH="/var/qmail/bin:/usr/local/bin" \
> tcpserver -H -R
ROTECTED]>
To: "Vchkpw" <[EMAIL PROTECTED]>
Sent: Thursday, February 27, 2003 3:21 PM
Subject: RE: [vchkpw] starting vpop gives error
i'm still in the learning process of understanding the syntax of scripts
what's the difference in "2>&1" vs. just
l/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir 2>&1
>
> Regards,
> Rob G
> [EMAIL PROTECTED]
>
>
>
> ----- Original Message -
> From: "Kevin L Aleshire" <[EMAIL PROTECTED]>
> To: "Vchkpw" <[EMAIL PROTECTED]>
> Sent: Thursday
localhost.localdoma:ntp *:*
udp0 0 *:ntp *:*
- Original Message -
From: "Rob G" <[EMAIL PROTECTED]>
To: "Vchkpw" <[EMAIL PROTECTED]>
Sent: Thursday, February 27, 2003 12:01 PM
Subject: Re: [vchkpw] starting vpop gives error
>
TECTED]>
Sent: Thursday, February 27, 2003 2:54 PM
Subject: RE: [vchkpw] starting vpop gives error
this is the response that i get from that command, it doesn't really list
anything specific
[EMAIL PROTECTED] /etc/rc3.d# netstat -na | grep LISTEN
tcp0 0 0.0.0.0:110
telnet to port 110 and try issuing cammands and see what it gives back...
-John
- Original Message -
From: "Kevin L Aleshire" <[EMAIL PROTECTED]>
To: "Vchkpw" <[EMAIL PROTECTED]>
Sent: Thursday, February 27, 2003 11:54 AM
Subject: RE: [vchkpw] starting
ISTEN
is there any other way to find out what it is?
> -Original Message-
> From: Rob G [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 27, 2003 1:48 PM
> To: Vchkpw
> Subject: Re: [vchkpw] starting vpop gives error
>
>
> Do a netstat -na | grep LISTE
Do a netstat -na | grep LISTEN and see if anything else is listening on port
110 as that is what is holding the address open.
Regards,
Rob G
[EMAIL PROTECTED]
- Original Message -
From: "Kevin L Aleshire" <[EMAIL PROTECTED]>
To: "Vchkpw" <[EMAIL PROTECTED]>
Sent: Thursday, February 27, 200