[syslog-ng]Problem with HP-UX 11.0

[email protected] [email protected]
Mon, 20 May 2002 08:21:02 -0400

Thanks for the info - I did try a number of different source statements, none of
gave me anything useful.  I'll deal with syslogd on the HP boxes until we're
able to


                      Balazs Scheidler                                                                                                      
                      <[email protected]>            To:      [email protected]                                                     
                      Sent by:                      cc:                                                                                     
                      [email protected]         bcc:                                                                                    
                      .balabit.hu                   Subject: Re: [syslog-ng]Problem with HP-UX 11.0                                         
                      05/17/2002 03:51 AM                                                                                                   
                      Please respond to                                                                                                     

On Thu, May 16, 2002 at 12:53:33PM -0600, Brad Arlt wrote:
> On Thu, May 16, 2002 at 02:16:58PM -0400, [email protected] wrote:
> > Hi all,
> >
> > I have been running syslog-ng on a handful of Solaris boxes for some time
> > now with no problems, and am attempting to get it running on HP-UX.
> > I have compiled (with gcc) and installed syslog-ng 1.5.16 and libol 0.3.2 on
> > a system running HP-UX 11.00.  I am using the following source statement
> > in my config file:
> >
> > source s_sys { pipe("/dev/log");  internal();  };
> Err... Ah, are you sure that opening a pipe from /dev/log will yeild
> what you want?  /dev/log is usually a Unix domain socket, which might
> put more in the stream asside from ASCII.  I'd turn off any syslog
> daemons you have and just cat /dev/log | od

Sorry, but HP-UX's /dev/log is really a pipe and not a socket. The problem
seems to be that programs sending messages to /dev/log write a whole 2048
bytes block regardless the real length of the message. As syslog-ng reads
_lines_ from a pipe, the rest of the 2048 bytes block is also read, which is
what you see there.

Currently my development branch of syslog-ng 2.0 supports this, but 1.5.x

A temporary solution would be to use both original syslogd from HP-UX and
have it send messages to localhost where a syslog-ng is listening.

PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1

syslog-ng maillist  -  [email protected]