topic Re: newsyslog program in Operating System - HP-UX

newsyslog program

Ragni Singh — Thu, 21 Mar 2002 18:22:53 GMT

Hey everyone,

Since I didn't get the answer from anyone regarding this, I have to ask again. Has anyone installed the newsyslogd program on their Unix server and isit working?. I am having some issues installing this and would love for some assistance. Any help will be greatly appreciated.

Re: newsyslog program

harry d brown jr — Thu, 21 Mar 2002 18:27:08 GMT

Sanman,

What do you mean by NEW syslogd program? Where did you get it? What OS are you running?

live free or die
harry

Re: newsyslog program

Helen French — Thu, 21 Mar 2002 18:31:26 GMT

Sanman,

Here is some information about nesyslog under Solaris. I have not tried this tool yet:

http://www.cert.org/security-improvement/implementations/i041.09.html

HTH,
Shiju

Re: newsyslog program

Ragni Singh — Thu, 21 Mar 2002 18:33:09 GMT

There is a newsyslog program that I downloaded from freshmeat.net.

When I ran the make install on the program, I get a strange message about sys_signame. I have no clue as to what it is and needed to know if anyone else encountered this problem when they installed it and what they did to fix it.
By the way, I'm installing thi son a K-class using 11 version 64 bit.

Re: newsyslog program

Jon Mattatall — Thu, 21 Mar 2002 19:40:35 GMT

PSIGNAL
SYNOPSIS
#include

void
psignal(unsigned sig, const char *s);

extern const char * const sys_siglist[];
extern const char * const sys_signame[];

#include

char *
strsignal(int sig);

DESCRIPTION
The psignal() and strsignal() functions locate the descriptive message string for a signal number.
The strsignal() function accepts a signal number argument sig and returns a pointer to the corresponding message string.
The psignal() function accepts an signal number argument sig and writes it to the standard error. If the argument s is non-NULL and does not point to the null character, s is written to the standard error file descriptor prior to the message string, immediately followed by a colon and a space. If the signal number is not recognized (sigaction(2)), the string ``Unknown signal'' is produced.

The message strings can be accessed directly through the external array sys_siglist, indexed by recognized signal numbers. The external array sys_signame is used similarly and contains short, lower-case abbreviations for signals which are useful for recognizing signal names in user input. The defined variable NSIG contains a count of the strings in sys_siglist and sys_signame.

I confess, I cannot make a great deal of sense of this. This is from a BSD man page.

The only reason I've even heard of newsyslogd is that one of the guys here is a FreeBSD Guru, and he managed to run it on an HP11.00 box after some tweaking. It was all well beyond me, I'm afraid.

There's likely an HPUX equivalent, but I have no idea what it may be.