LinuxQuestions.org - trying to solve "auth/tcp (2): bind: Address already in use"

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - trying to solve "auth/tcp (2): bind: Address already in use" (https://www.linuxquestions.org/questions/slackware-14/trying-to-solve-auth-tcp-2-bind-address-already-in-use-4175496889/)

trying to solve "auth/tcp (2): bind: Address already in use"

Got a fresh Slack 14 64 install (well, kind of fresh) and I'm noticing the folloing in my syslog every 10 minutes:

Code:

Mar 3 18:48:45 orion inetd[6615]: auth/tcp (2): bind: Address already in use

This has pretty much been the case since install and I'm trying to get to the bottom of it. Searching on here and googling etc but I'm in a hole really. Any pointers would be greatly appreciated.

Other servers (albeit) older installs don't show similar logs.
Thanks in advance...

UPDATE

I stopped in.identd and haven't seen the entry in the log since, if that explains anything.

I'm surprised no-one else has experienced it - typically, when opening a socket, you set the socket options before you call 'bind'. In this case it would be:

Code:

char one=1;

setsockopt({socket_fd}, SOL_SOCKET, SO_REUSEADDR, &one, sizeof(char));

bind({socket_fd}, struct sockaddr *....);

If the module/program/daemon/whatever for some reason aborted and was restarted, you would get the above message 'cuz the socket was not properly closed on exit (if you didn't do the setsockopt-call that is).