Bindsock issues all of a sudden

I’m using Domino7-b2.

It appears that bindsock has crapped the bed all of a sudden. I had a process top my CPU resources for over an hour straight, forcing me to restart the machine. Upon restart, bindsock no longer seems to work. Which means no SMTP listener. The port is not in use, bindsock is owned by root, has the sticky id set, etc.

I’ve also done a few kernel updates and wonder whether or not that may have screwed anything up. I’ve set the LD_ASSUME_KERNEL=2.2.5 in my .bash_profile, but no dice.

I tried then to install Domino7-b3 but no difference. I’m not sure if I need to just delete the /opt/lotus/ directory outright (in case of file corruption from the crash or what, but any ideas would be appreciated as I dunno what to try next.

Subject: bindsock issues all of a sudden

I just did an upgrade to Domino 7b3 and still the same problems. Anyone?

Thanks in advance,

Sam

Subject: RE: bindsock issues all of a sudden

Fixed it finally,

For the sake of posterity, if you do ‘chmod u+s’, and it still doesn’t work, try chmodding to 700, first (read only), and THEN doing a ‘chmod u+s’. I found that Domino was still scoffing at multi-user access to bindsock and didn’t allow smtp or http to load until ONLY root had access.

Hope that helps someone.

Sam