RE: Different socket types ... no response!

From: David Richards <dj.richards@dont-contact.us>
Date: Thu, 26 Feb 1998 15:48:10 +1000 (EST)

I have had no problems in similar applications, i.e. running in user
space. All I have had to do in the past is change the permissions on the
"server" socket. In this casem it just don't work.

Any other ideas??

Thanks,

Dave.

-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-
David Richards Ph: +61 7 3864 4347
Network Programmer Fax: +61 7 3864 5272
Computing Services E-mail: dj.richards@qut.edu.au
Queensland University of Technology
Brisbane, Australia
-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-

On Thu, 26 Feb 1998, Colin Rhodes wrote:

> Hi David,
>
> I suspect you have a software problem - might be something to do with include files or just a general bug.
>
> The squid code runs in user space. It simply can't tamper with your use of the socket. Even if you are in the same app,
> socket options are set on a per file descriptor basis, and the actual socket bit is well out of reach.
>
> So, squid can't screw up a new socket that you create (and I have had no problems creating sockets in squid, albeit not UNIX domain sockets).
>
> Usually, this is caused by getting the wrong value on AF_UNIX (ie. #defined badly by someone else and overriding the header defn), or SOCK_DGRAM. Run it through cpp and check the values against the header file.
>
>
> Kindest Regards,
>
> Colin Rhodes
> Senior Systems Engineer
> Kodak Australia.
>
> -----Original Message-----
> From: David Richards [SMTP:dj.richards@qut.edu.au]
> Sent: Thursday, February 26, 1998 3:14 PM
> To: Squid Discussion List
> Subject: Different socket types ... no response!
>
> Hi,
>
> Some of you may be aware that I've been playing with squid, it the
> authentication area. I have just tried to place into squid a socket of
> the type AF_UNIX, SOCK_DGRAM.
>
> When I try and write to this socket using "sendto", an error is
> generated errno equals 47 (EAFNOSUPPORT) which means :
>
> "Address family not supported by protocol family"
>
> Now what puzzles me is that the calls I am using have been proven
> time and time again, because I have created a library of these calls.
>
> Why will these not work in squid??
>
> Thanks,
>
> Dave.
>
> -#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-
> David Richards Ph: +61 7 3864 4347
> Network Programmer Fax: +61 7 3864 5272
> Computing Services E-mail: dj.richards@qut.edu.au
> Queensland University of Technology
> Brisbane, Australia
> -#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-#-
>
>
>
>
Received on Thu Feb 26 1998 - 00:39:50 MST

This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:38:59 MST