topic Re: syslogd problem with /dev/log.un in Operating System - HP-UX

syslogd problem with /dev/log.un

Whit Murrill_1 — Wed, 12 Apr 2000 12:40:23 GMT

The syslogd man page talks about a UNIX domain socket, /dev/log.un, that the
syslogd daemon reads from. Why doesn't this socket exist? Why doesn't syslogd
create this socket when it starts up?

The reason I'm interested is that I'm trying to build Perl. Perl has an
interface to syslog called Sys::Syslog. When Perl builds it looks for a
#define'd macro called _PATH_LOG; this it what it uses for the AF_UNIX socket
path. The HPUX include file, syslog.h, does not define this macro.

Re: syslogd problem with /dev/log.un

Berlene Herren_1 — Fri, 14 Apr 2000 06:02:30 GMT

Syslogd code will read from the file /dev/log.un IF the file exists. So,
program doing logging must create the AF_UNIX socket /dev/log.un and then
syslogd will read from it.

Berlene

Re: syslogd problem with /dev/log.un

Whit Murrill_1 — Fri, 14 Apr 2000 11:19:57 GMT

I did not think the client program would have to create the socket for the
syslogd daemon to listen to. The client program does not have permission to
write to the /dev directory.

Also, I downloaded BSD source code for syslogd (syslogd.c). Looking thru the
code, it is syslogd that creates a unix socket and binds to the address
/dev/log.un. This allows the client program to connect to the unix socket.