socket call resulted in error (98): no message

[Cantor, Scott]

> I had similar problems with 2.4.3 on CentOS 5.5 when I started shibd without
> the init scripts. Once started, shibd would not let go of its socket even with -f
> or manual kills of the processes. I tried "shibd stop", "shibd -f stop", "shibd -f
> start", and finally tried "kill" and eventually "kill -9". The kills terminated the
> process but the socket remained.

That's really odd. The socket is just a file, if nothing else killing the process and rm'ing the file should work fine.

> Once I started using the init.d scripts or the "service shibd start" command,
> the problem went away.

There isn't really that much difference. I only mentioned it because once the non-root support ships with 2.5, there will be.

If anybody can else reproduces this, please file a bug and I'll look into it.

-- Scott