syslog messages to port 32376

Nothing is usually listening there. Try using netstat to examine your machine. I wonder if Installer.app or Install.framework uses this for some sort of interprocess communication?

How about:

sudo lsof -i :32376

The line refers to the messages from an application logging with the 'install' facility, at all levels will be sent to the process running on the local host and listening at port 32376.

Which raises the question, why? Why would syslogd want to talk to itself?

from looking at the syslog.conf(5) manpage:

o A hostname (preceded by an at (``@'') sign). Selected messages are
forwarded to the syslogd program on the named host.

which is interesting since the syslogd daemon on my system is only listening on port

sudo lsof -p 61
syslogd 61 root 23u IPv4 0x0293a9c0 0t0 UDP *:54042

and netstat indicates that syslogd is listening for traffic from any host, that can make it past my firewall.

netstat -anf inet
udp4 0 0 *.54042 .

Andy

Samuel,

I have the feeling that this line is there either for compatibility reasons or because, as Mac OS X is based on FreeBSD, FreeBSD used it.
As the other posters said, it practically does nothing as the 32376 port is closed.

Mihalis.

Hi Samuel et al,
It's not necessary for a daemon to always be running in order for this entry to be important. The daemon has only to be listening while Installer.app is writing to syslog. This could make possible some sort of interprocess communication for the Installer process. This might also facilitate a "call home" by the installer when it's run on a managed machine. I wouldn't mess with one of Apple's entries unless you know exactly what it does.
--
Gary
~~~~
Labor, n.:
One of the processes by which A acquires property for B.
-- Ambrose Bierce, "The Devil's Dictionary"

That may be used internally for Software Update to create syslog entries.