[Date Prev]   [Date Next] [Thread Prev]   [Thread Next] [Date Index]   [Thread Index]

 

     Re: [nocol-users] bsdi socket


Well, the ping problem sounds like multiping is not setuid root?
(That's a guess, anyway)  

Other than that, looks like, as you said, the connect() is failing
in newSocket at line 167 (nocol 4.2.1); though the error message
surprises me a bit.


On Thu, 3 Dec 1998, Kenneth Cho wrote:

> Date: Thu, 3 Dec 1998 23:25:37 +0800 (HKT)
> From: Kenneth Cho <cho@HK.Super.NET>
> To: nocol-users@navya.com
> Cc: Cho Man Fai <cho@HK.Super.NET>
> Subject: [nocol-users] bsdi socket
> 
> 
> newSocket() connect failed: Bad file descriptor./bgpmon: 202.64.240.215: newSocket: Bad file descriptor
> newSocket() connect failed: Bad file descriptor./bgpmon: 202.64.240.41: newSocket: Bad file descriptor
> newSocket() connect failed: Bad file descriptornewSocket() connect failed: Bad file descriptor
> 
> (ippingmon).. locked pid-file, started new process
> ping: socket: Permission denied
> 
> 
> Thanks a lot.
> 
> Rgds,
> Cho Man Fai
> 

-- 
Russell M. Van Tassell                          Commercial Systems Corp.
russell@cscorp.com                               http://www.cscorp.com/

                                                     Ph: 1-888/COMM-SYS